[iiwusynth-devel] Re: [Swami-devel] iiwusynth segfault

[Josh Green]

On Thu, 2003-01-23 at 09:31, Mark Knecht wrote:
> > 
> > No information is useful except the back trace :) You can generate the
> > back trace from the core file though (like I mentioned in my previous
> > email). Just:
> > 
> > bash prompt> gdb iiwusynth core
> > 
> > (gdb) bt
> 
> I COMPLETELY misunderstood that step! Sorry!!! The core file has a
> number appended. I thought the gdb command was going to generate the
> core file named core. Anyway, here it is:
> 

No problem.. I forgot to mention that it might have a number tacked onto
it (I think its the PID of the program that died).


> #0  0x40189087 in pthread_mutex_lock () from /lib/i686/libpthread.so.0
> (gdb) bt
> #0  0x40189087 in pthread_mutex_lock () from /lib/i686/libpthread.so.0
> #1  0x4207ad18 in free () from /lib/i686/libc.so.6
> #2  0x40040bb4 in new_iiwu_jack_audio_driver (settings=0x804b3b0,
> synth=0x804c2b0)
>     at iiwu_jack.c:249
> #3  0x400462e5 in new_iiwu_audio_driver (settings=0x804b3b0,
> synth=0x804c2b0)
>     at iiwu_adriver.c:224
> #4  0x08049939 in main (argc=3, argv=0xbffff8f4) at iiwusynth.c:435
> #5  0x42017589 in __libc_start_main () from /lib/i686/libc.so.6
> (gdb)
> 

>From looking at the code it looks like it is a bug in the FluidSynth
jack driver. I think I fixed it. I checked it into FluidSynth CVS. Also,
I improved some other things with the filter turn off optimization and
made the synthesis loop more tolerant to smaller loops.
Let me know if this does or does not fix your problem. Cheers.
        Josh Green