Dead loop caused by sa_sigaction being NULL

[reverseXiang]

Hello, I'm confused about one part of the project. After using sigaction(sig, &action_info, &old_sa[sig]) in the function signal_handler_init(), I found that the values of old_sa[sig].sa_handler or old_sa[sig].sa_sigaction is always 0, which will leads to a problem: when initialized with signal_catch_init(), if a signal generated outside the try-catch range is caught, it should reasonably be handled according to the default logic, but the default handler function obtained through the sigaction function is NULL, so the signal_handler function cannot correctly handle This can lead to a dead loop where the exception is constantly triggered and signal_handler keeps catching.

[reverseXiang]

try use sa.sa_flags = SA_SIGINFO | SA_NODEFER | SA_RESETHAND; ？

But there is also a very strange phenomenon, when using SA_SIGINFO | SA_NODEFER | SA_RESETHAND, even though there is SA_SIGINFO, but the trigger signal function is sa_handler, not sa_sigaction, I found by observing the signal_handler (int signo, siginfo_t *info, void *reserved) after the 2 parameters of the address, they are random values which not readable. Finally, I use flag SA_SIGINFO | SA_NODEFER and signal(signo, SIG_DFL) to fix this problem.

[dario-chamorro-meli]

Hello, when a catch is presented outside the try-catch it enters an infinite loop, is there any way to trigger the error in a normal way if it is not in the try-catch, I am not clear about the fix you propose, could you give me an example?
Thank you very much and greetings