Re: [Help-smalltalk] SEGF in gst_initialize

[Roland Plüss]

> 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.
I can understand that but is it not bad to begin with to cause a SEGF in
the first place? It's just that when my apps cause a SEGF at any place
red flags come up immediatly.

( Side note, smalltalk is now running *thumbsup* using my special hack
to link it into a pure c++ environment )

-- 
Yours sincerely
Plüss Roland

Leader and Head Programmer
- Game: Epsylon ( http://epsylon.rptd.ch/ ,
http://www.moddb.com/games/4057/epsylon )
- Game Engine: Drag(en)gine ( http://dragengine.rptd.ch ,
http://www.moddb.com/engines/9/dragengine )
- Normal Map Generator: DENormGen ( http://epsylon.rptd.ch/denormgen.php )

signature.asc
Description: OpenPGP digital signature