From: Nathaniel Talbott <ntalbott@...>
Date: 2000-12-30T03:57:48+09:00
Subject: [ruby-talk:8289] Re: Inexplicable core dump [long]

> Thank you.  The backtrace helped me a lot.  I found a GC mark leakage.
> The smallest error reproducing script was
>
>   proc = self.method(:printf).to_proc
>   GC.start
>   proc.call("abc\n")
>
> Here's the patch.  Hope this helps you.
>
> 							matz.
>
<patch snipped>

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)

Eek! So I looked at the files, and ChangeLog, node.h and eval.c had all been
patched correctly. As I suspected, gc.c had not been patched, so I did so by
hand. When I then recompiled (after configure; make clean), I got another
one:

	<successful compiling>
	nm --extern-only --defined-only librubys.a | \
	  ./miniruby.exe -ne 'puts $1 if / [CDT] _(.*)$/' >> ruby.def
	./win32/resource.rb:17: [BUG] unknown node type 3
	ruby 1.6.2 (2000-12-25) [i686-cygwin]
	      0 [sig] miniruby 1336 stackdump: Dumping stack trace to
		miniruby.exe.stack
	dump
	Signal 6
	make: *** [dummy.rc] Error 134

So, needless to say, I have not successfully applied the patch :(

[A gray storm cloud gathers over Nathaniel's head and begins raining down
core dumps on him]

Any ideas on why this didn't patch/build correctly?


Nathaniel

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