[Top][All Lists]

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

[Qemu-devel] [Bug 1776478] Re: Getting qemu: uncaught target signal 6 wh

From: Peter Maydell
Subject: [Qemu-devel] [Bug 1776478] Re: Getting qemu: uncaught target signal 6 when running lv2 plugin cross-compilation
Date: Thu, 21 Jun 2018 12:50:07 -0000

Thanks for the repro case; it's on my list of things to look at, but the
gating factor there is that my todo list is several miles long. If you
want to look at it yourself, the first step is probably to run the
program under qemu with qemu's -g option to enable the gdbstub, connect
an arm-aware gdb to it and see if you can get a backtrace out of it.

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  Getting qemu: uncaught target signal 6 when running  lv2 plugin cross-

Status in QEMU:

Bug description:
  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:

  The command that is ruining is
  lv2_ttl_generator ./TAL-Filter-2.so 

  And ./TAL-Filter-2.so source is here:

  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:
  Bug in DISTRHO-Ports:

  Using qemu-arm-static version from master from two days ago:
  qemu-arm version 2.12.50 (v2.12.0-1182-ga7a7309ca5-dirty), commit: 

  Also saw this in qemu-arm version 2.12.0 (Debian 1:2.12+dfsg-3)


To manage notifications about this bug go to:

reply via email to

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