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 vstinner
Recipients BreamoreBoy, Rhamphoryncus, belopolsky, docs@python, eric.araujo, georg.brandl, gvanrossum, poolie, schmir, tebeka, terry.reedy, vstinner
Date 2011-08-31.12:02:30
SpamBayes Score 2.51604e-05
Marked as misclassified No
Message-id <201108311402.11025.victor.stinner@haypocalc.com>
In-reply-to <CAA9uavBU5TCMFuzwsgLrfHSNjpGu92DENOgfhsR-nujgVV9wfA@mail.gmail.com>
Content
Le mercredi 31 août 2011 02:52:01, vous avez écrit :
> > What do you want to do on a SIGSEGV? On a real fault, you cannot rely on
> >  Python internal state, you cannot use any Python object. To handle a
> > real SIGSEGV fault, you have to implement a signal handler using only
> > *signal safe* functions.... in C.
> 
> Well, strictly speaking, it is very hard or impossible to write C code
> that's guaranteed to be safe after an unexpected segv too

It is possible if you only use signal safe functions. I think that no Python 
function is signal safe :-)
History
Date User Action Args
2011-08-31 12:02:31vstinnersetrecipients: + vstinner, gvanrossum, georg.brandl, terry.reedy, tebeka, belopolsky, Rhamphoryncus, schmir, eric.araujo, docs@python, BreamoreBoy, poolie
2011-08-31 12:02:31vstinnerlinkissue1215 messages
2011-08-31 12:02:30vstinnercreate