From: ptkwt@...1.aracnet.com (Phil Tomson)
Date: 2001-04-25T02:10:09+09:00
Subject: [ruby-talk:14165] Re: How does one interpret a RUBY.EXE.stackdump file?

In article <000501c0ccac$3caa2a40$0201a8c0@NATHANIELS7500>,
Nathaniel Talbott <ntalbott@rolemodelsoft.com> wrote:
>Phil Tomson wrote:
>
>> Nathaniel Talbott <ntalbott@rolemodelsoft.com> wrote:
>>
>> >
>> >WATANABE Hirofumi wrote:
>> >
>> >> Run gdb:
>> >> $ gdb -nw ruby.exe
>> >> (gdb) run <script name>
>> >> ...
>> >> Program received signal SIGSEGV, Segmentation fault.
>> >> ...
>> >> (gdb) bt
>> >>
>> >> and show us the result.
>> >
>>
>> Does this mean that the file RUBY.EXE.stackdump that I got originally
>> (prior to using gdb) is not useful itself?  So I have to run
>> the script under gdb until it coredumps again?
>
>Yes, although I'll say that I'm no Windows debugging expert, so I'm not
>positive. My guess is that there's a Windows tool you can buy that will
>interpret that stack dump for you, but I don't know what it is or where to
>get it. Sorry :-(
>
>

Hmmm....  I can't get this to happen under gdb (partly because the script 
doesn't seem to get that far in  Cygnus window for some reason - I was 
running it under a DOS window previously).  Would this stack dump be 
readable by some tool in Visual C++?  

BTW: the problem seems to be with reopen and threads, does reopen use 
threads internally?

Phil