blob: 7404c9e116e47579ba45fdb8a9d4a8010e4de13c (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, so I'm trying to figure out whether this bug report is user-mode or system-mode related. Let me break down the information given.
The issue is that when running a simple PulseAudio application under QEMU's user mode (qemu-x86_64), it crashes with a segmentation fault. The user provided a test program that uses pulseaudio-simple and compiles and runs fine natively but crashes under QEMU. They also mentioned that compiling PulseAudio in debug mode caused an assertion failure in pa_mutex_unlock, which relates to futex system calls.
So, the problem occurs when using QEMU's user emulator (qemu-x86_64) to run a binary. This suggests it's related to how QEMU handles user-mode emulation. The application is crashing due to issues with PulseAudio, specifically in its threading or locking mechanisms, possibly because of incorrect handling of certain system calls by QEMU.
Since the issue arises when running under user-mode QEMU and involves interaction between the emulator and the PulseAudio library (which uses futex for synchronization), it's likely a problem within QEMU's user-mode emulation. Therefore, this should be classified as a 'user' mode bug.
</think>
The issue occurs in QEMU's user-mode emulator when running a PulseAudio application, indicating a problem with how user-mode processes are handled.
**Answer:** user
|