wx2.5 and wxproj.cpp segfault

[Jonathan Coles]

Am Montag, den 07.02.2005, 23:49 -0500 schrieb Daniel Calvelo Aros:
> Ooops. Forgot the attachment.

> > 
> > 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.


i can reproduce the problem:

jpc at reisen:/tmp/wx_test$ chmod +x build_and_run.sh 
jpc at reisen:/tmp/wx_test$ ./build_and_run.sh 
In Datei, eingefügt von /usr/include/python2.3/Python.h:8,
                    von wxtest.cpp:4:
/usr/include/python2.3/pyconfig.h:856:1: Warnung: »_POSIX_C_SOURCE«
redefiniert
In Datei, eingefügt von /usr/include/stdlib.h:25,
                    von wxtest.cpp:1:
/usr/include/features.h:131:1: Warnung: dies ist die Stelle der
vorherigen Definition
in Python: dc =  <wx._gdi.MemoryDC; proxy of C++ wxMemoryDC instance at
_18eb3a08_p_wxMemoryDC>
py_dc:_18eb3a08_p_wxMemoryDC
in use_DC:18eb3a08
./build_and_run.sh: line 3: 21353 Speicherzugriffsfehler  python
wxtest.py

--jonathan

-- 
=====================================================================
 Jonathan Coles                               http://www.jpcoles.com
 jonathan at jpcoles.com                    GnuPG Key: /gpg_pub_key.asc
=====================================================================