blob: b18905546b18f03d30915bd59bc0c8aea2621265 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
|
<think>
Okay, so I'm trying to help classify this bug report related to QEMU. Let me read through it carefully.
The user is running Ubuntu Precise AMD64 as the host and has set up a Debian Testing armhf guest using debootstrap with qemu-armhf-static. When they enter the chroot environment and run 'ps', it causes a segmentation fault. The error message mentions that the procps-ng version 3.3.4 caught the signal 11 (SEGV).
The user suspects that the issue might be in QEMU rather than procps because they couldn't find an existing bug report for procps. They also mention that this isn't just a minor inconvenience; it affects package installations via apt-get, which is pretty critical.
Now, looking at the possible categories: instruction, syscall, or runtime.
- **Instruction**: This would be if there was an error in how something was done, like a faulty command or procedure.
- **Syscall**: If the issue were related to system calls going wrong when interacting with the kernel.
- **Runtime**: For issues that occur during execution but aren't necessarily due to instructions or syscalls.
In this case, 'ps' is crashing inside the chroot. Since it's using qemu-armhf-static, which emulates an ARM environment on an x86_64 host, any issues here are likely related to how QEMU handles system calls or executes processes in the guest environment. The segmentation fault suggests a problem in memory access or instruction execution within the emulator.
I think this falls under **runtime** because it's happening while running 'ps' inside the chroot, which is part of the runtime environment provided by QEMU. It's not a faulty user instruction but rather an issue during normal operation.
</think>
The bug report describes a segmentation fault occurring when executing `ps` in a QEMU-emulated environment. This issue happens at runtime within the emulated guest system.
runtime
|