blob: 588e9ea8e9058291206649be270ce031e9e36ac7 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, so I'm trying to figure out whether this problem with cmake crashing on qemu-alpha-user is a user-mode issue or a system-mode issue. Let's break it down.
First, the user is building cmake using Debian unstable for Alpha architecture with qemu-user. They compiled the binary and it crashed with an "Illegal Instruction". The error occurred during the build process when trying to run the initial CMake as part of bootstrapping.
Looking at the command line, they're using g++ to compile various object files into a cmake executable. Then, when running this executable under qemu-alpha-user, it crashes with an illegal instruction. That suggests that the generated code isn't compatible with the Alpha architecture in some way.
Now, thinking about qemu modes: qemu-system is used for full system emulation where the host and guest are different OSes, requiring hardware-level virtualization. Qemu-user, on the other hand, is for user-mode emulation, allowing execution of binaries from another architecture within a chroot environment without needing to run a separate OS kernel.
Since they're using qemu-alpha-user, it's likely that the issue is happening in user mode because the process is running under the host's kernel but executing foreign architecture code. The Illegal Instruction error points towards something wrong with the instruction set—maybe the compiler isn't generating compatible code for Alpha when cross-compiling.
So, considering this, the bug would be related to how qemu-user handles the execution of the cmake binary on the Alpha architecture. It might involve issues with instruction emulation or compatibility layers in user mode. Therefore, it's more about user-mode since they're running a single executable without full system virtualization.
</think>
user
|