For some reason, wxDirDialog segfaults on alpha. I tested it with wxpython-2.6.10/2.6.3.3 (with/without USE="unicode opengl") and wxGTK-2.6.3.3. Alpha seems to be the only arch affected (x86 and sparc are sane AFAIK). I still not sure if it's a bug in the python bindings or in the wxwindows itself.
Created attachment 113285 [details] Segfaulting wxpython testcase wxpython buggy test
Well, problem isn't in the python bindings but in the wxWindows package itself.
Created attachment 113461 [details] Segfaulting wxwindows testcase wxwindows buggy test
Can a backtrace be made available? I don't have an alpha available to me. Should it crash on launch with no actions I need to take to make it crash? If no specific interaction is necessary then I indeed can't reproduce it on my x86. If someone with an alpha would be able to work with me realtime on this over IRC (nickname leio) I'd appreciate it. I have a 2.6.4.0 ebuild version and patchset available that I want to put in tree soon (I still need to do ABI compatibility testing), and it would be nice if that version will work without this crash on alpha - some testing from alpha people would help to ensure that ;)
Jose has tried 2.6.4.0, and at least the attached wxwidgets testcase doesn't crash anymore with a debug build. He will try with the same build settings as 2.6.3.3 and test bittornado and other things as well. Meanwhile I'll try to work towards 2.6.4.0 in portage (ABI checks, etc) and if all is fine (no patches for alpha support necessary) add it.
I've tested 2.6.0.4 with / without USE="unicode,debug" and all works as expected. bittornado and audacity work fine with the new version. 2.6.0.4 seems to solve all the problems on alpha. So, when it reaches portage, we can close this as FIXED. /me loves stories with a happy end. Thanks a lot to Mart.
New glibc-2.5 fixes this bug. After having some problems with the glibc stable version, now all is fine and I think we can close this. Thanks.
