Differences between version 4 and predecessor to the previous major change of SIGABRT.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Sunday, June 12, 2005 1:42:41 pm | by PerryLorier | Revert |
| Older page: | version 3 | Last edited on Sunday, June 12, 2005 2:00:40 am | by AristotlePagaltzis | Revert |
@@ -2,6 +2,4 @@
Generated by abort(3). This signal by default causes your program to terminate and dump core.
abort(3) is often called indirectly by assert(3). Basically this usually means that the program detected an illegal state and has aborted allowing for debugging.
-
-You can often also generate a [SIGABRT] with Ctrl-\, useful if you are trying to debug an infinite loop. (Run the program, wait for it to "hang" press Ctrl-\ or <tt>kill -ABRT ''pid''</tt>, and then use gdb(1) to inspect the core file).
