zenria,
Unfortunately, this is also not good.

the thread that crashed did so inside wxGTK lib and we have a corrupt stack, so it is not possible to trace the call inside aMule. What you can do if you have some patience is to compile wx yourself with debug information and then do another backtrace, then maybe we can find a problem inside wx code, or even a wrong parameter call inside aMule.
Anyway, the corrupt stack is misleading, the problem could be anywhere else.