wx2.5 and wxproj.cpp segfault

[Daniel Calvelo Aros]

Hi all.

I'm trying to work out the segfaults I get in wxproj when trying to port
thuban to wx2.5.

The story so far:

- the segfault arises when trying to access the C++ object obtained from the
Python repr of the object

- I isolated the problematic code in wxproj.cpp

- according to gdb and valgrind, the address given by wxPython's repr of the
wxDC is not an allocated or known address

I have tried to build my own debugging version of wxPython to dig deeper,
suspecting some weirdness in the unicode version I have (Debian unstable:
wxPython-2.5.3.2pre), but I have had no success to date.

So, linuxian thubaneers, can anybody with a wx2.5 installed try the following?
I attached a small archive that mimics the problematic code in wxproj.cpp; if
I run the build_and_run.sh three-liner, I get some output, with coherent
addresses for all objects and a segfault when trying to access from C++ the
wxDC created in Python. This is precisely what happens in wxproj.cpp.

Can you reproduce the problem? If so, I reckon the problem is somewhere
between SWIG and its use by wxPython, far beyond my current knowledge. Google
is of no use, and the only remotely related bug I found happened (once) in
aMule and went so far unresolved.

Cheers,

Daniel.

-- Daniel Calvelo Aros