From: Guido van Rossum <guido@python.org>
Date: Thu, 10 Apr 2003 20:30:18 +0000 (+0000)
Subject: Backport:
X-Git-Tag: v2.2.3c1~73
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=ef582abab461e306ac3fa0ad867b2db564fed3a5;p=thirdparty%2FPython%2Fcpython.git

Backport:
PyErr_NormalizeException(): in the type==NULL test, we should simply
return.  Setting an exception can mess with the exception state, and
continuing is definitely wrong (since type is dereferenced later on).
Some code that calls this seems to be prepared for a NULL exception
type, so let's be safe rather than sorry and simply assume there's
nothing to normalize in this case.
---

diff --git a/Python/errors.c b/Python/errors.c
index 13b3d11ed6b1..224c21619fd7 100644
--- a/Python/errors.c
+++ b/Python/errors.c
@@ -131,9 +131,8 @@ PyErr_NormalizeException(PyObject **exc, PyObject **val, PyObject **tb)
 	PyObject *initial_tb = NULL;
 
 	if (type == NULL) {
-		/* This is a bug.  Should never happen.  Don't dump core. */
-		PyErr_SetString(PyExc_SystemError,
-			"PyErr_NormalizeException() called without exception");
+		/* There was no exception, so nothing to do. */
+		return;
 	}
 
 	/* If PyErr_SetNone() was used, the value will have been actually