other: 0.179
semantic: 0.150
device: 0.095
debug: 0.072
vnc: 0.069
network: 0.065
graphic: 0.060
PID: 0.058
files: 0.055
performance: 0.052
socket: 0.044
permissions: 0.043
boot: 0.032
KVM: 0.028
debug: 0.256
files: 0.165
other: 0.140
semantic: 0.081
performance: 0.056
network: 0.047
PID: 0.046
device: 0.042
vnc: 0.042
permissions: 0.031
graphic: 0.029
boot: 0.028
socket: 0.024
KVM: 0.014

broken signal handling in nios2 user-mode emulation

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.



The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.

A quick eyeball of the patch and the current QEMU tree indicates that at least some of the bugs it's trying to fix still exist (notably a lot of use of "long" in various target_* structures, which should not be using types with a width dependent on the host system.)


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