Path: csiph.com!x330-a1.tempe.blueboxinc.net!feeder1.hal-mli.net!weretis.net!feeder4.news.weretis.net!news.cgarbs.de!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: Ruby app core dump on shutdown Date: Wed, 20 Apr 2011 12:29:28 -0500 Organization: Service de news de lacave.net Lines: 34 Message-ID: NNTP-Posting-Host: bristol.highgroove.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Trace: talisker.lacave.net 1303320737 15562 65.111.164.187 (20 Apr 2011 17:32:17 GMT) X-Complaints-To: abuse@lacave.net NNTP-Posting-Date: Wed, 20 Apr 2011 17:32:17 +0000 (UTC) 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: 381941 X-Ml-Name: ruby-talk X-Rubymirror: Yes X-Ruby-Talk: Xref: x330-a1.tempe.blueboxinc.net comp.lang.ruby:3257 So my work computers are down for part of the day I thought I would post a question on a problem that I have been really trying to track down. I have a Ruby/GTK that runs fine through out is operations. But will segv and core on shutdown. This is an OS level core, not a "ruby core" where it gives a Ruby like stack trace. I'm using Ruby 1.9.2p-180(I was on older but tried to uprade) Running on RHEL 5.4. My basic question, I am very familier with debugging core files with gdb on C/C++ applications, but of course the Ruby core files are not as helpful. My gut feel of this problem, is it is in one of my C extensions. But I am wondering how some of you have dealt with really tracking down what is going on. I have the feeling the problem is in garbage collection, since it happens after my last statement in my application. I run in VERBOSE and DEBUG, bot nothing stands out. I've also ran under valgrind, but its really hard to tell what a normal ruby warnings and not. I've even tried to build up a "Good valgrind Ruby suppression" file by making apps that I know have absolutly no problems. So anyone have a tip or pointer or other cool tool to really try to figure out what/where the problem is. This application runs perfectly fine under Ruby 1.8.6, but when I went up to Ruby 1.9.2, made the small neccesary chages, it will crash at shutdown. Thanks -- Posted via http://www.ruby-forum.com/.