blob: 36fad84ae63666851cdb2b6bd96fc5e8a0569c3f (
plain) (
blame)
1
2
3
4
5
6
7
|
<think>
Okay, let me try to figure out how to categorize this bug report. The user is having trouble with strace not showing execve syscalls when using QEMU in mipsel user mode. They mentioned that in older versions like 4.2.1, it worked, but in 6.2.0 and newer, it doesn't. The problem seems to be that the safe_execve function isn't returning, so the strace output for execve isn't completed.
Hmm. The key here is that the issue is specifically with the execve syscall not being traced properly. The user is using strace to monitor system calls, and execve is missing from the output. The problem appears to be related to how QEMU handles the execve syscall in user mode, particularly in newer versions. Since execve is a system call, and the issue is about tracing it, this seems like a syscall-related problem. The fact that older versions worked suggests a regression in how the syscall is handled or traced in newer QEMU versions. The user's configuration and build steps are correct, so it's not an instruction or runtime error. The core of the issue lies in the syscall tracing mechanism within QEMU. So the category should be 'syscall'.
</think>
syscall
|