[docs] [issue1215] documentation doesn't say that you can't handle C segfaults from python
STINNER Victor
report at bugs.python.org
Wed Aug 31 14:02:31 CEST 2011
STINNER Victor <victor.stinner at haypocalc.com> added the comment:
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 :-)
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue1215>
_______________________________________
More information about the docs
mailing list