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

[Mark Knecht]

On Thu, 2003-01-23 at 23:11, Josh Green wrote:
> On Thu, 2003-01-23 at 04:26, Mark Knecht wrote:
> > On Thu, 2003-01-23 at 06:36, Josh Green wrote:
> > 
> > > 
> > > P.S. Something else to make sure of is that you don't have any old
> > > versions of libiiwusynth.so.* hanging around. This can cause lots of
> > > weired problems.
> > > 
> > > 
> > How do I look around for this file? Is there a specific path it would be
> > at?
> > 
> 
> It would be in the install prefix of FluidSynth, which it looks like
> from your previous email is /usr/local. So it would be in
> /usr/local/lib. Basically if you see more than one libiiwusynth.so.*
> delete the older one. Or if you are unsure, delete both and do a "make
> install" again for FluidSynth.

Only seemed to be one.

address@hidden lib]$ ls -al
total 7956
drwxr-xr-x    5 root     root         4096 Jan 22 18:29 .
drwxr-xr-x   13 root     root         4096 Nov 24 02:13 ..
drwxr-xr-x    2 root     root         4096 Jan 18 06:01 ardour
-rw-r--r--    1 root     root      1874276 Jan 22 18:29 libiiwusynth.a
-rwxr-xr-x    1 root     root          834 Jan 22 18:29 libiiwusynth.la
lrwxrwxrwx    1 root     root           21 Jan 22 18:29 libiiwusynth.so
-> libiiwusynth.so.1.0.1
lrwxrwxrwx    1 root     root           21 Jan 22 18:29
libiiwusynth.so.1 -> libiiwusynth.so.1.0.1
-rwxr-xr-x    1 root     root       645813 Jan 22 18:29
libiiwusynth.so.1.0.1

> 
> > I'm have tried all of the ideas you had, but none of them are creating a
> > segfault inside of gdb.
> > 
> > I am able to capture a core dump when I run iiwusynth -a jack outside of
> > gdb. Is that worth anything without the back trace fom gdb?
> > 
> 
> 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:

address@hidden mark]$ gdb iiwusynth core.1630
GNU gdb Red Hat Linux (5.2-2)
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details.
This GDB was configured as "i386-redhat-linux"...
Core was generated by `iiwusynth -a jack'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/local/lib/libiiwusynth.so.1...done.
Loaded symbols for /usr/local/lib/libiiwusynth.so.1
Reading symbols from /lib/i686/libm.so.6...done.
Loaded symbols for /lib/i686/libm.so.6
Reading symbols from /usr/lib/libreadline.so.4...done.
Loaded symbols for /usr/lib/libreadline.so.4
Reading symbols from /usr/lib/libncurses.so.5...done.
Loaded symbols for /usr/lib/libncurses.so.5
Reading symbols from /usr/lib/libjack.so.0...done.
Loaded symbols for /usr/lib/libjack.so.0
Reading symbols from /usr/lib/libasound.so.2...done.
Loaded symbols for /usr/lib/libasound.so.2
Reading symbols from /lib/i686/libpthread.so.0...done.
Loaded symbols for /lib/i686/libpthread.so.0
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/i686/libc.so.6...done.
Loaded symbols for /lib/i686/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2
#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)


> 
> Should do it. You may have to hit enter a couple times when gdb starts
> up if there are a lot of symbols (gdb will prompt you, so you'll know).
> 
> > Thanks,
> > Mark
> 
> Cheers.
>       Josh Green
>