A RetroSearch Logo

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

Search Query:

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

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

[Python-Dev] Issue #8863 adds a new PYTHONNOFAULTHANDLER?environment variable [Python-Dev] Issue #8863 adds a new PYTHONNOFAULTHANDLER?environment variable"Martin v. Löwis" martin at v.loewis.de
Tue Dec 21 00:00:39 CET 2010
>> 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
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4