Re: gEDA-user: Another gschem crasher

[David Carr <dc@xxxxxxxxx>]

Carlos,

Thanks for your reply.  I wasn't aware that gEDA was using a 
bugtracker.  In the bugtracker it suggests to export 
G_SLICE=always-malloc prior to running gschem.  I can confirm that is 
works around the problem.

Thanks for your time Carlos,
David Carr

Carlos Nieves Ãnega wrote:
> Hi David,
>
> El mar, 16-05-2006 a las 23:21 -0500, David Carr escribiÃ:
>   
> > I just stumbled upon another crasher.
> >
> > Steps to reproduce:
> > Run gschem: gschem adc.sch  (Note that this is a different adc.sch than 
> > before)
> > Select the main IC and all of its surrounding signals
> > Hit delete.
> >
> > This causes a segfault for me.
> >
> > Backtrace:
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread -1219090752 (LWP 17763)]
> > 0xb7b501b3 in g_slice_get_config () from /usr/lib/libglib-2.0.so.0
> > (gdb) bt
> > #0  0xb7b501b3 in g_slice_get_config () from /usr/lib/libglib-2.0.so.0
> > #1  0xb7b504cd in g_slice_get_config () from /usr/lib/libglib-2.0.so.0
> > #2  0xb7b508ab in g_slice_free_chain_with_offset () from 
> > /usr/lib/libglib-2.0.so.0
> > #3  0xb7b387ff in g_list_free () from /usr/lib/libglib-2.0.so.0
> >     
>
> This bug and the previous one you reported are related to the newly
> slice allocator introduced into the glib library. It is already reported
> at: 
>
> http://sourceforge.net/tracker/index.php?func=detail&aid=1455979&group_id=161080&atid=818426
>
> We have to get some time to fix it...
>
> Regards,
>
> Carlos
>