[Qemu-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() failed

2019-08-15 Thread Thomas Huth
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:

[Qemu-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() failed

2019-07-16 Thread Richard Henderson
** Changed in: qemu Status: In Progress => Fix Committed -- 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 Comm

[Qemu-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() failed

2019-07-09 Thread Alex Bennée
See series: https://lists.gnu.org/archive/html/qemu- devel/2019-07/msg02189.html -- 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-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() failed

2019-07-09 Thread Alex Bennée
** Changed in: qemu Status: Fix Committed => In Progress -- 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: In Progr

[Qemu-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() failed

2019-07-08 Thread Peter Maydell
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

[Qemu-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() failed

2019-06-13 Thread Richard Henderson
Confirmed. The exact failure mode depends on debugging enabled or not. The test case is "buggy" in the sense that it makes a call to a NULL function pointer, and the failure happens while trying to translate the instructions at address 0. That said, the correct behaviour for QEMU is a SIGSEGV de

[Qemu-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() failed

2019-06-13 Thread Christophe Lyon
It's fairly recent: qemu-arm version 4.0.50 (v4.0.0-1215-ga578cdf-dirty) Copyright (c) 2003-2019 Fabrice Bellard and the QEMU Project developers commit a578cdfbdd8f9beff5ced52b7826ddb1669abbbf Merge: 19735c8 43b3952 Author: Peter Maydell Date: Mon Jun 10 16:09:19 2019 +0100 Merge remote-t

[Qemu-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() failed

2019-06-13 Thread Alex Bennée
** Tags added: arm tcg testcase -- 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: New Bug description: Hi, I have is

[Qemu-devel] [Bug 1832353] Re: cpu_exec: Assertion !have_mmap_lock() failed

2019-06-13 Thread Alex Bennée
What version of qemu where you running? My HEAD is failing in a different way. -- 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 Q