Doc/library/os.rst - Issue 12423: signal handler doesn't handle SIGABRT from os.abort

Keyboard Shortcuts

	File
u :	up to issue
m :	publish + mail comments
M :	edit review message
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line
<Enter> :	respond to / edit current comment

	Issue
u :	up to list of issues
m :	publish + mail comments
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue
# :	close issue

	Comment/message editing
<Ctrl> + s :	save comment
<Esc> :	cancel edit

Unified Diff: Doc/library/os.rst

Issue 12423: signal handler doesn't handle SIGABRT from os.abort

Patch Set: Created 1 year, 11 months ago

Use n/p to move between diff chunks; N/P to move between comments. Please Sign in to add in-line comments.

Jump to:

--- a/Doc/library/os.rst Mon Jul 04 11:44:46 2011 +0200

+++ b/Doc/library/os.rst Mon Jul 04 10:58:14 2011 -0700

@@ -1665,8 +1665,9 @@

Generate a :const:`SIGABRT` signal to the current process. On Unix, the default

behavior is to produce a core dump; on Windows, the process immediately returns

- an exit code of ``3``. Be aware that programs which use :func:`signal.signal`

- to register a handler for :const:`SIGABRT` will behave differently.

+ an exit code of ``3``. Be aware that calling this function will not call the

+ Python signal handler registered for :const:`SIGABRT` with

+ :func:`signal.signal`.

Availability: Unix, Windows.

« no previous file with comments | « no previous file | no next file » | no next file with comments »