79096500

Date: 2024-10-17 04:50:21
Score: 1
Natty:
Report link

I found the issue. The problem was that the parent was sending the signals to the child before the child could register the signal handler in the first place. Since the default behavior when SIGUSR1 and SIGUSR2 is received is to terminate, the child was exiting before it could print anything. Adding a 1 second delay in the parent process fixed the issue.

Reasons:
  • Has code block (-0.5):
  • Self-answer (0.5):
  • Single line (0.5):
  • Low reputation (0.5):
Posted by: Setu