RetroSearch Browse

Thu Dec 11 08:21:32 CET 2008 · http://mail.python.org/pipermail/python-dev/2008-December/084232.html

On Wed, Dec 10, 2008 at 8:37 PM, Victor Stinner
<victor.stinner at haypocalc.com> wrote:
> Recover after a segfault is dangerous, but my first goal was to get the Python
> backtrace instead just one line: "Segmentation fault". It helps a lot for
> debug!

This would be extremely useful. I've had PyGTK segfault on me a number
of times in an app I'm writing and I keep meaning to try get to the
bottom of the issue but it happens infrequently and somehow I never
get around to it. Some indictation of what Python was executing when
the segfault occurred would help narrow now the possibilities rapidly.

Schiavo
Simon

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://mail.python.org/pipermail/python-dev/2008-December/084232.html below:

[Python-Dev] Trap SIGSEGV and SIGFPE