ladcca-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ladcca] Segfault with LASH 0.4.0


From: Josh Green
Subject: [ladcca] Segfault with LASH 0.4.0
Date: Wed, 29 Jun 2005 12:41:24 -0700

Hello, I just now got around to applying the FluidSynth LADCCA patch
present in 0.4.0 to FluidSynth CVS.  In the process of testing I
discovered a bug in ladccad.  If FluidSynth is started, then stopped,
then started again (both times connecting to ladccad), on the second
connect ladccad will crash.  Of note is that this does not occur when
--enable-debug is supplied to configure.  Here is output from gdb:

Starting program: /home/josh/local/bin/ladccad
[Thread debugging using libthread_db enabled]
[New Thread -1211424032 (LWP 30825)]
Connected to JACK server with client name 'LADCCA_Server'
[New Thread -1211954256 (LWP 30829)]
[New Thread -1220346960 (LWP 30830)]
Opened ALSA sequencer with client ID 128
[New Thread -1228739664 (LWP 30831)]
Listening for connections
[New Thread -1237267536 (LWP 30838)]
[New Thread -1245660240 (LWP 30839)]
Created project project-1 in
directory /home/josh/audio-projects/project-1
Added client 4ea8bb28-e55a-4a16-82c9-1115a9b9c3dd of class fluidsynth to
project project-1
Client 4ea8bb28-e55a-4a16-82c9-1115a9b9c3dd removed from project
project-1
Project project-1 removed
cca_lookup_peer_info: could not get peer address: Bad file descriptor
cca_lookup_peer_info: could not get peer address: Bad file descriptor

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1237267536 (LWP 30838)]
0xb7d16bb3 in strlen () from /lib/libc.so.6

(gdb) bt full
#0  0xb7d16bb3 in strlen () from /lib/libc.so.6
No symbol table info available.
#1  0x0804bf84 in conn_get_str_id (conn=0x806b628) at conn.c:96
        str_id = 0x0
        str_id_len = 0
        host = 0x0
        port = 0x0
        new_str_id_len = 0
#2  0x0804d5c8 in conn_mgr_accept_connection (conn_mgr=0x805c4b0)
    at conn_mgr.c:399
        conn = (conn_t *) 0x806b628
        ss = {ss_family = 38912, __ss_align = 3084624192,


        ss_len = 3084624192
        err = 0
#3  0x0804defd in conn_mgr_recv_run (data=0x805c4b0) at conn_mgr.c:764
        sockets = {__fds_bits = {8192, 0 <repeats 31 times>}}
        err = 0
        i = 13
        select_timeout = {tv_sec = 0, tv_usec = 683000}
---Type <return> to continue, or q <return> to quit---
#4  0xb7dc297b in start_thread () from /lib/libpthread.so.0
No symbol table info available.
#5  0xb7d61a8a in clone () from /lib/libc.so.6
No symbol table info available.


Note that I left out the complete display of the "ss" variable in frame
#2, since it had some invalid chars that my email program didn't like.

FluidSynth displays this, on the second invocation:
cca_comm_recv_run: recieved unknown event of type 0

Ciao!
        Josh Green

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]