blob: cfe170fdb9edbf678279bfda5f60a854cee51424 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I'm looking at this bug report about qemu-aarch64-static segfaulting. The user provided some context where using dh_fixperms and debootstrap --second-stage both cause core dumps. They mentioned that upstream versions have issues but a binary from SUSE's aarch64-1.6 branch works fine, hinting at the problem being fixed with sigprocmask wrapper patches in SUSE's tree.
Looking at the backtrace provided, it starts with a memcpy call leading to a segmentation fault. The stack trace goes through functions related to target setup of sigframes and signals handling. It seems like an issue when setting up signal frames during emulation.
The possible categories are instruction, syscall, or runtime errors. Since the crash is happening during runtime while processing signals, specifically in the signal handling code (signal.c), it's not about a faulty instruction being executed or a syscall error. Instead, it's related to how the emulator handles runtime events like signals and exception frames.
So, this bug falls under 'runtime' because it's an error occurring during normal execution when handling signals.
</think>
The issue occurs during runtime while processing signals, specifically in setting up signal frames.
runtime
|