aMule Forum

English => Backtraces => Topic started by: skolnick on March 24, 2005, 12:20:42 AM

Title: never finished :(
Post by: skolnick on March 24, 2005, 12:20:42 AM

Hi!

I just closed amule, because needed to restart. Since i always start it from console, I know when it flushes the parts and finishes, but after closing it, nothing happenned. The console remained the same, and never started flushing the parts. As Xaignar suggested, i attached gdb to it, here's the bt:

Code: [Select]

(gdb) bt
#0  0xd22335f0 in wxEvtHandler::ProcessEvent ()
   from /usr/local/lib/libwx_base-2.5.so.4.0.0
#1  0xd22333f9 in wxEvtHandler::ProcessPendingEvents ()
   from /usr/local/lib/libwx_base-2.5.so.4.0.0
#2  0xd21ba100 in wxAppConsole::ProcessPendingEvents ()
   from /usr/local/lib/libwx_base-2.5.so.4.0.0
#3  0xd23d7bf8 in wxapp_pending_callback ()
   from /usr/local/lib/libwx_gtk_core-2.5.so.4.0.0
#4  0xd1c00dae in g_idle_dispatch (source_data=0xd23d7bc0,
    dispatch_time=0x8046ea0, user_data=0x0) at gmain.c:1367
#5  0xd1bffd9a in g_main_dispatch (dispatch_time=0x8046ea0) at gmain.c:656
#6  0xd1c003a7 in g_main_iterate (block=1, dispatch=1) at gmain.c:877
#7  0xd1c0053c in g_main_run (loop=0x8981a88) at gmain.c:935
#8  0xd1d3c837 in gtk_main () at gtkmain.c:524
#9  0xd23ec6f9 in wxEventLoop::Run ()
   from /usr/local/lib/libwx_gtk_core-2.5.so.4.0.0
#10 0xd2459f71 in wxAppBase::MainLoop ()
   from /usr/local/lib/libwx_gtk_core-2.5.so.4.0.0
#11 0xd245a0ab in wxAppBase::OnRun ()
   from /usr/local/lib/libwx_gtk_core-2.5.so.4.0.0
#12 0xd21ea30f in wxEntry () from /usr/local/lib/libwx_base-2.5.so.4.0.0
#13 0x082c30a3 in main (argc=1, argv=0x8047044) at amule-gui.cpp:297
(gdb)
and here's the bt full (just in case)

Code: [Select]

(gdb) bt full
#0  0xd22335f0 in wxEvtHandler::ProcessEvent ()
   from /usr/local/lib/libwx_base-2.5.so.4.0.0
No symbol table info available.
#1  0xd22333f9 in wxEvtHandler::ProcessPendingEvents ()
   from /usr/local/lib/libwx_base-2.5.so.4.0.0
No symbol table info available.
#2  0xd21ba100 in wxAppConsole::ProcessPendingEvents ()
   from /usr/local/lib/libwx_base-2.5.so.4.0.0
No symbol table info available.
#3  0xd23d7bf8 in wxapp_pending_callback ()
   from /usr/local/lib/libwx_gtk_core-2.5.so.4.0.0
No symbol table info available.
#4  0xd1c00dae in g_idle_dispatch (source_data=0xd23d7bc0,
    dispatch_time=0x8046ea0, user_data=0x0) at gmain.c:1367
        source_data = 0x1
#5  0xd1bffd9a in g_main_dispatch (dispatch_time=0x8046ea0) at gmain.c:656
        was_in_call = 0
        hook_data = 0x0
        source_data = 0xd23d7bc0
        dispatch = (gboolean (*)(void)) 0xd1c00d90
        need_destroy = -775811936
        source = (GSource *) 0x883e400
#6  0xd1c003a7 in g_main_iterate (block=1, dispatch=1) at gmain.c:877
        block = 148108408
        hook = (GHook *) 0x8d3f478
        current_time = {tv_sec = 1111584279, tv_usec = 871305}
        n_ready = 1
        current_priority = 900
        timeout = 0
        retval = 0
#7  0xd1c0053c in g_main_run (loop=0x8981a88) at gmain.c:935
        loop = (GMainLoop *) 0x8981a88
#8  0xd1d3c837 in gtk_main () at gtkmain.c:524
        tmp_list = (GList *) 0x0
        functions = (GList *) 0x0
        init = (GtkInitFunction *) 0x8981a98
        loop = (GMainLoop *) 0x8981a88
#9  0xd23ec6f9 in wxEventLoop::Run ()
   from /usr/local/lib/libwx_gtk_core-2.5.so.4.0.0
No symbol table info available.
#10 0xd2459f71 in wxAppBase::MainLoop ()
   from /usr/local/lib/libwx_gtk_core-2.5.so.4.0.0
No symbol table info available.
#11 0xd245a0ab in wxAppBase::OnRun ()
   from /usr/local/lib/libwx_gtk_core-2.5.so.4.0.0
No symbol table info available.
#12 0xd21ea30f in wxEntry () from /usr/local/lib/libwx_base-2.5.so.4.0.0
No symbol table info available.
#13 0x082c30a3 in main (argc=1, argv=0x8047044) at amule-gui.cpp:297
No locals.
(gdb)
Thanks.

Title: Re: never finished :(
Post by: phoenix on March 24, 2005, 04:05:00 AM

skolnick,

I don't see a crash there. Maybe it just received a signal. Did you try cont? What was the gdb message for the stop?

Cheers!

Title: Re: never finished :(
Post by: Xaignar on March 24, 2005, 11:43:08 AM

It was no crash, as the topic said, aMule never finished, so it got stuck in a infinite loop somewhere I guess.

Title: Re: never finished :(
Post by: phoenix on March 24, 2005, 01:49:12 PM

Well, not much info here. It got stuck inside wx event loop. Maybe a wx problem with solaris?

Title: Re: never finished :(
Post by: skolnick on March 24, 2005, 07:29:58 PM

don't think is a problem with amule on solaris, since previous versions of amule never did this, and this new CVS version has done it 2 out of 3 times I've tried to close it.

Regards.

Title: Re: never finished :(
Post by: phoenix on March 25, 2005, 03:40:11 AM

skolnick,

What was the platform you were running aMule? I guess the answer is: Solaris. So this _is_ a problem with aMule on Solaris :D Ok, maybe a problem of latest aMule cvs on Solaris. If this also happens in other platforms, then it is not an exclusive problem of Solaris ;) Anyway, I can not repeat it here on Linux.

Maybe if you have some (a lot) of patience, you could compile wx with debug info and try to understand why is wx stuck in this event loop.

Good luck! ;)