You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test-c-stack.sh, test-sigsegv-catch-stackoverflow1 and test-sigsegv-catch-stackoverflow2, these gnulib tests in packages diffutils and m4 will fail because the unexpected behavior of signal handling in qemu user.
These three tests will try to capture signal SIGSEGV and find out if the signal is triggered by the stack overflow exception. However, because of some unknown reason, the tests fail to capture the segmentation fault and so all of the tests will fail.
The reason why those tests fail is still unknown, but we can confirm that this unexpected behavior will occur in qemu-user only. In my opinion, we can just add those packages to the qemu user blacklist now as it is really hard to find out the reason.
The text was updated successfully, but these errors were encountered:
Avimitin
added a commit
to Avimitin/archriscv-packages
that referenced
this issue
Feb 15, 2023
What happened
test-c-stack.sh
,test-sigsegv-catch-stackoverflow1
andtest-sigsegv-catch-stackoverflow2
, these gnulib tests in packagesdiffutils
andm4
will fail because the unexpected behavior of signal handling in qemu user.These three tests will try to capture signal SIGSEGV and find out if the signal is triggered by the stack overflow exception. However, because of some unknown reason, the tests fail to capture the segmentation fault and so all of the tests will fail.
How to reproduce:
Here is a small reproduce example: https://github.com/Avimitin/stackoverflow-recover.
git clone https://github.com/Avimitin/stackoverflow-recover.git cd stackoverflow-recover make run
Current behavior
Conclusion
The reason why those tests fail is still unknown, but we can confirm that this unexpected behavior will occur in qemu-user only. In my opinion, we can just add those packages to the qemu user blacklist now as it is really hard to find out the reason.
The text was updated successfully, but these errors were encountered: