[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() fai
From: |
Thomas Huth |
Subject: |
[Qemu-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() failed |
Date: |
Fri, 16 Aug 2019 04:58:35 -0000 |
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=52ba13f042714c4086416
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1832353
Title:
cpu_exec: Assertion !have_mmap_lock() failed
Status in QEMU:
Fix Released
Bug description:
Hi,
I have isolated a testcase from the GCC testsuite (actually gfortran,
test proc_ptr_51.f90) which produces tons of:
qemu-arm: /home/christophe.lyon/src/qemu/accel/tcg/cpu-exec.c:701:
cpu_exec: Assertion `!have_mmap_lock()' failed.
including with master qemu as of today.
I'm attaching a tarball containing:
qemu-assert:
cmd lib proc_ptr_51.exe
qemu-assert/lib:
ld-linux-armhf.so.3 libc.so.6 libgcc_s.so.1 libgfortran.so.5 libm.so.6
where cmd is the basic command used to launch the test & reproduce the
failure.
Note that the test or the generated may actually be buggy: I have
reported failures on native aarch64 and arm machines. Yet, qemu should
not fail with a loop of asserts.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1832353/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Qemu-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() failed,
Thomas Huth <=