summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2-tmp/output/permissions/1903833
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/permissions/1903833')
-rw-r--r--results/classifier/deepseek-2-tmp/output/permissions/190383312
1 files changed, 0 insertions, 12 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/permissions/1903833 b/results/classifier/deepseek-2-tmp/output/permissions/1903833
deleted file mode 100644
index bc5f97ff..00000000
--- a/results/classifier/deepseek-2-tmp/output/permissions/1903833
+++ /dev/null
@@ -1,12 +0,0 @@
-
-User mode qemu-aarch: SIGGSEGV signal handler works wrong
-
-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.
\ No newline at end of file