blob: 14a17cec55fb14267e7792225d2de4ee5ff4b57b (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, I need to figure out how to classify this segmentation fault issue when compiling an Elixir app on QEMU aarch64 under an x86_64 host. The user provided the error message and their GitHub Actions setup.
First, looking at the error output, it mentions a Segmentation Fault occurring during the compilation of 'nimble_options'. That suggests that some code being executed is accessing memory it shouldn't, causing the crash.
The user mentioned using Alpine 3.18 with OTP25 and JIT enabled. They suspect it's related to QEMU issue 1034, which I think refers to a problem with floating-point operations in the emulator. So maybe the JIT compiler is generating code that interacts poorly with QEMU.
Now, classifying this bug: The options are instruction, syscall, or runtime.
An instruction issue would be if there's an incorrect CPU instruction being used by the program. A syscall error would involve a problem with system calls. But here, it's more about the runtime environment—specifically how the emulator is handling certain operations during execution.
Since the segfault happens while running Elixir code on QEMU, and considering the JIT aspect, this seems like a runtime issue in the emulator rather than an instruction or syscall error.
</think>
runtime
|