On Thu, 03 Feb 2011 21:52:40 +0100
Victor Stinner wrote:
> Le jeudi 03 février 2011 à 12:22 -0500, Reid Kleckner a écrit :
> > On Thu, Feb 3, 2011 at 8:05 AM, Victor Stinner
> > wrote:
> > > - SIGABRT is not handled
> >
> > Why not?
>
> Just because I forgot to handle it. But I don't know if i
Le jeudi 03 février 2011 à 12:22 -0500, Reid Kleckner a écrit :
> On Thu, Feb 3, 2011 at 8:05 AM, Victor Stinner
> wrote:
> > - SIGABRT is not handled
>
> Why not?
Just because I forgot to handle it. But I don't know if it is a good
thing to display the Python backtrace on abort() or not. Pytho
On Thu, Feb 3, 2011 at 8:05 AM, Victor Stinner
wrote:
> - SIGABRT is not handled
Why not? That seems useful for debugging assertion failures, although
most C code in Python raises exceptions rather than asserting.
I'm guessing it's because it aborts the process after printing the
backtrace. Y
On Thu, Feb 3, 2011 at 11:05 PM, Victor Stinner
wrote:
> - I have to write something to be able to enable the faulthandler
> before starting your program (write a program for that?)
I don't know enough about signal handling to help with your other
remaining concerns, but an appropriate "-X" comm
Hi,
Since the end of last december, I'm still working on my fault handler
project:
https://github.com/haypo/faulthandler
You can use it to get more information after a crash or if you program
hangs somewhere. It helps if you don't have access to other debugging
tool (eg. install gdb7+python-gdb.p
