blob: d7ee89034af8001dbdd5d605f20a992eca2c2d82 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
|
<think>
Okay, so I'm trying to classify this bug report for QEMU. Let me read through it carefully.
The user is encountering a crash when running qemu-x86_64 on LoongArch. They built a static hello test on an x86_64 machine and then built qemu-x86_64 on LoongArch. When they run the hello program using QEMU, they get a Bus error (core dumped).
The additional information mentions that this started happening since commit 45bf0e7aa648369cf8ab2333bd20144806fc1be3. They also provided logs with various debug options: -d in_asm, op, out_asm, strace.
Looking at the possible categories:
- instruction: Faulty instruction causing issues.
- syscall: Error related to system calls.
- runtime: Other runtime errors.
I need to figure out what's causing the bus error. Bus errors are typically memory-related, like accessing invalid memory or misaligned accesses. Since it's happening on LoongArch when running x86_64 code, maybe QEMU isn't handling some instruction correctly, leading to a bad memory access.
The crash occurs during runtime, not necessarily due to a faulty instruction in the guest or an issue with system calls. It's more about how QEMU is executing instructions on LoongArch.
So I think this falls under 'runtime' because it's an error happening at runtime when running the emulated program, likely related to how QEMU handles certain operations on the host architecture.
</think>
runtime
|