From: Thomas Huth <1776478@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1776478] Re: Getting qemu: uncaught target signal 6 when running lv2 plugin cross-compilation
Date: Sun, 02 May 2021 05:37:50 -0000 [thread overview]
Message-ID: <161993387101.3909.3373028472418790542.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 152880770129.26761.1762643804065210181.malonedeb@gac.canonical.com
The QEMU project is currently considering to move its bug tracking to
another system. For this we need to know which bugs are still valid
and which could be closed already. Thus we are setting older bugs to
"Incomplete" now.
If you still think this bug report here is valid, then please switch
the state back to "New" within the next 60 days, otherwise this report
will be marked as "Expired". Or please mark it as "Fix Released" if
the problem has been solved with a newer version of QEMU already.
Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
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:
Incomplete
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
next prev parent reply other threads:[~2021-05-02 5:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 12:48 [Qemu-devel] [Bug 1776478] [NEW] Getting qemu: uncaught target signal 6 when running lv2 plugin cross-compilation guysoft
2018-06-12 14:31 ` [Qemu-devel] [Bug 1776478] " Peter Maydell
2018-06-12 21:25 ` guysoft
2018-06-12 21:30 ` guysoft
2018-06-21 10:54 ` guysoft
2018-06-21 12:50 ` Peter Maydell
2018-07-03 10:47 ` guysoft
2018-07-03 11:27 ` Peter Maydell
2018-07-03 12:14 ` guysoft
2018-07-03 12:56 ` Peter Maydell
2018-07-25 16:28 ` guysoft
2018-07-25 16:45 ` Peter Maydell
2018-07-25 16:51 ` Peter Maydell
2018-07-25 17:11 ` guysoft
2018-07-25 17:27 ` Peter Maydell
2021-05-02 5:37 ` Thomas Huth [this message]
2021-05-02 15:13 ` guysoft
2021-05-02 15:24 ` Peter Maydell
2021-05-03 5:04 ` Paul Guyot
2021-05-03 10:12 ` Peter Maydell
2021-06-18 15:26 ` Thomas Huth
2021-07-03 4:17 ` Launchpad Bug Tracker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161993387101.3909.3373028472418790542.malone@chaenomeles.canonical.com \
--to=1776478@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).