aMule Forum
English => aMule crashes => Topic started by: skolnick on December 23, 2004, 02:27:02 AM
-
Hi! I was very happy using my amule, it was minimized, when suddenly, no more mule!! all it left behind was this:
--------------------------------------------------------------------------------Oops, aMule crashed!
Hey, stop crying! You wanted the edge, and now you fell down?!
Please, post these lines on the backtrace forum on http://www.amule.org/
aMule version is: CVS using wxGTK2 v2.5.3
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
- CamuleApp::OnFatalException() in amule.cpp:979
[1] wxFatalSignalHandler in /usr/local/lib/libwx_base-2.5.so.3
[0xf6b43882]
[2] ?? in /lib/tls/libpthread.so.0 [0x95b8a8]
[3] CClientReqSocket::ProcessExtPacket(char const*, unsigned int, unsigned char) in ListenSocket.cpp:1623
[4] CClientReqSocket::PacketReceived(Packet*) in ListenSocket.cpp:2070
[5] CEMSocket::OnReceive(int) in EMSocket.cpp:262
[6] CUpDownClient::SetDownloadLimit(unsigned int) in BaseClient.cpp:2088
[7] CPartFile::Process(unsigned int, unsigned char) in PartFile.cpp:1611
[8] CDownloadQueue::Process() in DownloadQueue.cpp:378
[9] CamuleApp::OnCoreTimer(wxTimerEvent&) in amule.cpp:1380
[10] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) const in /usr/local/lib/libwx_base-2.5.so.3[0xf6acfe3d]
[11] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) in /usr/local/lib/libwx_base-2.5.so.3[0xf6b3eea4]
[12] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in /usr/local/lib/libwx_base-2.5.so.3[0xf6b3f185]
[13] wxEvtHandler::ProcessEvent(wxEvent&) in /usr/local/lib/libwx_base-2.5.so.3[0xf6b3fcac]
[14] wxTimerBase::Notify() in /usr/local/lib/libwx_gtk2_core-2.5.so.3[0xf6d536ba]
[15] timeout_callback in /usr/local/lib/libwx_gtk2_core-2.5.so.3[0xf6c93150]
[16] ?? in /usr/lib/libglib-2.0.so.0 [0x8922f8]
[17] g_main_context_dispatch in /usr/lib/libglib-2.0.so.0[0x88f74b]
[18] ?? in /usr/lib/libglib-2.0.so.0 [0x8911d2]
[19] g_main_loop_run in /usr/lib/libglib-2.0.so.0[0x89147f]
[20] gtk_main in /usr/lib/libgtk-x11-2.0.so.0[0xb8378e]
[21] wxEventLoop::Run() in /usr/local/lib/libwx_gtk2_core-2.5.so.3[0xf6c8c055]
[22] wxAppBase::MainLoop() in /usr/local/lib/libwx_gtk2_core-2.5.so.3[0xf6cfaf09]
[23] wxAppBase::OnRun() in /usr/local/lib/libwx_gtk2_core-2.5.so.3[0xf6cfb047]
[24] wxEntry(int&, char**) in /usr/local/lib/libwx_base-2.5.so.3[0xf6b000ab]
[25] main in amule-gui.cpp:161
[26] __libc_start_main in /lib/tls/libc.so.6[0x641e33]
[27] wxTextCtrl::GetSelection(long*, long*) const in ./amule[0x813ed71]
--------------------------------------------------------------------------------Aborted
[autizt@neptune src]$
Hope this helps someway...
Thanks.
-
Didn't it generate a core file? If it did, you can do:
$ gdb /path/to/amule core.1231
...
(gdb) bt
...
(gdb) bt full
...
and other stuff you think is pertinent. That would help more.
Cheers!
-
didn't look for the core file. Using windows now, so can't reallt look. Will look into it later.
Thanks.
BTW: RC8 crashed exactly the same random way about 4 hours after starting it.
Skolnick.
-
Hi all!
I've been looking around for the core file, but it seems there is none. I've looked into the home folder, and in the current working directory when amule crashed. o traces of it. I think something is misconfigured in Fedora/my amule, and it won't produce core files. Any idea is welcomed.
Thanks!
Skolnick.
-
skolnick,
Put this in your ~/.bashrc:
ulimit -c unlimited
Cheers!
-
Hi!
Thanks for the hint. I'll do it, only problem is now amule is not crashing anymore (or so it seems). Only thing I did was recompile it, without the --enable-optimize option, and yesterday worked just fine. Could that be the fix?
Regards.
-
skolnick,
:D Definetly not :)
It is supposed to run just fine with or without --enable-optimize. There is a bug out there somewhere.
Cheers!
-
Maybe without the --enable-optimize the -O3 is not overridden and that leads to the problem?
-
Hmm...now I remember, the times aMule crashed, I was using the webserver, but the webserver did not crash (well, once did crash, but that was some hours before amule itself crashed, so maybe it's not related) problem is, none produced a core file. The webserver did not even produced a backtrace, like amule does. Maybe the problem is with the webserver?
Regards.
-
Forget it. It just crashed again. Damn. I'll have to look for a solution to this, I can't stand this anymore. I'll do the backtrace thing, and post it ASAP.
Regards.
-
skolnick,
Remember, you can also run aMule *inside* gdb, which is probably the preferred way if you want to debug it. Just said the thing about the core file because we are not always running aMule that way, and those times, the core file comes in handy.
Cheers!
-
Thanks for the hint, I already found it at amule's wiki, in the backtraces explanation. I'll run amule tomorrow (today's bittorrent day :P) and see if I can produce a really nice backtrace for you to enjoy.
Regards.
Skolnick.