[PD] [segfault] bug or feature?

Federico xaero at inwind.it
Thu Dec 16 22:34:38 CET 2004

using pd-0.38test13,
take this patch:

if you move numbers with 'compute audio' turned off, everything it's ok.
but if you move the first number (first harmonic) while processing
audio, you (should) get a seg_fault:

#0  0x080a03e7 in sys_queuegui (client=0x8205aa8, glist=0x82085c8,
    at s_inter.c:753
#1  0x08064940 in garray_redraw (x=0x8205aa8) at g_array.c:813
#2  0x080e80d8 in template_float_vec ()
#3  0x080e879c in s_x ()
#4  0x00000203 in ?? ()
#5  0x08067c0c in garray_dofo (x=0xc, npoints=1, dcval=6.72623263e-44, 
    nsin=136338088, vsin=0x8218968, sineflag=512) at g_array.c:934
#6  0x402960b0 in __after_morecore_hook () from /lib/libc.so.6
#7  0x00000018 in ?? ()
#8  0x402960a0 in __after_morecore_hook () from /lib/libc.so.6
#9  0x4012328e in sem_timedwait () from /lib/libpthread.so.0
Previous frame inner to this frame (corrupt stack?)
(gdb) watchdog: signaling pd...
watchdog: signaling pd...

it is a normal behavior, or a bug?


More information about the Pd-list mailing list