summaryrefslogtreecommitdiff
path: root/Include/intrcheck.h
diff options
context:
space:
mode:
authorGuido van Rossum <guido@python.org>1997-11-14 22:24:28 +0000
committerGuido van Rossum <guido@python.org>1997-11-14 22:24:28 +0000
commit359bcaa539d9bbb2b008b5fd0a76c758b489bed5 (patch)
treee6c5cb83090ef2a2cffcbb18f0ec5db28111a960 /Include/intrcheck.h
parentc9fd600640229af8381f207b7d9224ba86db7206 (diff)
downloadcpython-git-359bcaa539d9bbb2b008b5fd0a76c758b489bed5.tar.gz
This fix (across 4 files in 3 directories) solves a subtle problem with
signal handlers in a fork()ed child process when Python is compiled with thread support. The bug was reported by Scott <scott@chronis.icgroup.com>. What happens is that after a fork(), the variables used by the signal module to determine whether this is the main thread or not are bogus, and it decides that no thread is the main thread, so no signals will be delivered. The solution is the addition of PyOS_AfterFork(), which fixes the signal module's variables. A dummy version of the function is present in the intrcheck.c source file which is linked when the signal module is not used.
Diffstat (limited to 'Include/intrcheck.h')
-rw-r--r--Include/intrcheck.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/Include/intrcheck.h b/Include/intrcheck.h
index f9658e28b1..8566051690 100644
--- a/Include/intrcheck.h
+++ b/Include/intrcheck.h
@@ -37,6 +37,7 @@ PERFORMANCE OF THIS SOFTWARE.
extern int PyOS_InterruptOccurred Py_PROTO((void));
extern void PyOS_InitInterrupts Py_PROTO((void));
+void PyOS_AfterFork Py_PROTO((void));
#ifdef __cplusplus
}