RetroSearch Browse

Sun Dec 21 19:27:29 CET 2008 · https://mail.python.org/pipermail/python-dev/2008-December/084514.html

skip at pobox.com schrieb:
>     Stijn> any hints what might cause this (or how i can figure it out). i
>     Stijn> have a coredump, but have no clue what to look for.
> 
> I can reproduce it on my Mac.  The croak happens while it is attempting to
> raise the exception about a bad file descriptor.  Unfortunately, in
> PyErr_Restore the call to PyThreadState_GET() returns NULL which means that
> _PyThreadState_Current is NULL.  I see no differences between pystate.[ch]
> in the 2.5 and 2.6 branches.  There must be something different about the
> way PyThreadState_Swap or PyThreadState_DeleteCurrent are used.  Those are
> the only two routines which appear to set it.  
> 
> Did this not happen with 2.5.2?

Wild guess: the bug might be related to
http://bugs.python.org/issue1683. From the top of my head it's the only
major change in the thread state code that I can recall.

Christian

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-December/084514.html below:

[Python-Dev] python 2.5.3 segmentation fault with gcc 4.1.2