Dec. 10, 2008
11:21 p.m.
On Wed, Dec 10, 2008 at 8:37 PM, Victor Stinner <victor.stinner@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