aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Crash after two days  (Read 2195 times)

Aquarion

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 17
Crash after two days
« on: May 07, 2004, 06:50:07 PM »

Almost exactly two days uptime this time, before:

(Last thing I did was add something from a search list to the download queue, but this was at least five minutes later)

Code: [Select]
CPartFile::CPartFile(CSearchFile*): added tag "codec"="dx50"
CPartFile::CPartFile(CSearchFile*): added tag "length"="43:56"

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 31593)]
0x081c3e9b in CPartFile::UpdatePartsInfo ()
(gdb)
(gdb) bt
#0  0x081c3e9b in CPartFile::UpdatePartsInfo ()
#1  0x081024f9 in CUpDownClient::ProcessFileStatus ()
#2  0x080a73b4 in CClientReqSocket::ProcessPacket ()
#3  0x080ad565 in CClientReqSocket::PacketReceived ()
#4  0x080af31d in CEMSocket::OnReceive ()
#5  0x080ad65d in CClientReqSocket::OnReceive ()
#6  0x08234e4f in CamuleDlg::socketHandler ()
#7  0x4035faf2 in wxEvtHandler::SearchEventTable () from /usr/lib/libwx_gtk-2.4.so.0
#8  0x4035f961 in wxEvtHandler::ProcessEvent () from /usr/lib/libwx_gtk-2.4.so.0
#9  0x4035f82b in wxEvtHandler::ProcessPendingEvents () from /usr/lib/libwx_gtk-2.4.so.0
#10 0x403217e5 in wxAppBase::ProcessPendingEvents () from /usr/lib/libwx_gtk-2.4.so.0
#11 0x402c9096 in wxWakeUpIdle () from /usr/lib/libwx_gtk-2.4.so.0
#12 0x40756fa0 in g_timeout_add () from /usr/lib/libglib-1.2.so.0
#13 0x4075603d in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#14 0x407564f4 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
#15 0x40756724 in g_main_run () from /usr/lib/libglib-1.2.so.0
#16 0x4067cc3f in gtk_main () from /usr/lib/libgtk-1.2.so.0
#17 0x402c9a28 in wxApp::MainLoop () from /usr/lib/libwx_gtk-2.4.so.0
#18 0x40321657 in wxAppBase::OnRun () from /usr/lib/libwx_gtk-2.4.so.0
#19 0x402ca359 in wxEntry () from /usr/lib/libwx_gtk-2.4.so.0
#20 0x0822ce10 in main ()
(gdb) bt full
#0  0x081c3e9b in CPartFile::UpdatePartsInfo ()
No symbol table info available.
#1  0x081024f9 in CUpDownClient::ProcessFileStatus ()
No symbol table info available.
#2  0x080a73b4 in CClientReqSocket::ProcessPacket ()
No symbol table info available.
#3  0x080ad565 in CClientReqSocket::PacketReceived ()
No symbol table info available.
#4  0x080af31d in CEMSocket::OnReceive ()
No symbol table info available.
#5  0x080ad65d in CClientReqSocket::OnReceive ()
No symbol table info available.
#6  0x08234e4f in CamuleDlg::socketHandler ()
No symbol table info available.
#7  0x4035faf2 in wxEvtHandler::SearchEventTable () from /usr/lib/libwx_gtk-2.4.so.0
No symbol table info available.
#8  0x4035f961 in wxEvtHandler::ProcessEvent () from /usr/lib/libwx_gtk-2.4.so.0
No symbol table info available.
#9  0x4035f82b in wxEvtHandler::ProcessPendingEvents () from /usr/lib/libwx_gtk-2.4.so.0
No symbol table info available.
#10 0x403217e5 in wxAppBase::ProcessPendingEvents () from /usr/lib/libwx_gtk-2.4.so.0
No symbol table info available.
#11 0x402c9096 in wxWakeUpIdle () from /usr/lib/libwx_gtk-2.4.so.0
No symbol table info available.
#12 0x40756fa0 in g_timeout_add () from /usr/lib/libglib-1.2.so.0
No symbol table info available.
#13 0x4075603d in g_get_current_time () from /usr/lib/libglib-1.2.so.0
No symbol table info available.
#14 0x407564f4 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
No symbol table info available.
#15 0x40756724 in g_main_run () from /usr/lib/libglib-1.2.so.0
No symbol table info available.
#16 0x4067cc3f in gtk_main () from /usr/lib/libgtk-1.2.so.0
No symbol table info available.
#17 0x402c9a28 in wxApp::MainLoop () from /usr/lib/libwx_gtk-2.4.so.0
No symbol table info available.
#18 0x40321657 in wxAppBase::OnRun () from /usr/lib/libwx_gtk-2.4.so.0
No symbol table info available.
#19 0x402ca359 in wxEntry () from /usr/lib/libwx_gtk-2.4.so.0
No symbol table info available.
#20 0x0822ce10 in main ()
No symbol table info available.

If this is the socket bug, could you say how I could tell a socket-bug crash from a normal one, so I don't clog up the bt forum with repeats?
Logged