|
From: | Paolo Bonzini |
Subject: | Re: [Help-smalltalk] SEGF in gst_initialize |
Date: | Sat, 31 Oct 2009 23:27:30 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091014 Fedora/3.0-2.8.b4.fc11 Lightning/1.0pre Thunderbird/3.0b4 |
On 10/31/2009 10:19 PM, Roland Plüss wrote:
Trying to figure out why something doesn't work and for this I did gdb on the code. I then noticed a SEGF trigged only inside GDB. Tracing it down I ended up at the gst initialization code somehow causing a SEGF. The code is the following: gst_initialize( NULL, NULL, GST_NO_TTY ); Calling this line causes SEGF only in gdb. Anything wrong here? I used NULL for image and kernel string since in the doc there has been no indication at all what has to go there if anything at all.
NULL is fine.However gst traps SEGVs for its own generational GC. You can use "handle SIGSEGV noprint" at the beginning of your gdb session, or place it in .gdbinit.
Real SEGVs become SIGABRT. Paolo
[Prev in Thread] | Current Thread | [Next in Thread] |