[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1791763] Re: broken signal handling in nios2 user-mode emulation
From: |
Thomas Huth |
Subject: |
[Bug 1791763] Re: broken signal handling in nios2 user-mode emulation |
Date: |
Tue, 11 May 2021 05:35:10 -0000 |
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/261
** Changed in: qemu
Status: Confirmed => Expired
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #261
https://gitlab.com/qemu-project/qemu/-/issues/261
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1791763
Title:
broken signal handling in nios2 user-mode emulation
Status in QEMU:
Expired
Bug description:
This bug is against the 3.0 release.
It appears that the signal handling parts of the nios2 user-mode
emulation have never really been completed or tested. Some examples
of failing tests from the GCC testsuite are gcc.dg/pr78185.c and
gcc.dg/cleanup-10.c.
Some problems I've identified and tried to fix with the attached patch
are:
- Code copied from the Linux kernel wasn't adjusted to differentiate
between host and target data types and address spaces.
- The sigaltstack() system call returns EINVAL because fields are
listed in the wrong order in struct target_sigaltstack.
With this patch, the system calls to set up the signal handler are
returning successfully, but the handler isn't being invoked, so
something is still wrong. I think I need another pair of eyes to look
over this code.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1791763/+subscriptions
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Bug 1791763] Re: broken signal handling in nios2 user-mode emulation,
Thomas Huth <=