Ok, got it to run with (had to septate arguments with --):
sudo chroot . usr/bin/qemu-arm-static -g -- DISTRHO-
Ports/libs/lv2_ttl_generator DISTRHO-Ports/bin/lv2/TAL-Filter-2.lv2/TAL-
Filter-2.so
When running I can see two processes:
root 31993 0.0 0.0 86556 4696 pts/9 S+ 15:06 0:00 sudo chroot .
usr/bin/qemu-arm-static -g -- DISTRHO-Ports/libs/lv2_ttl_generator
DISTRHO-Ports/bin/lv2/TAL-Filter-2.lv2/TAL-Filter-2.so
root 31994 0.0 0.0 4240444 9592 pts/9 Rl+ 15:06 0:00
usr/bin/qemu-arm-static -g -- DISTRHO-Ports/libs/lv2_ttl_generator
DISTRHO-Ports/bin/lv2/TAL-Filter-2.lv2/TAL-Filter-2.so
I can attach to the pid using something like this:
sudo gdb -p $(ps aux | grep usr/bin/qemu-arm-static | grep -v grep |
grep -v chroot | awk '{ print $2 }')
When I continue I get:
Attaching to process 32519
[New LWP 32520]
0x00000000607a0973 in ?? ()
(gdb) c
Continuing.
Thread 1 "qemu-arm-static" received signal SIGABRT, Aborted.
0x00000000601786cd in ?? ()
The other process I can get with removing "-v" chroot so:
...
sudo gdb -p $(ps aux | grep usr/bin/qemu-arm-static | grep -v grep |
grep chroot | awk '{ print $2 }')
Reading symbols from /lib/x86_64-linux-gnu/libsystemd.so.0...(no debugging
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/liblzma.so.5...(no debugging symbols
found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/liblz4.so.1...(no debugging
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libgcrypt.so.20...(no debugging
symbols found)...done.
Reading symbols from /lib/x86_64-linux-gnu/libgpg-error.so.0...(no debugging
symbols found)...done.
0x00007f65cfd51bc4 in __GI___poll (fds=0x560bc6fe3040, nfds=2, timeout=-1) at
../sysdeps/unix/sysv/linux/poll.c:29
29 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory.
(gdb)
I think the first one is the interesting run, but being verbose.
Any tips on adding symbols?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1776478
Title:
Getting qemu: uncaught target signal 6 when running lv2 plugin cross-
compilation
Status in QEMU:
New
Bug description:
Hey,
I am part of the Zynthian team and we use qemu-arm-static to cross compile
lv2 audio plugins.
When running a compilation of DISTRHO-Ports we get:
lv2_ttl_generator: pthread_mutex_lock.c:81: __pthread_mutex_lock: Assertion
`mutex->__data.__owner == 0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
./scripts/generate-ttl.sh: line 27: 16524 Aborted $GEN ./$FILE
Makefile:62: recipe for target 'gen_lv2' failed
make[1]: *** [gen_lv2] Error 134
make[1]: Leaving directory '/home/pi/zynthian-sw/plugins/DISTRHO-Ports'
Makefile:104: recipe for target 'lv2' failed
make: *** [lv2] Error 2
lv2_ttl_generator source is here:
https://github.com/DISTRHO/DISTRHO-Ports/tree/master/libs/lv2-ttl-generator
The command that is ruining is
lv2_ttl_generator ./TAL-Filter-2.so
And ./TAL-Filter-2.so source is here:
https://github.com/DISTRHO/DISTRHO-Ports/tree/master/ports/tal-filter-2/source
Is there a way to debug what is going on?
This runs fine on a Raspberrypi which is armv7
A workaround would also help.
Bug in Zynthian:
https://github.com/zynthian/zynthian-sys/issues/59
Bug in DISTRHO-Ports:
https://github.com/DISTRHO/DISTRHO-Ports/issues/29
Using qemu-arm-static version from master from two days ago:
qemu-arm version 2.12.50 (v2.12.0-1182-ga7a7309ca5-dirty), commit:
a7a7309ca52c327c6603d60db90ae4feeae719f7
Also saw this in qemu-arm version 2.12.0 (Debian 1:2.12+dfsg-3)
Thanks,
Guy
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1776478/+subscriptions
