[Python-Dev] Issue #8863 adds a new PYTHONNOFAULTHANDLER environment variable (original) (raw)

Victor Stinner vstinner at edenwall.com
Mon Dec 20 14:39:29 CET 2010

Le lundi 20 décembre 2010 12:08:35, Stefan Krah a écrit :

I think the output is not particularly informative:

$ ./python Lib/test/crashers/gcinspection.py (<object object at 0x7f01827ad870>, , , , , , , , , ) Fatal Python error: Segmentation fault Traceback (most recent call first): File "Lib/test/crashers/gcinspection.py", line 29 in g File "Lib/test/crashers/gcinspection.py", line 32 in Segmentation fault Segmentation fault

The backtrace is valid. Don't you think that this backtrace is more useful than just "Segmentation fault"?

Another test is hanging indefinitely (Ubuntu 64-bit):

$ ./python Lib/test/crashers/nastyeqvsdict.py [hanging with no output]

I didn't tried with patch version 9, but with the patch version 10 I get:

$ ./python Lib/test/crashers/nasty_eq_vs_dict.py Fatal Python error: Segmentation fault

Traceback (most recent call first): File "Lib/test/crashers/nasty_eq_vs_dict.py", line 16 in hash File "Lib/test/crashers/nasty_eq_vs_dict.py", line 40 in __fill_dict File "Lib/test/crashers/nasty_eq_vs_dict.py", line 30 in eq File "Lib/test/crashers/nasty_eq_vs_dict.py", line 47 in Segmentation fault Erreur de segmentation $ echo $? 139

And this test does not report anything at all:

$ ./python Lib/test/crashers/compilerrecursion.py [no output at all] $ echo $? 0

Patch version 9 doesn't call the previous handler. Please retry with patch version 10 (which call the previous handler).

With the patch version 10 I get:

$ ./python Lib/test/crashers/compiler_recursion.py Fatal Python error: Segmentation fault

Traceback (most recent call first): File "Lib/test/crashers/compiler_recursion.py", line 5 in Segmentation fault Erreur de segmentation $ echo $? 139

Victor

More information about the Python-Dev mailing list