[Top][All Lists]

[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: Peter Maydell
Subject: [Qemu-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() failed
Date: Mon, 08 Jul 2019 15:22:32 -0000

The fix for this bug is now in master and will be in QEMU 4.1.

** Changed in: qemu
       Status: In Progress => Won't Fix

** Changed in: qemu
       Status: Won't Fix => Fix Committed

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  cpu_exec: Assertion !have_mmap_lock() failed

Status in QEMU:
  Fix Committed

Bug description:

  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:
  cmd  lib  proc_ptr_51.exe

  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

  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:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]