Ucontext gets blocked signal after swapcontext

Question

I am blocking a SIGINT in ucontext A, for example, say I hit ^C (SIGINT) while it is running, nothing happens as expected.

In context B, there is a SIGINT handler. When I swapcontext(A, B) then ucontext B immediately executes the signal handler. Even though context A is the one that received and blocked this signal. Is there a way to ensure process B does not enter the signal handler right away?

See: https://stackoverflow.com/questions/63866300/does-a-blocked-signal-also-a-pending-signal — jxh, Apr 06 '22 at 06:18

score 0 · Answer 1 · answered Apr 06 '22 at 05:47

0

While I did not figure this out, using a critical flag, instead of blocking the signal was what I used.

answered Apr 06 '22 at 05:47

beans

31
5

1

please add some example in your answer. – Engr.Aftab Ufaq Apr 06 '22 at 06:41

Ucontext gets blocked signal after swapcontext

1 Answers1