October 2018
Beginner
794 pages
19h 23m
English
Notice how our previous test case, sending 5,000 SIGUSR1 signals to the defer_or_not application running with SA_NODEFER set, caused it to crash with a segmentation fault (often abbreviated as segfault). The OS sent the signal SIGSEGV (segmentation violation) to the process when it made an invalid memory reference; in other words, a bug related to a memory access. Trapping the SIGSEGV could be very valuable; we can gain information concerning how and why the application crashed (in fact, we shall do precisely this in the next chapter).
However, think carefully: in the last test case (the 5,000 signals... one), the reason the process crashed is that its stack overflowed. Thus, the OS delivered the signal
Read now
Unlock full access