SIGSEGV in wxApp::GetGdkVisual()

wxPython Users
1

Hi all,

I have some application as python binaries (.pyc, .pyo) only. It requires
wxPython to run properly, so I've compiled wxPython from source (2.4.2.4)
for python 2.2.2.

Now when I run the python binaries like 'python app.pyc' it ends with
SIGSEGV:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 17053)]
0x406ddbc3 in wxApp::GetGdkVisual() () from /opt/wx/lib/libwx_gtk2-2.4.so

I've tryied wxWindows including wxPython from cvs, but it's the same.

I'm not sure what to do with that. Could it be wxPython bug? What can I do
with that?

Thank you for any support in advance,

Petr Koloros

2

Petr Koloros wrote:

Hi all,

I have some application as python binaries (.pyc, .pyo) only. It requires
wxPython to run properly, so I've compiled wxPython from source (2.4.2.4)
for python 2.2.2.

Now when I run the python binaries like 'python app.pyc' it ends with
SIGSEGV:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 17053)]
0x406ddbc3 in wxApp::GetGdkVisual() () from /opt/wx/lib/libwx_gtk2-2.4.so

I've tryied wxWindows including wxPython from cvs, but it's the same.

Do the wxWindows samples have the same problems? Do you have app.py to see if it does anything out of the ordinary? If you run from within gdb what does the backtrace at the time of the crash look like?

ยทยทยท

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