[Python-Dev] Issue #8863 adds a new PYTHONNOFAULTHANDLER?environment variable (original) (raw)
"Martin v. Löwis" martin at v.loewis.de
Tue Dec 21 00:00:39 CET 2010
- Previous message: [Python-Dev] Issue #8863 adds a new PYTHONNOFAULTHANDLER?environment variable
- Next message: [Python-Dev] Issue #8863 adds a new PYTHONNOFAULTHANDLER environment variable
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Do you have an example bug where this patch helps in finding the precise location of a segfault? How is 'line 29 in g' not more precise than 'Segmentation fault'?
I think Stefan is treating "precise location" as an absolute property, not a relative one. The precise location would be the very instruction causing the fault; this is something that a core dump provides, unless a signal handler interferes with that.
In many crashes I fixed, the Python stack trace was irrelevant to understand the nature of the crash. Of course, there were also counter- examples where you'ld need the Python stack (or, rather, the entire interpreter trace) to understand how the crashing case can occur in the first place.
Regards, Martin
- Previous message: [Python-Dev] Issue #8863 adds a new PYTHONNOFAULTHANDLER?environment variable
- Next message: [Python-Dev] Issue #8863 adds a new PYTHONNOFAULTHANDLER environment variable
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]