blob: c92b370185a2f0db60c1c1f1a7ebcd271f37c928 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
|
<think>
Okay, so I'm trying to classify this bug report about QEMU's microblaze emulator having an issue with CLONE_THREAD. The user is saying that when they use CLONE_THREAD, the new process starts at the system call instruction instead of the next one, causing threads to multiply and crash quickly.
First, I need to understand what category this falls under: instruction, syscall, or runtime.
The bug is related to how QEMU handles the clone system call specifically for creating threads on microblaze. The problem isn't about executing an incorrect instruction but rather about the behavior of a system call (clone) not working as expected. So it's more than just a faulty instruction; it's about the handling of a syscall.
Looking at the possible categories:
- Instruction: Faulty instructions, which doesn't seem to be the case here.
- Syscall: Errors related to how system calls are handled.
- Runtime: Other runtime errors not covered by the above two.
Since the issue is specifically with the clone syscall and how it's emulated, leading to incorrect thread creation behavior, this falls under 'syscall'.
</think>
The bug report describes an error in handling the CLONE_THREAD system call within QEMU's microblaze emulator. It's a problem with the syscall emulation rather than an instruction or general runtime issue.
sys
|