On Fri, Sep 06, 2019 at 11:41:51PM -0400, Sandro Tosi wrote: > > Switching to the GTK 3 version may be as simple as: > > 1) Update your Build-Depends > > libwxgtk3.0-dev -> libwxgtk3.0-gtk3-dev > > libwxgtk-media3.0-dev -> libwxgtk-media3.0-gtk3-dev > > 2) Rebuild > > 3) Test > > i tried this but it failed with this segfault: > [...] > > Thread 1 "amule" received signal SIGSEGV, Segmentation fault. > 0x00007ffff71d8c1a in wxWindow::DoClientToScreen(int*, int*) const () from > /usr/lib/x86_64-linux-gnu/libwx_gtk3u_core-3.0.so.0
That sounds suspiciously similar to this bug, reported as happening when using the GTK2 flavour of wxWidgets: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935698 It appears that somehow a window can end up being its own parent (or a parent of one of its own ancestors), which isn't valid and results in wx running out of stack when it tries to recurse up the window hierarchy. > No idea what it really when wrong, but if you could lend a head it would be > great! Sadly upstream don't seem to be making progress on this. I've recall from past wx transitions that amule is difficult to debug without connecting to file sharing networks, which I really don't want to be doing. Is there a way to reproduce this without any remote connections? It rather looks to me like this probably isn't specific to GTK3 though. Cheers, Olly
