[chuck-dev] segfaults galore

smoerk smoerk at gmx.de
Tue Jul 27 05:32:14 EDT 2004

the same here

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

after ../chuck + moe.ck

i'm on linux 2.6.7 with alsa

did anyone test it with 2.4 kernel?

(i praised chuck too early... :-))

Niklas Werner wrote:

> On Tue, 27 Jul 2004 12:31, Ge Wang wrote:
>>Hi Niklas!
>>Hmm... I tried this on os x and couldn't seg fault.
>>Did you do a clean build?  does it happen consistently?
> yes and yes. Any other Linux users out there?
>>it is suspicious that GDB points to getconcurrency()...
>>shreds do not use pthreads (obviously, ha).
> Hmm, correct, but those first pthread things are more likely 
> alsa/sound-related, and they are only SIG32, (other programs run in gdb 
> receive the same signals, but run fine afterwards)
>>it could be a synchronization bug in the server code
>>and the VM.
> so? What can we do?

More information about the chuck-dev mailing list