blob: 2d666e682cf2b7e57d408392faa44f8186399fc4 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
|
<think>
Okay, let's see. The user is experiencing a SIGSEGV when running 'ls' under QEMU on a SunOS 5.8 box emulated in RHEL 6.4. They tried different QEMU versions and even a static binary, but it still segfaults. The GDB backtrace points to static_code_gen_buffer in cpu_tb_exec.
Hmm, the stack trace shows the crash is happening in the code generation buffer. The function cpu_tb_exec is part of QEMU's execution core. The static_code_gen_buffer is likely related to how QEMU translates guest instructions into host code. A segmentation fault here suggests that there's an invalid memory access during this translation or execution process.
Since the problem occurs when executing the guest binary (like 'ls'), it's probably related to how QEMU is handling the instructions from the guest OS. This doesn't look like a syscall issue because the backtrace is in the execution path, not in system call handling. Also, the user mentioned trying different QEMU versions, which might point to a persistent issue in the instruction execution or code generation part of QEMU. So, this seems like an 'instruction' category bug. The faulty instruction translation or execution is causing the segfault.
</think>
instruction
|