From: Peter Maydell <peter.maydell@linaro.org>
To: Bug 1776478 <1776478@bugs.launchpad.net>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Bug 1776478] Re: Getting qemu: uncaught target signal 6 when running lv2 plugin cross-compilation
Date: Wed, 25 Jul 2018 18:27:55 +0100 [thread overview]
Message-ID: <CAFEAcA8RosX691BsqQKr+GNWVtCtKmygj+UjRbNbHSak3BUSdQ@mail.gmail.com> (raw)
In-Reply-To: <153253867764.12274.1892143119027483590.malone@gac.canonical.com>
On 25 July 2018 at 18:11, guysoft <guysoft@gmail.com> wrote:
> target: No such file or directory.
> /tmp/mount/remote: No such file or directory.
> (gdb) file DISTRHO-Ports/libs/lv2_ttl_generator
> Reading symbols from DISTRHO-Ports/libs/lv2_ttl_generator...(no debugging symbols found)...done.
> (gdb) file DISTRHO-Ports/bin/lv2/TAL-Filter-2.lv2/TAL-Filter-2.so
> Reading symbols from DISTRHO-Ports/bin/lv2/TAL-Filter-2.lv2/TAL-Filter-2.so...(no debugging symbols found)...done.
These files seem to have no debug symbols. Compiling them
with debug might help (or might not).
thanks
-- PMM
next prev parent reply other threads:[~2018-07-25 17:28 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 [this message]
2021-05-02 5:37 ` Thomas Huth
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=CAFEAcA8RosX691BsqQKr+GNWVtCtKmygj+UjRbNbHSak3BUSdQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=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).