[issue4168] core dump exiting python

Changes by Benjamin Peterson <[EMAIL PROTECTED]>: -- resolution: -> out of date status: open -> closed ___ Python tracker <[EMAIL PROTECTED]> ___ _

[issue4168] core dump exiting python

David W. Lambert <[EMAIL PROTECTED]> added the comment: I rebuilt python3k from "today's snapshot". No more core dump. Problem solved, close case. IMH'edO. ___ Python tracker <[EMAIL PROTECTED]>

[issue4168] core dump exiting python

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: I can reproduce the problem, and it seems that it is already corrected by r66562 (issue3666), one week after 3.0rc1. Can you try with a newer version? -- nosy: +amaury.forgeotdarc ___ Python

[issue4168] core dump exiting python

STINNER Victor <[EMAIL PROTECTED]> added the comment: About your gdb output: - You have a 64 bits CPU (I have a 32 bits CPU) - You are using Red Hat 6.3.0.0-1.132.EL4rh (I'm using Ubuntu Hardy) - The crash occurs in PyErr_Fetch() on "*p_type = tstate->curexc_type;": I guess that p_type and/or

[issue4168] core dump exiting python

STINNER Victor <[EMAIL PROTECTED]> added the comment: I installed gsl using "sudo apt-get install libgsl0ldbl". Then I added ".0" to the library filenames (eg. CDLL('libgsl.so.0')). $ python3.0 dumpdriver.py Exception AttributeError: "'NoneType' object has no attribute 'debug'" in > ignored R

[issue4168] core dump exiting python

New submission from David W. Lambert <[EMAIL PROTECTED]>: I created in the python module gsl_fft a __del__ method to release workspace when the data size changes. It is called upon exiting python, and gave errors without traceback. So I registered it with atexit. This caused core dump. The