1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
|
<think>
Okay, let's see. The user is reporting an issue with QEMU's user mode emulation where using the -L option with a sysroot that includes /proc and /dev causes it to consume all memory and crash. The problem seems to be that QEMU is recursively following symbolic links in /proc, leading to an infinite loop.
First, I need to classify this bug into one of the three categories: instruction, syscall, or runtime.
The user mentions that QEMU is following symbolic links recursively, which is causing an endless loop. The strace output shows that it's getting stuck in the proc filesystem. The suggestion is to modify the add_dir_maybe function in path.c to avoid following symlinks.
Looking at the categories:
- Instruction would be if there's a wrong CPU instruction being executed, which doesn't seem the case here.
- Syscall would involve an error in system calls, maybe like a failed call or incorrect handling. But here, the problem is more about how QEMU processes the directories and symlinks, not the syscall itself failing.
- Runtime errors are other issues occurring during execution, like infinite loops, memory leaks, etc. Since the problem is an infinite loop due to recursive symlink following, this seems like a runtime issue.
The core issue is that during runtime, QEMU's code is entering a loop because it's following symlinks in /proc (which are supposed to be virtual and have their own handling). The code isn't checking for symlinks properly, leading to endless recursion and memory exhaustion. So runtime is the correct category here.
</think>
runtime
|