it seems we have really nailed down the cause of your bug, a bug in wx.
Maybe not...
There was a reason why 'the feel' of this mule was not right:
the mule has crashed...
(amule:16456): GLib-CRITICAL **: g_source_remove: assertion `tag > 0' failed
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule SVN compiled with wxGTK2 v2.8.11 (Debugging) (Snapshot: rev. 10454)
Running on: Linux 2.6.31-22-generic i686
[2] fprintf in stdio2.h:99
[3] wxFatalSignalHandler in /home/rrm/temp-amule/build/lib/libwx_baseud-2.8.so.0[0xcc7ddd]
[4] ?? in [0x905400]
[5] ?? in /home/rrm/temp-amule/build/lib/libwx_gtk2ud_core-2.8.so.0 [0x10dd07a]
[6] ?? in /usr/lib/libgdk-x11-2.0.so.0 [0x6b2f7c]
[7] ?? in /lib/libglib-2.0.so.0 [0x1634dab]
[8] g_main_context_dispatch in /lib/libglib-2.0.so.0[0x15fde88]
[9] ?? in /lib/libglib-2.0.so.0 [0x1601730]
[10] g_main_loop_run in /lib/libglib-2.0.so.0[0x1601b9f]
[11] gtk_main in /usr/lib/libgtk-x11-2.0.so.0[0x914e419]
[12] wxEventLoop::Run() in /home/rrm/temp-amule/build/lib/libwx_gtk2ud_core-2.8.so.0[0x10db089]
[13] wxAppBase::MainLoop() in /home/rrm/temp-amule/build/lib/libwx_gtk2ud_core-2.8.so.0[0x117cc53]
[14] wxAppBase::OnRun() in /home/rrm/temp-amule/build/lib/libwx_gtk2ud_core-2.8.so.0[0x117cdb3]
[15] wxEntry(int&, wchar_t**) in /home/rrm/temp-amule/build/lib/libwx_baseud-2.8.so.0[0xc51224]
[16] wxEntry(int&, char**) in /home/rrm/temp-amule/build/lib/libwx_baseud-2.8.so.0[0xc512ea]
[17] main in amule-gui.cpp:93
[18] __libc_start_main in /lib/tls/i686/cmov/libc.so.6[0xd7ab56]
[19] _start in start.S:122
--------------------------------------------------------------------------------
Aborted
So, how to link this mule to the libs statically, so that we can start it using gdb
and get a good backtrace?