[issue8863] Display Python backtrace on SIGSEGV, SIGFPE and fatal error

STINNER Victor report at bugs.python.org
Thu Dec 23 04:35:58 CET 2010


STINNER Victor <victor.stinner at haypocalc.com> added the comment:

Le jeudi 23 décembre 2010 à 02:27 +0000, Scott Dial a écrit :
> Scott Dial <scott at scottdial.com> added the comment:
> 
> On 12/22/2010 8:52 PM, STINNER Victor wrote:
> > Amaury asked for a sys.setsegfaultenabled() option: I think that the command line option and the environment variable are enough.
> 
> I really think you should think of it as a choice the developer of an
> application makes instead of a choice an application user makes.

Why do you think so? Can you give me an use case of
sys.setsegfaultenabled()?

Extract of my email on python-dev:

  Use case: when a program crashs, the user reruns its application 
  with the fault handler enabled and tries to reproduce the crash.
  He/She can send the Python backtrace to the developer, or use
  it directly (if he/she understands it).

After the discussion on python-dev, I don't think that the fault handler
should be enabled by default, but only for a single run.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8863>
_______________________________________


More information about the Python-bugs-list mailing list