blob: 1431a9efa908b647f849c68c883447fabcf5906f (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
|
<think>
Okay, so I need to figure out how to classify this bug report as either 'instruction', 'syscall', or 'runtime'. Let's break it down step by step.
The problem occurs when running a 32-bit program on a 64-bit host using qemu-user-static. The issue is with the `mremap` function in the musl-libc library. Specifically, when `pthread_getattr_np` is called, it enters an infinite loop because `mremap` keeps failing with `EFAULT`.
Looking at the code snippet provided, the while loop in `pthread_getattr_np.c` uses `mremap` and checks if it returns `MAP_FAILED` due to `ENOMEM`. The problem arises when `mremap` fails for a different reason, causing the loop to repeat indefinitely.
The key points here are:
1. It's related to a system call (`mremap`).
2. The failure is due to an error condition (`EFAULT`) that isn't properly handled.
3. This issue happens at runtime when the program is executed under qemu-user-static.
Since `mremap` is a syscall, and the problem stems from how it's being handled or called, the category should be 'syscall'. It's not about an incorrect instruction or a general runtime error but specifically about a syscall failing unexpectedly.
</think>
The bug report involves an issue with the `mremap` system call causing unexpected behavior when running under qemu-user-static. The problem arises from how the syscall is being handled, leading to an infinite loop.
sys
|