On 07/21/2017 11:28 AM, Max wrote: > On 2017년 07월 21일 07:43, IOhannes m zmölnig wrote: >> On 07/20/2017 10:40 PM, Max wrote: >>> >>> >>> Thread 3 "pd" received signal SIGSEGV, Segmentation fault. >>> [Switching to Thread 0x7ffff7eb1700 (LWP 21699)] >>> 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 >>> (gdb) bt >>> #0 0x00007ffff78b8f96 in ?? () from >>> /usr/lib/x86_64-linux-gnu/libjack.so.0 >>> #1 0x00007ffff78b99c5 in ?? () from >>> /usr/lib/x86_64-linux-gnu/libjack.so.0 >>> #2 0x00007ffff7893fc8 in ?? () from >>> /usr/lib/x86_64-linux-gnu/libjack.so.0 >>> #3 0x00007ffff78bbb6a in ?? () from >>> /usr/lib/x86_64-linux-gnu/libjack.so.0 >>> #4 0x00007ffff78b6aa0 in ?? () from >>> /usr/lib/x86_64-linux-gnu/libjack.so.0 >>> #5 0x00007ffff766c6ba in start_thread (arg=0x7ffff7eb1700) at >>> pthread_create.c:333 >>> #6 0x00007ffff6e953dd in clone () at >>> ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 >>> >>> is that helpful or should I try one of these options? >> >> >> no, it's not helpful :-( >> please install the debug package(s) for libjack, >> and read the section about backtraces for multithreaded programs. > > I see. > > > > > (gdb) run > Starting program: /path/pd-0.48-0test3/bin/pd > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [New Thread 0x7ffff7f32700 (LWP 27779)] > [New Thread 0x7ffff7eb1700 (LWP 27781)] > > Thread 3 "pd" received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0x7ffff7eb1700 (LWP 27781)] > 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 > > (gdb) thread apply all bt > Thread 3 (Thread 0x7ffff7eb1700 (LWP 27781)): > #0 0x00007ffff78b8f96 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 > #1 0x00007ffff78b99c5 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 > #2 0x00007ffff7893fc8 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 > #3 0x00007ffff78bbb6a in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 > #4 0x00007ffff78b6aa0 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 > #5 0x00007ffff766c6ba in start_thread (arg=0x7ffff7eb1700) > at pthread_create.c:333 > #6 0x00007ffff6e953dd in clone () > at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 > > Thread 2 (Thread 0x7ffff7f32700 (LWP 27779)): > #0 pthread_cond_wait@@GLIBC_2.3.2 () > at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 > #1 0x00007ffff78b78cc in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 > #2 0x00007ffff78aa828 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 > #3 0x00007ffff78b6aa0 in ?? () from /usr/lib/x86_64-linux-gnu/libjack.so.0 > #4 0x00007ffff766c6ba in start_thread (arg=0x7ffff7f32700) > at pthread_create.c:333 > #5 0x00007ffff6e953dd in clone () > at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109 > > > better? >
somewhat, but not much.
> #1 0x00007ffff78b78cc in ?? () from
/usr/lib/x86_64-linux-gnu/libjack.so.0
this basically tells us, that it is crashing somewhere in libjack, but
the actual place/function in which this is happening is unknown ("??").
i think, you are still missing the debug packages of libjack.
you need to enable to debugsym repository [1], and then install the
"libjack-jackd2-0-dbgsym" package (if libjack-jackd2-0 provides your the
libjack.so).
to you are unsure about the libjack.so provider, install the package
printed out by this:
dpkg -S /usr/lib/x86_64-linux-gnu/libjack.so.0 | sed -e 's|:.*|-dbgsym|'
fgmdsr
IOhannes
[1] https://wiki.ubuntu.com/Debug%20Symbol%20Packages
signature.asc
Description: OpenPGP digital signature
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
