> This seems to be becoming a habit, but when I applied the
> patch, I got:
>
> 	$ patch <ruby-talk8288\ Re\ Inexplicable\ core\ dump\ long.txt
> 	patching file `ChangeLog'
> 	Hunk #1 succeeded at 1 with fuzz 1.
> 	patching file `node.h'
> 	patching file `eval.c'
> 	Hunk #1 succeeded at 3746 (offset -1 lines).
> 	patching file `gc.c'
> 	assertion "hunk" failed: file "/src/patch/patch.c", line 334
> 	      0 [sig] patch 1376 stackdump: Dumping stack trace to
> 			patch.exe.stackdump
> 		Aborted (core dumped)

OK, I figured this one out... I saved the patch out using Outlook, and it
munged the carriage returns. I used another editor to restore them to their
original unix form, and the patch runs without core dumping.

Building Ruby is still broken, though:

	$ make
	./win32/resource.rb:17: [BUG] unknown node type 3
	ruby 1.6.2 (2000-12-25) [i686-cygwin]
	      0 [sig] miniruby 1500 stackdump: Dumping stack trace to
		 miniruby.exe.stack
	dump
	Signal 6
	make: *** [dummy.rc] Error 134

Here's the debug information:

	$ gdb -nw --quiet miniruby.exe
	(gdb) run ./win32/resource.rb
	Starting program: /cygdrive/c/ruby-1.6.2-new/ruby-1.6.2/miniruby.exe
	 ./win32/resource.rb
	./win32/resource.rb:17: [BUG] unknown node type 3
	ruby 1.6.2 (2000-12-25) [i686-cygwin]
	      0 [sig] miniruby 1440 stackdump: Dumping stack trace to
		 miniruby.exe.stack
	dump

	Program exited with code 0303000.
	(gdb) bt
	No stack.
	(gdb)


Nathaniel

<:((><
+ - -						+ - -
| RoleModel Software, Inc. &		| EQUIP VI
| The XP Software Studio(TM)		|