➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author neologix
Recipients neologix, rpointel, vstinner
Date 2011-09-01.06:45:09
SpamBayes Score 0.00091209396
Marked as misclassified No
Message-id <CAH_1eM3vEqHMpY1xHcGHnEO9_Q_Ek4iScCinRczQ=MgE0te8DA@mail.gmail.com>
In-reply-to <1314855252.72.0.757975285253.issue12868@psf.upfronthosting.co.za>
Content 
> without-threads, it segfault:
>

It's normal :-)
_stack_overflow triggers - as it names implies - a stack overflow.
However, as you can see in the output, faulthandler is now able to
catch the SIGSEGV and display the backtrace (because it set up an
alternate stack for the signal handler with sigaltstack).

> However, if I run test_faulthandler.py, it seems to be ok:

Yes: the test checks that the stack overflow was correctly caught by
faulthandler.

@Victor: can I commit the patch?
History
Date User Action Args
2011-09-01 06:45:09neologixsetrecipients: + neologix, vstinner, rpointel
2011-09-01 06:45:09neologixlinkissue12868 messages
2011-09-01 06:45:09neologixcreate