[chuck-dev] segfaults galore

Niklas Werner bergtroll at gmx.li
Mon Jul 26 19:56:24 EDT 2004


Hi all,

I tried to run chuck (cvs from just an hour ago) in --loop mode. I can 
then add shreds, but if I try to remove one, chuck crashes:

chuck --srate44100 --loop
[chuck](VM): sporking incoming shred: 1...
[chuck](VM): sporking incoming shred: 2...
Segmentation fault


the commands leading to this were:

nick at detritus ~/build/chuck_dev/examples $ chuck + moe.ck
nick at detritus ~/build/chuck_dev/examples $ chuck + larry.ck
nick at detritus ~/build/chuck_dev/examples $ chuck - 2

(gdb) r --srate44100 --loop
Starting program: /usr/bin/chuck --srate44100 --loop
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.

Program received signal SIG32, Real-time event 32.
0x0fc292f4 in pthread_getconcurrency () from /lib/libpthread.so.0
(gdb) c
Continuing.

Program received signal SIG32, Real-time event 32.
0x0fc292f4 in pthread_getconcurrency () from /lib/libpthread.so.0
(gdb) c
Continuing.
[chuck](VM): sporking incoming shred: 1...
[chuck](VM): sporking incoming shred: 2...

Program received signal SIGSEGV, Segmentation fault.
0x0fef277c in mallopt () from /lib/libc.so.6
(gdb) bt
#0  0x0fef277c in mallopt () from /lib/libc.so.6
#1  0x0ffbc5ec in ?? () from /lib/libc.so.6
(gdb)


hmmm, is there a double call to free() going on or anything similar?
 
(Oh, and gentoo on Powerbook Aluminium)

Cheers,

Niklas
--
Computer Music PhD-student
University of Waikato
Hamilton
New Zealand


More information about the chuck-dev mailing list