Author christian.heimes
Recipients christian.heimes, ctheune, gvanrossum
Date 2012-11-01.15:35:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

Py_FatalError() might be too drastic for the task. It calls abort() which kills the process with SIGABRT. The function closes and flushes all stream but no additional cleanup code is executed. This might be bad for resources like shared memories, named semaphores or database connections. On Windows abort() causes a pop up window with a crash report, too.

Would exit(3) or _exit(2) work here?
Date User Action Args
2012-11-01 15:35:21christian.heimessetrecipients: + christian.heimes, gvanrossum, ctheune
2012-11-01 15:35:21christian.heimessetmessageid: <>
2012-11-01 15:35:21christian.heimeslinkissue16381 messages
2012-11-01 15:35:21christian.heimescreate