mirror of https://github.com/python/cpython
tuple.__repr__ did not consider a reference loop as it is not possible from
Python code; but it is possible from C. object.__str__ had the issue of not expecting a type to doing something within it's tp_str implementation that could trigger an infinite recursion, but it could in C code.. Both found thanks to BaseException and how it handles its repr. Closes issue #1686386. Thanks to Thomas Herve for taking an initial stab at coming up with a solution.
This commit is contained in:
parent
c537881caa
commit
0b14f243c4
|
@ -12,6 +12,12 @@ What's New in Python 2.6 alpha 1?
|
|||
Core and builtins
|
||||
-----------------
|
||||
|
||||
- Issue #1686386: Tuple's tp_repr did not take into account the possibility of
|
||||
having a self-referential tuple, which is possible from C code. Nor did
|
||||
object's tp_str consider that a type's tp_str could do something that could
|
||||
lead to an inifinite recursion. Py_ReprEnter() and Py_EnterRecursiveCall(),
|
||||
respectively, fixed the issues.
|
||||
|
||||
- Issue #1164: It was possible to trigger deadlock when using the 'print'
|
||||
statement to write to a file since the GIL was not released as needed. Now
|
||||
PyObject_Print() does the right thing along with various tp_print
|
||||
|
|
|
@ -408,7 +408,12 @@ _PyObject_Str(PyObject *v)
|
|||
if (Py_Type(v)->tp_str == NULL)
|
||||
return PyObject_Repr(v);
|
||||
|
||||
/* It is possible for a type to have a tp_str representation that loops
|
||||
infinitely. */
|
||||
if (Py_EnterRecursiveCall(" while getting the str of an object"))
|
||||
return NULL;
|
||||
res = (*Py_Type(v)->tp_str)(v);
|
||||
Py_LeaveRecursiveCall();
|
||||
if (res == NULL)
|
||||
return NULL;
|
||||
type_ok = PyString_Check(res);
|
||||
|
|
|
@ -216,6 +216,15 @@ tuplerepr(PyTupleObject *v)
|
|||
PyObject *s, *temp;
|
||||
PyObject *pieces, *result = NULL;
|
||||
|
||||
/* While not mutable, it is still possible to end up with a cycle in a
|
||||
tuple through an object that stores itself within a tuple (and thus
|
||||
infinitely asks for the repr of itself). This should only be
|
||||
possible within a type. */
|
||||
i = Py_ReprEnter((PyObject *)v);
|
||||
if (i != 0) {
|
||||
return i > 0 ? PyString_FromString("(...)") : NULL;
|
||||
}
|
||||
|
||||
n = Py_Size(v);
|
||||
if (n == 0)
|
||||
return PyString_FromString("()");
|
||||
|
@ -226,7 +235,10 @@ tuplerepr(PyTupleObject *v)
|
|||
|
||||
/* Do repr() on each element. */
|
||||
for (i = 0; i < n; ++i) {
|
||||
if (Py_EnterRecursiveCall(" while getting the repr of a tuple"))
|
||||
goto Done;
|
||||
s = PyObject_Repr(v->ob_item[i]);
|
||||
Py_LeaveRecursiveCall();
|
||||
if (s == NULL)
|
||||
goto Done;
|
||||
PyTuple_SET_ITEM(pieces, i, s);
|
||||
|
@ -261,6 +273,7 @@ tuplerepr(PyTupleObject *v)
|
|||
|
||||
Done:
|
||||
Py_DECREF(pieces);
|
||||
Py_ReprLeave((PyObject *)v);
|
||||
return result;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue