blob: ad46a14bbb83480d123630493662aeb4c8fd1782 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, I need to classify this bug report as either user-mode or system-mode related. Let me go through the details provided.
The user is using qemu-4.2.0 configured for arm-linux-user, which indicates they're running in user mode emulation. They're cross-compiling an old version of V8 and encountered a segmentation fault when running under qemu-arm. The error happens during the execution of a specific command that runs mksnapshot.
Looking at the backtrace from gdb, it points to functions within the TCG (Translation Code Generation) subsystem, specifically in cpu_exec.c and cpu_loop.c. These are part of the user-mode emulation code because they handle CPU loop execution for emulated processes.
The issue occurs when running an application under qemu-arm, which is a user-mode emulator. There's no mention of system-level components like devices, peripherals, or higher privileges, which would be typical in system-mode (like QEMU with KVM).
So, putting it all together, the bug seems to be within the user-mode execution environment of QEMU, as opposed to any hardware emulation aspects.
</think>
user
|