blob: 889fb7c77e7cb77cbde671d26d4724222b33ca02 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
|
The issue described involves problems with signal handling in QEMU's user mode emulation (`qemu-arm-static`), specifically how signals are routed between threads during the termination of Mono applications. The problem causes hangs when running Mono within a chroot environment using `qemu-user-static`.
The bug report mentions that certain signals (like SIGPWR) used during thread termination in Mono are not handled correctly by QEMU, leading to deadlocks or hangs. This affects both Mono and Java applications running under emulation.
The analysis also points out that there's an openSUSE patch available for QEMU that addresses a similar issue related to signal handling and the `SA_RESTART` race condition. Applying this patch resolves the problem in some cases.
This issue is not limited to Debian but impacts the upstream QEMU code as well. The reporter intends to report it to the QEMU project, referencing this bug report for further action.
In terms of classification:
- **Instruction**: No faulty instruction per se; the issue arises from signal handling and thread communication.
- **Syscall**: There might be issues with how syscalls like `futex` or `tgkill` are handled under emulation.
- **Runtime**: The problem occurs during runtime, specifically when applications terminate and signals are processed.
Given that the issue involves incorrect routing of signals at runtime within QEMU's user mode environment, the most appropriate category is:
**runtime**
|