I don't suppose anybody's going to get round to implementing RT signals
for SPARC any time soon, so let's retitle this bug to track the one
remaining issue.
** Summary changed:
- qemu user mode does not support catching SIGSEGV on some architectures
+ qemu user mode: rt signals not implemented f
I confirm that in qemu-2.11, the ppc and s390x cases are fixed, however
the sparc64 case is still failing:
$ ~/inst-qemu/2.11.0/bin/qemu-ppc testsigsegv-ppc
$ echo $?
0
$ ~/inst-qemu/2.11.0/bin/qemu-ppc64 testsigsegv-ppc64
$ echo $?
0
$ ~/inst-qemu/2.11.0/bin/qemu-ppc64le testsigsegv-ppc64le
$ e
Patchset that fixes all the minor parts of this, leaving (probably) just sparc
setup_rt_frame/rt_sigreturn:
https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg00833.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://b
...and also
* SPARC doesn't implement setup_rt_frame(), so it can't deliver RT signals at
all.
That's a bigger missing feature than the rest.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1705118
T
This is an interesting collection of different bugs:
* s390x is missing masking operations, as you describe
* ppc is passing the PC of the offending insn, not the data address, into
si_addr
* sparc fails to record the address of a data fault and so passes 0 into
si_addr
* sparc also isn't imp
** Tags added: linux-user
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1705118
Title:
qemu user mode does not support catching SIGSEGV on some architectures
Status in QEMU:
New
Bug description
The behaviour in qemu-2.10 is the same as in qemu-2.9.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1705118
Title:
qemu user mode does not support catching SIGSEGV on some architectures
Status in
** Attachment added: "Statically compiled test program for ppc64"
https://bugs.launchpad.net/qemu/+bug/1705118/+attachment/4917118/+files/testsigsegv-ppc64
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net
** Attachment added: "Statically compiled test program for ppc"
https://bugs.launchpad.net/qemu/+bug/1705118/+attachment/4917117/+files/testsigsegv-ppc
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bug
** Attachment added: "Statically compiled test program for ppc64le"
https://bugs.launchpad.net/qemu/+bug/1705118/+attachment/4917119/+files/testsigsegv-ppc64le
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad
** Attachment added: "Statically compiled test program for sparc64"
https://bugs.launchpad.net/qemu/+bug/1705118/+attachment/4917121/+files/testsigsegv-sparc64
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad
** Attachment added: "Statically compiled test program for s390x"
https://bugs.launchpad.net/qemu/+bug/1705118/+attachment/4917120/+files/testsigsegv-s390x
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net
12 matches
Mail list logo
