aMule Forum
English => aMule crashes => Topic started by: zekkerj on December 16, 2005, 05:23:07 AM
-
A fatal error has occurred and aMule has crashed.
Please assist us in fixing this problem by posting the backtrace below in our
'aMule Crashes' forum and include as much information as possible regarding the
circumstances of this crash. The forum is located here:
http://forum.amule.org/board.php?boardid=67
If possible, please try to generate a real backtrace of this crash:
http://www.amule.org/wiki/index.php/Backtraces
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule 2.0.3 using wxGTK2 v2.6.2
Running on: Linux 2.6.11-72032U10_17clcustom i686
[2] wxFatalSignalHandler in /usr/local/lib/libwx_base-2.6.so.0[0x406bc6ea]
[3] ?? in /lib/libpthread.so.0 [0x40053799]
[4] ?? in [0xffffe420]
[5] wxString::operator=(wxString const&) in string.h:916
[6] CUpDownClient::ProcessHelloTypePacket(CSafeMemFile const&) in BaseClient.cpp:372
[7] CUpDownClient::ProcessHelloAnswer(char const*, unsigned) in BaseClient.cpp:347
[8] CClientReqSocket::ProcessPacket(char const*, unsigned, unsigned char) in ListenSocket.cpp:282
[9] CClientReqSocket::PacketReceived(CPacket*) in ListenSocket.cpp:1766
[10] CEMSocket::OnReceive(int) in EMSocket.cpp:260
[11] CClientReqSocket::OnReceive(int) in ListenSocket.cpp:1673
[12] CClientReqSocketHandler::ClientReqSocketHandler(wxSocketEvent&) in ListenSocket.cpp:88
[13] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) const in /usr/local/lib/libwx_base-2.6.so.0[0x4061b578]
[14] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) in /usr/local/lib/libwx_base-2.6.so.0[0x406b6f60]
[15] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in /usr/local/lib/libwx_base-2.6.so.0[0x406b6445]
[16] wxEvtHandler::ProcessEvent(wxEvent&) in /usr/local/lib/libwx_base-2.6.so.0[0x406b70d8]
[17] wxEvtHandler::ProcessPendingEvents() in /usr/local/lib/libwx_base-2.6.so.0[0x406b6eb3]
[18] wxAppConsole::ProcessPendingEvents() in /usr/local/lib/libwx_base-2.6.so.0[0x4061b4f9]
[19] ?? in /usr/local/lib/libwx_gtk2_core-2.6.so.0 [0x403702cf]
[20] ?? in /usr/lib/libglib-2.0.so.0 [0x40ee1623]
[21] ?? in /usr/lib/libglib-2.0.so.0 [0x40ede262]
[22] g_main_context_dispatch in /usr/lib/libglib-2.0.so.0[0x40edf358]
[23] ?? in /usr/lib/libglib-2.0.so.0 [0x40edf690]
[24] g_main_loop_run in /usr/lib/libglib-2.0.so.0[0x40edfcd3]
[25] gtk_main in /usr/lib/libgtk-x11-2.0.so.0[0x40b38993]
[26] wxEventLoop::Run() in /usr/local/lib/libwx_gtk2_core-2.6.so.0[0x40387b39]
[27] wxAppBase::MainLoop() in /usr/local/lib/libwx_gtk2_core-2.6.so.0[0x4040e9b9]
[28] wxAppBase::OnRun() in /usr/local/lib/libwx_gtk2_core-2.6.so.0[0x4040eadf]
[29] wxEntry(int&, char**) in /usr/local/lib/libwx_base-2.6.so.0[0x4065b45a]
[30] main in amule-gui.cpp:147
[31] __libc_start_main in /lib/libc.so.6[0x4086d447]
[32] wxAppBase::Dispatch() in :0
--------------------------------------------------------------------------------
Abortado
Any idea? I's happening a few minutes after start.
-
zekkerj,
I think this is an old and fixed bug. Try using a cvs tarball and see what you get.
http://www.hirnriss.net/?area=cvs
For instructions, read our wiki:
http://www.amule.org/wiki/index.php/Main_Page
Specially this:
http://www.amule.org/wiki/index.php/Compilation_Installation
E seja bem vindo! :)
-
Any deadline for 2.1 version? I think I can force my machine to keep amule respawning for a few days, if it won't long. So I can save one compilation or two. 8)
But, can I call this an "attack"??? Are these "Hello Packets" that are causing my amule to crash (as I understood) legitimate, or is some vandal just targeting me?
Because if there is a packet signature for these "bad guys", I can use an IDS to block them.
PS: Setting up "ip filter" didn't worked.
-
zekkerj,
Like I said in the previous post, this is not an attack, this is an old and fixed bug.
There is no deadline for the release, all we can say is "soon". How soon? Ask Kry, he will be pleased to tell you :P
Cheers!
-
Soon.
-
I made a try on the "filter all messages", and amule seems to be more stable.
"Soon" is a good word when you're the right side. ;)
Seems that I'll be back to the CVS, anyway.