blob: 5faf6ef96d027c6026f94c65979af6d567e3cad7 (
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 and the sh4 architecture. The user is trying to set up a buildd for the Debian sh4 port using QEMU in user emulation mode. They ran into an issue where QEMU throws an error saying "Unsupported syscall: 186".
From what I know, in QEMU, there are two main modes of operation: user-mode and system-mode. User-mode emulation allows running programs compiled for one architecture on another by translating syscalls. System-mode emulates the entire machine, including hardware devices and the OS kernel.
The error message mentions that syscall 186 (which is sigaltstack) isn't implemented for sh4 in QEMU's user-mode code. Looking at the provided code snippet, I see that sigaltstack is only handled for several architectures but not sh4. So the issue here is specific to user-mode because it's about a system call that isn't being translated correctly when running an application (Python 3.4 installation in this case) under emulation.
The user is asking why sigaltstack isn't enabled for sh4 and if it can be added. This falls under improving QEMU's user-mode support for sh4, ensuring that all necessary syscalls are implemented to allow applications to run smoothly without encountering errors.
Since the problem arises when running a userspace application (Python install) in an emulated environment and not during OS boot or hardware emulation, this is definitely a user-mode issue. There's no mention of system-level components like devices or kernel mode, so it doesn't relate to system-mode.
</think>
user
|