From 49b0c3bafe8fd9818e73e3594e12a749f796eeb2 Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Thu, 6 Jul 2000 19:42:19 +0000 Subject: [PATCH] Fix bug #392, reported by Jonathan Giddy : In posixmodule.c:posix_fork, the function PyOS_AfterFork is called for both the parent and the child, despite the docs stating that it should be called in the new (child) process. This causes problems in the parent since the forking thread becomes the main thread according to the signal module. Calling PyOS_AfterFork() only in the child fixes this. Changed for both fork() and forkpty(). --- Modules/posixmodule.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/Modules/posixmodule.c b/Modules/posixmodule.c index d85b91cc0b..eea797e940 100644 --- a/Modules/posixmodule.c +++ b/Modules/posixmodule.c @@ -1755,7 +1755,8 @@ posix_fork(self, args) pid = fork(); if (pid == -1) return posix_error(); - PyOS_AfterFork(); + if (pid == 0) + PyOS_AfterFork(); return PyInt_FromLong((long)pid); } #endif @@ -1814,7 +1815,8 @@ posix_forkpty(self, args) pid = forkpty(&master_fd, NULL, NULL, NULL); if (pid == -1) return posix_error(); - PyOS_AfterFork(); + if (pid == 0) + PyOS_AfterFork(); return Py_BuildValue("(ii)", pid, master_fd); } #endif -- 2.40.0