From: Christophe Lyon <christophe.lyon+launchpad@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1727737] Re: qemu-arm stalls on a GCC sanitizer test since qemu-2.7
Date: Thu, 26 Oct 2017 13:55:16 -0000 [thread overview]
Message-ID: <150902611696.19943.13330574177366822897.malone@soybean.canonical.com> (raw)
In-Reply-To: 150902607840.5143.15937446061017284272.malonedeb@chaenomeles.canonical.com
** Attachment added: "tarball with testcase and libs"
https://bugs.launchpad.net/qemu/+bug/1727737/+attachment/4996620/+files/qemu-bug-gcc-sanitizers.tar.xz
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1727737
Title:
qemu-arm stalls on a GCC sanitizer test since qemu-2.7
Status in QEMU:
New
Bug description:
Hi,
I have noticed that several GCC/sanitizer tests fail with timeout when
executed under QEMU.
After a bit of investigation, I have noticed that this worked with
qemu-2.7, and started failing with qemu-2.8, and still fails with
qemu-2.10.1
I'm attaching a tarball containing:
alloca_instruments_all_paddings.exe : the testcase, and the needed libs:
lib/librt.so.1
lib/libdl.so.2
lib/ld-linux-armhf.so.3
lib/libasan.so.5
lib/libc.so.6
lib/libgcc_s.so.1
lib/libpthread.so.0
lib/libm.so.6
To reproduce the problem:
$ qemu-arm -cpu any -R 0 -L $PWD $PWD/alloca_instruments_all_paddings.exe
returns in less than a second with qemu-2.7, and never with qemu-2.8
Using -d in_asm suggests that the program "almost" completes and qemu seems to stall on:
0x40b6eb44: e08f4004 add r4, pc, r4
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1727737/+subscriptions
next prev parent reply other threads:[~2017-10-26 14:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 13:54 [Qemu-devel] [Bug 1727737] [NEW] qemu-arm stalls on a GCC sanitizer test since qemu-2.7 Christophe Lyon
2017-10-26 13:55 ` Christophe Lyon [this message]
2017-11-06 15:19 ` [Qemu-devel] [Bug 1727737] " Peter Maydell
2017-11-06 15:47 ` Christophe Lyon
2017-11-06 19:48 ` Peter Maydell
2017-11-07 16:53 ` Christophe Lyon
2017-11-08 13:55 ` Christophe Lyon
2017-11-13 13:14 ` Christophe Lyon
2017-11-13 13:18 ` Christophe Lyon
2017-11-13 13:42 ` Peter Maydell
2017-11-13 14:00 ` Christophe Lyon
2017-11-13 14:28 ` Peter Maydell
2017-11-13 14:49 ` Christophe Lyon
2017-11-13 15:13 ` Peter Maydell
2017-11-13 16:29 ` Christophe Lyon
2017-11-13 16:45 ` Peter Maydell
2018-01-13 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=150902611696.19943.13330574177366822897.malone@soybean.canonical.com \
--to=christophe.lyon+launchpad@gmail.com \
--cc=1727737@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.