Lisandro Dalcin wrote: > On Sun, Oct 18, 2009 at 1:04 PM, Stefan Behnel wrote: >> while working on the Py3 exception code, I discovered that something in the >> tree transformation or tree assertion code makes the Python interpreter >> crash during the test suite run. > > As I routinely test from 2.3 to 3.2 with debug Python builds (and > UCS2, just because I always forget to use UCS4), I got these two: > > <...> > Running tests against Cython 0.11.3 > Python 3.1.1 (r311:74480, Sep 9 2009, 10:27:39) > [GCC 4.4.1 20090725 (Red Hat 4.4.1-2)] > > compiling (c) first_assignment ... HIER1 > python3.1: Objects/unicodeobject.c:839: PyUnicodeUCS2_FromFormatV: > Assertion `obj' failed. > Aborted > > <...> > Running tests against Cython 0.11.3 > Python 3.2a0 (py3k:75400, Oct 14 2009, 11:53:23) > [GCC 4.4.1 20090725 (Red Hat 4.4.1-2)] > > compiling (c) first_assignment ... HIER1 > python3.2: Objects/unicodeobject.c:839: PyUnicodeUCS2_FromFormatV: > Assertion `obj' failed. > Aborted > > So it it seems that PyUnicode_FromFormat (perhaps from PyErr_Format()) > is called with %R format and a NULL PyObject*.
Yep, that's when it's trying to print the corrupted sys.exc_info(). I'll file a bug report over at CPython. Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
