qemu user mode: rt signals not implemented for sparc guests
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The documentation
<https:/
qemu in user mode supports POSIX signal handling.
Catching SIGSEGV according to POSIX, however, does not work on
ppc, ppc64, ppc64le, s390x, sparc64.
It does work, however, on
aarch64, alpha, arm, hppa, m68k, mips, mips64, sh4.
How to reproduce:
The attached program runs fine (exits with code 0) on
- real hardware Linux/PowerPC64 (in 32-bit and 64-bit mode),
- real hardware Linux/PowerPC64LE,
- qemu-system-s390x emulated Linux/s390x,
- real hardware Linux/SPARC64.
$ gcc -O -Wall testsigsegv.c; ./a.out; echo $?
0
For ppc:
$ powerpc-
$ ~/inst-
$ echo $?
3
For ppc64:
$ powerpc64-
$ ~/inst-
$ echo $?
3
For ppc64le:
$ powerpc64le-
$ ~/inst-
$ echo $?
3
For s390x:
$ s390x-linux-
$ ~/inst-
$ echo $?
3
$ s390x-linux-
$ ~/inst-
$ echo $?
0
So, the test fails here because the Linux/s390x kernel omits the least
significant 12 bits of the fault address in the 'si_addr' field. But
qemu-s390x is not compatible with the Linux/s390x behaviour: it puts
the complete fault address in the 'si_addr' field.
For sparc64:
$ sparc64-
$ ~/inst-
Segmentation fault (core dumped)
tags: | added: linux-user |
Changed in qemu: | |
status: | Expired → Fix Committed |
Changed in qemu: | |
status: | Fix Committed → Fix Released |
The behaviour in qemu-2.10 is the same as in qemu-2.9.