From: Andreas Schwab <schwab@suse.de>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Helge Deller <deller@gmx.de>,
Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Bin Meng <bin.meng@windriver.com>,
qemu-riscv@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [RISC-V] ERROR:../accel/tcg/cpu-exec.c:1028:cpu_exec_setjmp: assertion failed: (cpu == current_cpu)
Date: Mon, 03 Jul 2023 14:42:11 +0200 [thread overview]
Message-ID: <mvm5y71tbdo.fsf@suse.de> (raw)
In-Reply-To: <87h6qli4au.fsf@linaro.org> ("Alex Bennée"'s message of "Mon, 03 Jul 2023 13:08:02 +0100")
On Jul 03 2023, Alex Bennée wrote:
> Andreas Schwab <schwab@suse.de> writes:
>
>> On Jul 03 2023, Andreas Schwab wrote:
>>
>>> This is a regression in 8.0. It causes the testsuite of mold to fail:
>>>
>>> https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/mold/standard/riscv64
>>>
>>> + out/test/elf/riscv64/section-start/exe2
>>> **
>>> ERROR:../accel/tcg/cpu-exec.c:1028:cpu_exec_setjmp: assertion failed: (cpu == current_cpu)
>>> **
>>> ERROR:../accel/tcg/cpu-exec.c:1028:cpu_exec_setjmp: assertion failed: (cpu == current_cpu)
>>
>> This bisects down to commit 86f04735ac ("linux-user: Fix brk() to
>> release pages"). See the attached test case.
>>
>> $ ./qemu-riscv64 ../exe1
>> **
>> ERROR:../qemu/accel/tcg/cpu-exec.c:1027:cpu_exec_setjmp: assertion failed: (cpu == current_cpu)
>> Bail out! ERROR:../qemu/accel/tcg/cpu-exec.c:1027:cpu_exec_setjmp: assertion failed: (cpu == current_cpu)
>> **
>> ERROR:../qemu/accel/tcg/cpu-exec.c:1027:cpu_exec_setjmp: assertion failed: (cpu == current_cpu)
>> Bail out! ERROR:../qemu/accel/tcg/cpu-exec.c:1027:cpu_exec_setjmp: assertion failed: (cpu == current_cpu)
>
> I wonder if applying c5ffd16ba4c8fd fixes this?
No, the error still happens with current master, and reverting
86f04735ac on top of it fixes it.
> I tried to double check with the test case but I can't run it as it's a
> dynamic binary so needs an ld.so.
You can download the glibc package from
<https://download.opensuse.org/ports/riscv/tumbleweed/repo/oss/>.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-07-03 12:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 7:52 [RISC-V] ERROR:../accel/tcg/cpu-exec.c:1028:cpu_exec_setjmp: assertion failed: (cpu == current_cpu) Andreas Schwab
2023-07-03 11:55 ` Andreas Schwab
2023-07-03 12:08 ` Alex Bennée
2023-07-03 12:42 ` Andreas Schwab [this message]
2023-07-04 10:52 ` Andreas Schwab
2023-07-04 12:02 ` Alex Bennée
2023-07-09 6:12 ` Helge Deller
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=mvm5y71tbdo.fsf@suse.de \
--to=schwab@suse.de \
--cc=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=bin.meng@windriver.com \
--cc=deller@gmx.de \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@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).