[PD] Gem crash in Trigger Gang Bang patch

Frank Barknecht fbar at footils.org
Tue Sep 7 11:28:16 CEST 2004


Hi,

as I'm a Gem dork, I don't know, at all, why the Trigger Gang Bang
patch keeps crashing at always the same position (after the first 16
bars.) I can however provide a backtrace, maybe this can be a hint: 

wt?!: and hop

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1076242848 (LWP 20958)]
0x4019c44c in mallopt () from /lib/tls/libc.so.6
(gdb) bt
#0  0x4019c44c in mallopt () from /lib/tls/libc.so.6
#1  0x0809b55b in atom_string (a=0x4025eedc, buf=0x2f102f0 <Address 0x2f102f0 out of bounds>, 
    bufsize=1162937064) at m_atom.c:83
#2  0x4050715f in TextBase::textMess () from /usr/lib/pd/extra/Gem.pd_linux
#3  0x405072d0 in TextBase::textMessCallback () from /usr/lib/pd/extra/Gem.pd_linux
#4  0x08099477 in pd_typedmess (x=0x824fae0, s=0x425ffff8, argc=1, argv=0x80ee5b0) at m_class.c:656
#5  0x0809aac7 in outlet_anything (x=0x2f102f1, s=0x81fd750, argc=1, argv=0x80ee5b0) at m_obj.c:385
#6  0x080990c6 in pd_typedmess (x=0x824f704, s=0x425ffff8, argc=1, argv=0x80ee5b0) at m_class.c:740
#7  0x0809c654 in binbuf_eval (x=0x48, target=0x824f704, argc=0, argv=0x0) at m_binbuf.c:578
#8  0x08060ab5 in message_bang (x=0x48) at g_text.c:294
#9  0x0809853f in pd_bang (x=0x48) at m_pd.c:269
#10 0x0809a88b in outlet_bang (x=0x2f102f1) at m_obj.c:323
#11 0x0809861a in bindlist_bang (x=0x48) at m_pd.c:269
#12 0x080994f7 in pd_typedmess (x=0x828bb38, s=0x425ffff8, argc=0, argv=0x80ee5a8) at m_class.c:632
#13 0x0809c654 in binbuf_eval (x=0x48, target=0x828bb38, argc=0, argv=0x0) at m_binbuf.c:578
#14 0x08060ab5 in message_bang (x=0x48) at g_text.c:294
#15 0x0809853f in pd_bang (x=0x48) at m_pd.c:269
#16 0x0809a88b in outlet_bang (x=0x2f102f1) at m_obj.c:323
#17 0x0809853f in pd_bang (x=0x48) at m_pd.c:269
#18 0x0809853f in pd_bang (x=0x48) at m_pd.c:269
#19 0x0809a88b in outlet_bang (x=0x2f102f1) at m_obj.c:323
#20 0x08098567 in pd_float (x=0x48, f=3.54134556e-37) at m_pd.c:274
#21 0x0809a96f in outlet_float (x=0x2f102f1, f=384) at m_obj.c:355
#22 0x0809865e in bindlist_float (x=0x48, f=384) at m_pd.c:274
#23 0x08098567 in pd_float (x=0x48, f=3.54134556e-37) at m_pd.c:274
#24 0x08098567 in pd_float (x=0x48, f=3.54134556e-37) at m_pd.c:274
#25 0x0809a96f in outlet_float (x=0x2f102f1, f=384) at m_obj.c:355
#26 0x080c9153 in pdint_bang (x=0x2f102f1) at x_connective.c:33
#27 0x0809853f in pd_bang (x=0x48) at m_pd.c:269
#28 0x0809a88b in outlet_bang (x=0x2f102f1) at m_obj.c:323
#29 0x080a1066 in m_scheduler () at m_sched.c:357
#30 0x080a40af in sys_main (argc=72, argv=0x81f4838) at s_main.c:263
#31 0x080a78eb in main (argc=72, argv=0x48) at s_entry.c:49
(gdb) 

Any ideas what might cause this? It is using the Debian package of
Gem-0.90 and Pd 0.37

Ciao
-- 
 Frank Barknecht                               _ ______footils.org__




More information about the Pd-list mailing list