[issue1215] documentation doesn't say that you can't handle C segfaults from python

2013-10-06 Thread Roundup Robot
Roundup Robot added the comment: New changeset bd16e333 by Georg Brandl in branch '3.3': Closes #1215: document better why it is not a good idea to catch e.g. SIGSEGV and refer to faulthandler. http://hg.python.org/cpython/rev/bd16e333 -- nosy: +python-dev resolution: -> fixed

[issue1215] documentation doesn't say that you can't handle C segfaults from python

2013-10-06 Thread Georg Brandl
Georg Brandl added the comment: I see not much to be done here, except from committing Martin's patch updated to the current trunk. -- ___ Python tracker ___

[issue1215] documentation doesn't say that you can't handle C segfaults from python

2011-08-31 Thread STINNER Victor
STINNER Victor 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 han

[issue1215] documentation doesn't say that you can't handle C segfaults from python

2011-08-30 Thread Martin Pool
Martin Pool added the comment: On 31 August 2011 07:56, STINNER Victor wrote: > > STINNER Victor added the comment: > >> def handler(signal, stackframe): >>     print "OUCH" >>     stdout.flush() >>     _exit(1) > > What do you want to do on a SIGSEGV? On a real fault, you cannot rely on   > P

[issue1215] documentation doesn't say that you can't handle C segfaults from python

2011-08-30 Thread STINNER Victor
STINNER Victor added the comment: > def handler(signal, stackframe): > print "OUCH" > stdout.flush() > _exit(1) 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 ha

[issue1215] documentation doesn't say that you can't handle C segfaults from python

2011-08-30 Thread Éric Araujo
Changes by Éric Araujo : -- nosy: +eric.araujo, haypo versions: +Python 3.3 -Python 2.6, Python 2.7, Python 3.1, Python 3.2 ___ Python tracker ___

[issue1215] documentation doesn't say that you can't handle C segfaults from python

2011-08-21 Thread Martin Pool
Martin Pool added the comment: This patch tries to improve the documentation a bit more to address the issue that confused tebeka and to advertise faulthandler. Could someone review or apply it? -- keywords: +patch Added file: http://bugs.python.org/file22989/20110822-1525-signal-doc

[issue1215] documentation doesn't say that you can't handle C segfaults from python

2011-08-21 Thread Martin Pool
Changes by Martin Pool : -- title: Python hang when catching a segfault -> documentation doesn't say that you can't handle C segfaults from python ___ Python tracker ___