I'm using Debian, and have the Debian packages of wxWindows 2.2.9.2.
There is a libwxgtk2.2-python package containing wxPython, then there is
a libwxgtk2.2, as well as a libwxgtk2.2-dbg, which contains a debug
version of the wxWindows library,
/usr/lib/libwx_gtkd-2.2.so.6.2.6
Is this enough for debugging, how do I get wxPython to use this? Or what
must I look for to compile a debug version of wxPython? I'm not afraid
of editing the package sources to create a debug version. I do prefer to
create Debian packages, rather than compiling from the upstream sources
and doing the "make install" thing, but I will do that if necessary.
Basically, what command line parameters are needed in the build to make
a debug version? Instructions for clean upstream sources would be great,
I'll figure out the Debian package specific stuff myself.
Hehe, sorry, I no longer need to build a debug version. Turned out the
"Bus Error" I mailed about long long ago was due filesystem corruption
causing mmap to cause a SIGBUS.
The "workaround" since then was that I used a different machine to
develop. Only now did I get back to this, and discover the truth.
I'm using Debian, and have the Debian packages of wxWindows 2.2.9.2.
There is a libwxgtk2.2-python package containing wxPython, then there is
a libwxgtk2.2, as well as a libwxgtk2.2-dbg, which contains a debug
version of the wxWindows library,
/usr/lib/libwx_gtkd-2.2.so.6.2.6
Is this enough for debugging, how do I get wxPython to use this?
I don't know anything about the .deb build scripts, but if you build
wxPython using the debugging version of wxGTK then wxPython will be built
with debug info too. It just depends on which wx-config script is used.
ยทยทยท
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters? http://wxPython.org Relax with wxPython!
I don't know anything about the .deb build scripts, but if you build
wxPython using the debugging version of wxGTK then wxPython will be built
with debug info too. It just depends on which wx-config script is used.
This would be because building wxGTK with debug gives you a wx-config
script that enables debug and this is what is called by wxPython build
scripts... Right, thanks.