From: Launchpad Bug Tracker <1856837@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1856837] Re: qemu 4.2.0 arm segmentation fault with gcc 9.2
Date: Fri, 02 Jul 2021 04:17:26 -0000 [thread overview]
Message-ID: <162519944676.31921.15422663333373285646.malone@loganberry.canonical.com> (raw)
In-Reply-To: 157666594314.15384.3778802807711797985.malonedeb@wampee.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1856837
Title:
qemu 4.2.0 arm segmentation fault with gcc 9.2
Status in QEMU:
Expired
Bug description:
As discussed with f4bug yesterday on IRC here comes the bug
description.
I'm building/configured qemu-4.2.0 on an x86_64 (gcc (Debian
6.3.0-18+deb9u1) 6.3.0 20170516) with target-list "arm-softmmu,arm-
linux-user" and debug enabled. I use the arm-linux-user variant,
"qemu-arm".
Then i'm trying to cross-compile (arm gcc) an old version of googles
v8 (as i need this version of the lib for binary compatibility) which
uses qemu during build.
It worked with gcc 5.4.0 but not with 9.2.0. I also tried with 6.5.0,
7.4.0 and 8.3.0 but those are also causing the same segmentation
fault.
The executed command wich breaks qemu is:
qemu-arm /tmp/build/out/arm.release/mksnapshot.arm --log-snapshot-
positions --logfile
/tmp/build/out/arm.release/obj.host/v8_snapshot/geni/snapshot.log
--random-seed 314159265 /tmp/build/out/arm.release/obj.host/v8_snap
The printed error message is:
ARMv7=1 VFP3=1 VFP32DREGS=1 NEON=0 SUDIV=0 UNALIGNED_ACCESSES=1 MOVW_MOVT_IMMEDIATE_LOADS=0 USE_EABI_HARDFLOAT=1
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Calling qemu with gdb gives the following information:
Thread 1 "qemu-arm" received signal SIGSEGV, Segmentation fault.
0x0000555555d63d11 in static_code_gen_buffer ()
and
(gdb) bt
#0 0x0000555555d63d11 in static_code_gen_buffer ()
#1 0x0000555555628d58 in cpu_tb_exec (itb=<optimized out>, cpu=0x555557c33930) at
/tmp/build/qemu/accel/tcg/cpu-exec.c:172
#2 cpu_loop_exec_tb (tb_exit=<synthetic pointer>, last_tb=<synthetic pointer>, tb=<optimized out>,
cpu=0x555557c33930) at /tmp/build/qemu/accel/tcg/cpu-exec.c:618
#3 cpu_exec (cpu=cpu@entry=0x555557c2b660) at /tmp/build/qemu/accel/tcg/cpu-exec.c:731
#4 0x0000555555661578 in cpu_loop (env=0x555557c33930) at /tmp/build/qemu/linux-user/arm/cpu_loop.c:219
#5 0x00005555555d6d76 in main (argc=<optimized out>, argv=<optimized out>, envp=<optimized out>) at /tmp/build/qemu/linux-user/main.c:865
Calling qemu-arm with debug switch "-d in_asm,int,op_opt" shows the
log in the attached file.
Thanks for any hints!
Fabian
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1856837/+subscriptions
prev parent reply other threads:[~2021-07-02 4:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 10:45 [Bug 1856837] [NEW] qemu 4.2.0 arm segmentation fault with gcc 9.2 Fabian Godehardt
2019-12-19 15:01 ` [Bug 1856837] " Peter Maydell
2020-01-06 7:39 ` Fabian Godehardt
2020-01-20 15:26 ` Peter Maydell
2020-01-28 7:28 ` Fabian Godehardt
2021-05-02 18:15 ` Thomas Huth
2021-07-02 4:17 ` Launchpad Bug Tracker [this message]
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=162519944676.31921.15422663333373285646.malone@loganberry.canonical.com \
--to=1856837@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.