blob: 6d0498426bc8163e2849c854cb8f6d4d5b2c1444 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
|
<think>
Okay, let's see. The user is reporting a crash in QEMU's linux-user mode when running a specific test case from the GCC libgomp testsuite. The error message mentions a GLib critical error and an assertion failure in QOM's object_get_canonical_path_component. The backtrace points to the crash happening during a do_fork() call, which is part of the syscall handling in QEMU.
Looking at the categories provided: instruction, syscall, runtime. The problem seems to be related to the do_fork() syscall, which is handled in the linux-user mode. The crash occurs during the execution of the fork system call, specifically when creating a CPU in the child process. The error is in the QOM (QEMU Object Model) code when trying to get the canonical path component, which shouldn't be reached.
Since the issue is triggered during a system call (fork) and the backtrace shows it's in the syscall handling code (do_fork), the category should be syscall. The problem isn't about a specific instruction being wrong, nor is it a general runtime error—it's specifically tied to the handling of the fork syscall in QEMU's user mode.
</think>
syscall
|