Differences between version 3 and previous revision of SIGABRT.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Sunday, June 12, 2005 2:00:40 am | by AristotlePagaltzis | Revert |
| Older page: | version 2 | Last edited on Thursday, November 21, 2002 12:01:17 pm | by PerryLorier | Revert |
@@ -1,7 +1,7 @@
-!!!Signal: Abort
+!!! Signal: Abort
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.
+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 kill -ABRT ''pid'', and then use gdb(1) to inspect the core file).
+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).
