[wxPython-users] Again Crash in gtk and debugging

[Robin Dunn]

Franz Steinhaeusler wrote:
> 2.8.4, Kubuntu 7.10, python 2.5
> 
> Several times, when I quit my app, I have an segmentation fault.
> I tried to use gdb, but it said, no debug symbols found and so the stacktrace is
> not really expressive.
> In the archives, I also found "break g_log". Is that useful too?

That works if there is a GTK warning or error log message and you want 
to see how it is getting to the point of showing the log.  For a crash 
like this it wouldn't be applicable.

> My question is:
> How can I get debug symbols (with load xy.so or do I have to get an according (wx)pyhton
> version?

The most reliable way to get the debug symbols is to build your own 
Python and wxPython.  (Building your own Python isn't really necessary, 
but it helps give you more of the stack context.)

> 
> I suspect, by quitting the app, the program receives still some events, for ojbects, which
> are in the process of being destroyed. But its hard to figure out, except an debugger with 
> according debug symbols
> 

Are you exiting the app by closing all top-level windows and letting 
MainLoop exit naturally?  Or are you doing something more drastic like 
calling wx.Exit()?


-- 
Robin Dunn
Software Craftsman
http://wxPython.org  Java give you jitters?  Relax with wxPython!