Quote:
The sigaction() function provides a more comprehensive and reliable mechanism for controlling signals; new applications should use sigaction() rather than signal().
I perfectly agree with the above and have been using that only.
Am just curious to know about the behavior of signal(); and why its behavior is different in different systems.
Is it due to the reason that different libraries are in use ? If so, how to identify them ?
Quote:
from occurring until the current signal handling has completed
Am confused about this too, there is no guarantee with the older semantics that the signal of same type will not be delivered while the current function block for the signal is being executed.
In that case, there is no reason for it to wait till the function block is executed.
In short, can it be said signal() behavior is undefined - or am I being rude in saying that ?