From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1529226] Re: qemu-i386-user on 32-bit Linux: uncaught target signal 11
Date: Fri, 17 Jun 2016 15:45:28 -0000 [thread overview]
Message-ID: <20160617154528.2703.60950.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20151225114312.18411.84061.malonedeb@wampee.canonical.com
Hi; thanks for this bug report. Could you provide instructions for how
to reproduce this bug, please?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1529226
Title:
qemu-i386-user on 32-bit Linux: uncaught target signal 11
Status in QEMU:
New
Bug description:
Even though the command I'm trying to run (a wrapper script for
qemu-i386-user running rustc, the rust compiler) produces the
expected compiled output, the build process is interrupted:
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
i686-unknown-linux-gnu/stage0/bin/rustc: line 1: 7474 Segmentation fault /usr/local/bin/qemu-i386 -cpu qemu32 /home/petevine/stage0/rustc.bin -C target-cpu=pentium2 -L /home/petevine/unpacked/rust-master/i686-unknown-linux-gnu/stage0/lib/rustlib/i686-unknown-linux-gnu/lib/ "$@"
make: *** [i686-unknown-linux-gnu/stage0/lib/rustlib/i686-unknown-linux-gnu/lib/stamp.rustc_back] Error 139
The stamp file is not being created so this could be about forking
bash after finishing the wrapper script.
Qemu was compiled from the latest git source.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1529226/+subscriptions
next prev parent reply other threads:[~2016-06-17 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-25 11:43 [Qemu-devel] [Bug 1529226] [NEW] qemu-i386-user on 32-bit Linux: uncaught target signal 11 PeteVine
2016-06-17 15:45 ` Peter Maydell [this message]
2016-06-18 0:53 ` [Qemu-devel] [Bug 1529226] " PeteVine
2016-06-18 11:42 ` PeteVine
2019-04-16 7:16 ` Thomas Huth
2019-04-16 7:16 ` Thomas Huth
2019-06-16 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=20160617154528.2703.60950.malone@chaenomeles.canonical.com \
--to=peter.maydell@linaro.org \
--cc=1529226@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).