invalid signal-context capability

[Stefan Thöni]

Hello Genodians

I'm debugging an "invalid signal-context capability" but I can't 
pinpoint the bug.

 From my understanding an "invalid signal-context capability" happens 
when the signal handler is destroyed before the signal is processed. I 
have therefore carefully looked at the lifetime of all signal handlers 
and their corresponding signals, refactoring code to allow signals to be 
processed before destroying signal handlers.

Is there another condition that triggers an "invalid signal-context 
capability" besides destroying the signal handler before any 
corresponding signal is processed?

Does anyone have any tips on how to find which signal handler caused an 
"invalid signal-context capability" or where the signal originated?

Best regards
Stefan


-- 
Freundliche Grüsse

Stefan Thöni
Senior Security Architect
+41 79 824 11 90

gapfruit AG
Baarerstrasse 135
6300 Zug
https://gapfruit.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x99A5F4B3D4E372A6.asc
Type: application/pgp-keys
Size: 1871 bytes
Desc: OpenPGP public key
URL: <http://lists.genode.org/pipermail/users/attachments/20220718/a189a7cd/attachment.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 313 bytes
Desc: OpenPGP digital signature
URL: <http://lists.genode.org/pipermail/users/attachments/20220718/a189a7cd/attachment.sig>