Alexander Belopolsky <belopol...@users.sourceforge.net> added the comment:
On Wed, Dec 22, 2010 at 9:27 PM, Scott Dial <rep...@bugs.python.org> wrote:
>
> Scott Dial <sc...@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. A
> setsegfaultenabled() could just be another step of initializing the
> application akin to setting up the logging module, for instance. In that
> situation, a function call has a much lower barrier for use than a CLI
> option or environment variable where you'd have to create a wrapper script.
+1
I would actually prefer just sys.setsegfaultenabled() without a
controlling environment variable. If necessary, the environment
variable can be checked in site.py and sys.setsegfaultenabled()
called.
As I suggested on python-dev, I also think this belongs to a separate
module rather than core or sys. The relevant code is already
segregated in a file, so turning it into a module should not be
difficult. The only function that probably must stay in core is
_Py_DumpBacktrace(). With say "segvhandler" module, site.py can
include something like this:
if sys.getenv('PYTHONSEGVHANDLER'):
import segvhandler
segvhandler.enable()
Does the latest patch address the GIL/multithreading issues?
----------
title: Display Python backtrace on SIGSEGV, SIGFPE and fatal error ->
Display Python backtrace on SIGSEGV, SIGFPE and fatal error
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue8863>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
