blob: 028116ce4f8f5441b453119ea03742b8b2725285 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I'm trying to classify this bug report for QEMU. The issue mentioned is about the 'waitid' function leaving the target siginfo uninitialized when info.si_pid is zero. Hmm, waitid is a system call in Linux used to wait for a child process and get information about its termination.
So, the problem here seems to be related to how the siginfo structure is handled after using waitid. If si_pid is zero, that might mean the process ID isn't being set correctly or perhaps it's indicating some error condition where the info isn't properly initialized.
Since the issue revolves around a system call (waitid) and its handling of the siginfo structure, I think this falls under a syscall category. The bug isn't about an instruction in code being wrong, nor is it a runtime error that occurs elsewhere during execution—it's specifically about how the system call interacts with data structures.
Therefore, the category should be 'syscall'.
</think>
The bug report discusses an issue related to the waitid system call and its handling of siginfo. Therefore, it falls under the syscall category.
sys
|