Programming

Normally, a good program should have 1 exit point.
that is the reason for elimination of goto statements from good programming.
its better to return from signal hander to the calling function and exit.

Suggestion with regard to the original question. I believe the signal handlers to be roughly intended as giving you what amounts to a user-space interrupt service routine. Generally in those we set variables, move things around, that sort of thing. Unusual results sometimes happen because your context can vary significantly. If, for example, you are in the main "scope" of your process, context is quite different from if you are in a "wait" state, as in a blocking read on a socket or some other input source.

My first experience to programming in "kernel space" on a BSD kernel was an eye-opener; there are times when one must literally do everything necessary to count and minimize machine cycles. Rules regarding reuse and form can be secondary to the clear and absolute need for efficiency. Examples abound and would probably bore the reader, so I will spare you.

In any event, were I to declare and use the interrupt vectors such as SIGINT, SIGHUP and so on, I would use the routine to set flags, in the unusual circumstance that I'm working with globals; sometimes I use one if I'm deliberately doing a "blocking read" from something, so that I know that my slumber will not be forever. Non-blocking reads of course are a different sort of logic.

I hope this helps.