From: Ayman Khamouma <1863445@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1863445] Re: assertion failed at translate-all.c:2523 with version 3.1.1
Date: Sun, 16 Feb 2020 07:20:25 -0000 [thread overview]
Message-ID: <158183762559.14759.8775333478950152712.malone@soybean.canonical.com> (raw)
In-Reply-To: 158180717472.31124.817430819772209101.malonedeb@wampee.canonical.com
indeed, works fine with 4.2
thanks
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1863445
Title:
assertion failed at translate-all.c:2523 with version 3.1.1
Status in QEMU:
Incomplete
Bug description:
I was trying to debug a userspace binary with radare2 and met the
following assertion in qemu:
```
qemu-mipsel: /builddir/build/BUILD/qemu-3.1.1/accel/tcg/translate-all.c:2523: page_check_range: Assertion `start < ((target_ulong)1 << L1_MAP_ADDR_SPACE_BITS)' failed.
qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x7fd1c11c5987
```
```
# qemu-mipsel --version
qemu-mipsel version 3.1.1 (qemu-3.1.1-2.fc30)
Copyright (c) 2003-2018 Fabrice Bellard and the QEMU Project developers
```
not much to add. seems like qemu is not properly checking for valid
addresses
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1863445/+subscriptions
next prev parent reply other threads:[~2020-02-16 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 22:52 [Bug 1863445] [NEW] assertion failed at translate-all.c:2523 with version 3.1.1 Ayman Khamouma
2020-02-15 22:53 ` [Bug 1863445] " Ayman Khamouma
2020-02-15 22:55 ` Ayman Khamouma
2020-02-15 22:56 ` Ayman Khamouma
2020-02-16 3:46 ` Richard Henderson
2020-02-16 7:20 ` Ayman Khamouma [this message]
2020-02-16 8:59 ` Richard Henderson
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=158183762559.14759.8775333478950152712.malone@soybean.canonical.com \
--to=1863445@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).