On date Tuesday 2009-06-02 14:09:14 +0200, Stefano Sabatini wrote: > Hi all, > > I'm following the fluxus-documentation tutorial, and I can't get > start-audio working without to crash. > > I'm running jackd and a readable client connected to jack with ID > metro1:120_bpm and invoking the command: > (start-audio "metro1:120_bpm" 256 44100) > > which causes fluxus to crash every time, while the metro readable > client got zombified: > > stef...@geppetto ~/s/S/C/libjack> metro --name metro1 -b 120 -d 0.2 -f 4000 > jack_client_thread zombified - exiting from JACK > > and this is fluxus bt: > (gdb) bt > #0 0xb7f9f424 in __kernel_vsyscall () > #1 0xb747e640 in raise () from /lib/i686/cmov/libc.so.6 > #2 0xb7480018 in abort () from /lib/i686/cmov/libc.so.6 > #3 0xb7df9375 in fault_handler () from /usr/lib/libmzscheme3m-4.0.1.so > #4 <signal handler called> > #5 0xb7b36d7f in jack_thread_wait () from /usr/lib/libjack.so.0 > #6 0xb7b36f9e in ?? () from /usr/lib/libjack.so.0 > #7 0x0866aba0 in ?? () > #8 0x00000000 in ?? () > > I'm using fluxus git of the day, but I was getting the very same > problem with an old version (December 2008) of fluxus. > > Suggestions are welcome, the crash seems rooted in libmzscheme3m, so > maybe it could depend by that lib version. > > Any suggestion is welcome.
I forgot to say that I'm using plt scheme 4.0.1-2 in Debian. As an added rebus, if I try to debug fluxus with gdb it always crashes immediately: (gdb) r [Thread debugging using libthread_db enabled] [New Thread 0xb73668e0 (LWP 11199)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb73668e0 (LWP 11199)] 0xb7cc362f in ?? () from /usr/lib/libmzscheme3m-4.0.1.so This only happens when using the debugger to run the process. Regards.
