[PD-dev] Segfault without messages

[Brian Neltner]

Thanks for the info Claude,

Here is what gdb eventually spit out.

I read the documentation page, but I'm afraid I don't really see what I
should do from that. Is it trying to do a trace with #0 being the
immediate call that crashed, while #1 is what called #0 and #2 called #1
and so on? If so, it seems that maxlib history is what is causing the
problem.

Sorry, I wish I knew more about programming...
Brian

On Sat, 2010-10-23 at 21:13 +0100, Claude Heiland-Allen wrote:
> On 23/10/10 20:36, Brian Neltner wrote:
> > I have attached the offending script.
> 
> Seems quite simple, but I don't have pd-extended and miss the required 
> libraries to test.
> 
> > pd gui; pd process exited
> > Segmentation Fault
> >
> > Not very useful...
> 
> You could try 'gdb' or 'valgrind' to get more useful output.
> 
> $ gdb --args pd-extended blah blah
>  > run
> Segmentation Fault
>  > bt
> (tells you where the error is, hopefully)
>  > quit
> $
> 
> See also:
> 
> http://puredata.info/docs/developer/DebuggingPdExternals
> 
> 
> Claude

-------------- next part --------------
Program received signal SIGSEGV, Segmentation fault.
0xb6c1bf13 in ?? () from /usr/lib/pd-extended/extra/maxlib/history.pd_linux
(gdb) bt
#0  0xb6c1bf13 in ?? () from /usr/lib/pd-extended/extra/maxlib/history.pd_linux
#1  0x080b92d7 in outlet_float (x=0x85b6cc8, f=6.63301707e-34) at m_obj.c:397
#2  0x080b92d7 in outlet_float (x=0x85b6c48, f=23.1156178) at m_obj.c:397
#3  0x08059b12 in env_tilde_tick (x=0x85e66c8) at d_ctl.c:671
#4  0x080c3a3c in sched_tick (next_sys_time=34468536320) at m_sched.c:374
#5  0x080c3e83 in m_pollingscheduler () at m_sched.c:487
#6  m_mainloop () at m_sched.c:563
#7  0x080c6b49 in sys_main (argc=4, argv=0xbffff484) at s_main.c:304
#8  0x080ce82b in main (argc=4, argv=0xbffff484) at s_entry.c:32
(gdb)