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 rep...@bugs.python.org
http://bugs.python.org/issue1215
___
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
STINNER Victor victor.stin...@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
Changes by Éric Araujo mer...@netwok.org:
--
nosy: +eric.araujo, haypo
versions: +Python 3.3 -Python 2.6, Python 2.7, Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1215
STINNER Victor victor.stin...@haypocalc.com 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
Martin Pool m...@sourcefrog.net added the comment:
On 31 August 2011 07:56, STINNER Victor rep...@bugs.python.org wrote:
STINNER Victor victor.stin...@haypocalc.com added the comment:
def handler(signal, stackframe):
print OUCH
stdout.flush()
_exit(1)
What do you want to do
Changes by Martin Pool m...@sourcefrog.net:
--
title: Python hang when catching a segfault - documentation doesn't say that
you can't handle C segfaults from python
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1215
Martin Pool m...@sourcefrog.net 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:
