Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!news.dougwise.org!news.davenulle.org!noc.nerim.net!nerim.net!usenet-fr.net!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!talisker.lacave.net!lacave.net!not-for-mail From: Grant Schoep Newsgroups: comp.lang.ruby Subject: Re: Ruby app core dump on shutdown Date: Thu, 21 Apr 2011 16:14:31 -0500 Organization: Service de news de lacave.net Lines: 30 Message-ID: References: NNTP-Posting-Host: bristol.highgroove.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: talisker.lacave.net 1303425351 1991 65.111.164.187 (21 Apr 2011 22:35:51 GMT) X-Complaints-To: abuse@lacave.net NNTP-Posting-Date: Thu, 21 Apr 2011 22:35:51 +0000 (UTC) In-Reply-To: X-Received-From: This message has been automatically forwarded from the ruby-talk mailing list by a gateway at comp.lang.ruby. If it is SPAM, it did not originate at comp.lang.ruby. Please report the original sender, and not us. Thanks! For more details about this gateway, please visit: http://blog.grayproductions.net/categories/the_gateway X-Mail-Count: 382024 X-Ml-Name: ruby-talk X-Rubymirror: Yes X-Ruby-Talk: Xref: x330-a1.tempe.blueboxinc.net comp.lang.ruby:3338 Roger Pack wrote in post #994110: > does gdb help at all in this case? This is where I don't think gdb is helping me out, the first point where shows is (gdb) where #0 0x8744568d in ?? () Cannot access memory at address 0x8744568c All the rest of the threads are in varying states of #0 0x40000402 in __kernel_vsyscall () I have attached a "thread apply all where" that shows all the threads I'm loading the core file via "gdb /prod/ruby/bin/ruby core.12345" Where /prod/ruby/bin/ruby is the ruby interpreter the ruby script was using. Attachments: http://www.ruby-forum.com/attachment/6139/gdb.where.txt -- Posted via http://www.ruby-forum.com/.