[Python-Dev] Issue #8863 adds a new PYTHONNOFAULTHANDLER environment variable

[Victor Stinner]

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/gc_inspection.py
> (<object object at 0x7f01827ad870>, <NULL>, <NULL>, <NULL>, <NULL>, <NULL>,
> <NULL>, <NULL>, <NULL>, <NULL>) Fatal Python error: Segmentation fault
> 
> Traceback (most recent call first):
>   File "Lib/test/crashers/gc_inspection.py", line 29 in g
>   File "Lib/test/crashers/gc_inspection.py", line 32 in <module>
> 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/nasty_eq_vs_dict.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 <module>
Segmentation fault
Erreur de segmentation
$ echo $?
139
-----------------

> And this test does not report anything at all:
> 
> $ ./python Lib/test/crashers/compiler_recursion.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 <module>
Segmentation fault
Erreur de segmentation
$ echo $?
139
-----------------

Victor