From: matz@... (Yukihiro Matsumoto)
Date: 2000-12-29T12:16:32+09:00
Subject: [ruby-talk:8230] Re: Inexplicable core dump

Hi,

In message "[ruby-talk:8178] Inexplicable core dump"
    on 00/12/29, "Nathaniel Talbott" <ntalbott@rolemodelsoft.com> writes:

|The first time it gets called in my code where proc.arity != 0 (i.e. it goes
|into the else branch) it does one of these:
|
|	./Tuner.rb:20: [BUG] Segmentation fault
|	ruby 1.6.2 (2000-12-25) [i686-cygwin]
|	      0 [sig] ruby 120 stackdump: Dumping stack trace to ruby.exe.stackdump
|	Aborted (core dumped)

Hmm, can you provide error reproducing script (and data)?
I'd like to see the stacktrace too, but since you're on Win 2000, it
may not be possible.

|Which is exactly what I started with plus a blank line at 21! I'm completely
|clueless. If I remove that blank line, things still core dump. Anybody have
|any idea what this is or how to fix it? Let me know if there's any more info
|that would be helpful (version info is in the core dump above; I'm running
|Windows 2000).

This is often a symptom of a GC bug.

							matz.