blob: ed43429bc90736e55a375dbd2a50fa5dc3c9f601 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
The issue described seems to be related to how QEMU handles certain signals or exceptions during execution when running in a chroot environment on a 64-bit host. The assertion failure points to an issue within the `signal.c` file at line 4341, specifically with setting up the frame for signal handling. This suggests that there might be a problem with how QEMU is translating or emulating system calls (syscalls) and exceptions in this specific setup.
Considering the possible categories provided:
- **Instruction**: This would involve an issue with how individual CPU instructions are handled by QEMU, which doesn't seem to be the case here.
- **Syscall**: Since the error occurs during signal handling, which involves system calls and exception management, this category fits well.
- **Runtime**: While it's a runtime error, the specific cause is related to signal handling, making "syscall" more precise.
Given that the problem arises when interacting with the chroot environment and specifically points to signal handling code, the most appropriate classification is:
**syscall**
|