blob: 24f32747151da7fce9b0b543a0bdfa3b863830f5 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
|
<think>
Okay, so I'm trying to figure out how to classify this bug report about QEMU. The user has set up a powerpc chroot on a Debian system using debootstrap and copied in a statically linked qemu-ppc-static binary. When they run certain commands inside the chroot, like 'ls' after changing directory to home, it fails with an assertion error related to signal handling.
The problem occurs during runtime when executing specific commands within the chroot environment. The error message mentions an assertion failure in the setup_frame function of signal.c. This suggests that there's something wrong with how signals are being handled or set up by QEMU when running on a 64-bit host for a powerpc target.
I think this isn't about incorrect instructions because the issue arises during execution, not necessarily from compiling faulty code. It also doesn't seem to be directly related to a specific syscall failing; it's more about how the environment is handling signals. So the error occurs at runtime when trying to execute these commands, which makes me think it falls under 'runtime' errors.
So, putting it all together, the bug seems to be happening during runtime due to incorrect signal frame setup in the QEMU user emulator.
</think>
runtime
|