[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1903833] [NEW] User mode qemu-aarch: SIGGSEGV signal handler works
From: |
Boris |
Subject: |
[Bug 1903833] [NEW] User mode qemu-aarch: SIGGSEGV signal handler works wrong |
Date: |
Wed, 11 Nov 2020 10:19:23 -0000 |
Public bug reported:
I have a user mode qemu-aarch issue. Program with SIGSEGV signal handler works
wrong under qemu-aarch:
once the progam handles the SEGV signal, qemu marks the program's page
protected, and signal handler gets SEGV on each subsequent memory access
instruction within a program.
The issue is reproduced on WSL Ubuntu 20.04 under Windows 10, qemu-aarch64
version 5.1.50
The issue is also reproducible on the latest upstream qemu-aarch build.
The following workaround disables mprotect call and fixes the issue:
https://github.com/BorisUlasevich/qemu/commit/3063d9a64f8395185d65c6b6710d28ee92cd8be5
The issue can be reproduced on OpenJDK which reports SIGSEGV immediately
after start. The small reproducer program is attached.
** Affects: qemu
Importance: Undecided
Status: New
** Attachment added: "minimal reproducers for the issue"
https://bugs.launchpad.net/bugs/1903833/+attachment/5433337/+files/test.cpp
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1903833
Title:
User mode qemu-aarch: SIGGSEGV signal handler works wrong
Status in QEMU:
New
Bug description:
I have a user mode qemu-aarch issue. Program with SIGSEGV signal handler
works wrong under qemu-aarch:
once the progam handles the SEGV signal, qemu marks the program's page
protected, and signal handler gets SEGV on each subsequent memory access
instruction within a program.
The issue is reproduced on WSL Ubuntu 20.04 under Windows 10, qemu-aarch64
version 5.1.50
The issue is also reproducible on the latest upstream qemu-aarch build.
The following workaround disables mprotect call and fixes the issue:
https://github.com/BorisUlasevich/qemu/commit/3063d9a64f8395185d65c6b6710d28ee92cd8be5
The issue can be reproduced on OpenJDK which reports SIGSEGV
immediately after start. The small reproducer program is attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1903833/+subscriptions
- [Bug 1903833] [NEW] User mode qemu-aarch: SIGGSEGV signal handler works wrong,
Boris <=