aMule Bug Tracker - aMule
View Issue Details
0000318aMuleMessagespublic2005-03-07 19:552005-03-07 22:27
murphy 
 
normalcrashsometimes
closedopen 
2.0.0-rc8 
 
0000318: amule crash
--------------------------------------------------------------------------------
OOPS! Houston, we have a situation: seems like aMule crashed!
Please, post these lines on the backtrace forum on http://www.amule.org/ [^]
aMule version is: 2.0.0rc8 using wxGTK1 v2.4.2
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
 
[0] CamuleApp::OnFatalException() in amule.cpp:979
[1] wxFatalSignalHandler in /usr/lib/libwx_gtk-2.4.so[0x403ed8b6]
[2] ?? in /lib/i686/libpthread.so.0 [0x400315ce]
[3] ?? in /lib/i686/libc.so.6 [0x40a203b8]
[4] CClientReqSocket::ProcessExtPacket(char const*, unsigned, unsigned char) in ListenSocket.cpp:1623
[5] CClientReqSocket::PacketReceived(Packet*) in ListenSocket.cpp:2069
[6] CEMSocket::OnReceive(int) in EMSocket.cpp:261
[7] CClientReqSocket::OnReceive(int) in ListenSocket.cpp:2087
[8] CEMSocket::SetDownloadLimit(unsigned) in EMSocket.cpp:286
[9] CUpDownClient::SetDownloadLimit(unsigned) in BaseClient.cpp:2087
[10] CPartFile::Process(unsigned, unsigned char) in PartFile.cpp:1609
[11] CDownloadQueue::Process() in DownloadQueue.cpp:378
[12] CamuleApp::OnCoreTimer(wxTimerEvent&) in amule.cpp:1378
[13] wxEvtHandler::SearchEventTable(wxEventTable&, wxEvent&) in /usr/lib/libwx_gtk-2.4.so[0x40317c7a]
[14] wxEvtHandler::ProcessEvent(wxEvent&) in /usr/lib/libwx_gtk-2.4.so[0x40317aa1]
[15] wxTimerBase::Notify() in /usr/lib/libwx_gtk-2.4.so[0x403acc43]
[16] timeout_callback in /usr/lib/libwx_gtk-2.4.so[0x402cf8b8]
[17] ?? in /usr/lib/libglib-1.2.so.0 [0x40810c6b]
[18] ?? in /usr/lib/libglib-1.2.so.0 [0x408113ee]
[19] ?? in /usr/lib/libglib-1.2.so.0 [0x40811199]
[20] g_main_run in /usr/lib/libglib-1.2.so.0[0x40810174]
[21] gtk_main in /usr/lib/libgtk-1.2.so.0[0x40715ccd]
 
--------------------------------------------------------------------------------
Running Mandrake 9.1 kernel : 2.4.21-0.13mdk
Seems to occur sometimes when a transfer is completed. When restarting
the mule, I get :

Hasher: Finished hashing file: <file>
Hasher: No files on queue, stopping thread.
Hasher: A thread has died.
AICH Thread: Syncronization thread started.
AICH Thread: Masterhashes of known files have been loaded.
AICH Thread: No new files found.
AICH Thread: Thread terminated.
No tags attached.
Issue History
2005-03-07 19:55murphyNew Issue
2005-03-07 22:27GonoszTopiStatusnew => closed
2005-03-07 22:27GonoszTopiNote Added: 0000700

Notes
(0000700)
GonoszTopi   
2005-03-07 22:27   
This bug has already been fixed in current CVS. Try a recent CVS tarball or wait for 2.0.0 final release.