Scott Dial <sc...@scottdial.com> added the comment: On 12/22/2010 10:35 PM, STINNER Victor wrote: > Why do you think so? Can you give me an use case of > sys.setsegfaultenabled()?
To feed back your own argument on python-dev: > How do you know that you application will crash? The idea is to give > informations to the user when an application crashs: the user can use > the backtrace or send it to the developer. Segmentation faults are > usually not (easilly) reproductible :-( So even if you enable the > fault handler, you may not be able to replay the crash. Or even > worse, the fault may not occurs at all when you enable the fault > handler... (Heisenbugs!) > 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. I agree that it should be disabled by default because of the potential do bad things if the application was not wrote with it in mind. But an application developer would be in a much better position to decide what the default should be for their application if they believe they will be able to get more useful bug reports from their users by enabling it. I thought that was your position, but if you no longer believe that, then I will not push for it. ---------- 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
