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

In article <GVhF6.169$Yn3.7162@typhoon.aracnet.com>,
Phil Tomson <ptkwt@shell1.aracnet.com> wrote:
>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 :-(
>>
>>

OK, I managed to get it to run under gdb and this is what I get:

deadlock 0x45a5148: 2:8 (main) - drb_srvr.rb:317
deadlock 0x4611a88: 2:1  - 
/cygdrive/c/RUBY/lib/ruby/site_ruby/1.6/drb/drb.rb:29
6
deadlock 0x457a500: 2:2  - ./winntkill.rb:27

Program received signal SIGSEGV, Segmentation fault.
0x67d5652d in ?? ()
(gdb)

I don't see any kind of a core file...

Phil