blob: c127b9b12a02d3a2a58e822b275aa0b4fe9a0e89 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
|
<think>
Alright, I need to classify this bug report for QEMU as either "instruction", "syscall", or "runtime". Let's break down what the issue is.
The user reported that running qemu-x86_64-static three times in a row with /bin/true causes a segmentation fault. The error message mentions an internal SIGSEGV from QEMU, which points to an access error at a specific memory address.
I remember that SIGSEGV usually indicates a problem accessing memory that the program isn't allowed to touch. In this case, it's happening within the QEMU process itself when it's trying to emulate another instance of itself multiple times.
Looking at the possible categories:
- "Instruction" would involve a specific CPU instruction causing issues, but there's no mention here of any particular instruction failing.
- "Syscall" relates to errors with system calls, but the problem seems more internal to QEMU rather than an issue with how it interacts with the OS through syscalls.
- "Runtime" covers other runtime errors that don't fall into the first two categories. Since this is a segmentation fault within QEMU's execution when handling multiple instances, it fits under runtime issues.
So, the most appropriate category here is "runtime".
</think>
The bug report describes an internal error (SIGSEGV) occurring during runtime while running multiple instances of QEMU. This doesn't relate to a specific instruction or syscall issue but rather to how QEMU handles its own execution.
runtime
|