aMule Forum
English => Backtraces => Topic started by: Eumel71 on October 09, 2010, 11:09:35 PM
-
Backtrace:
----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule 2.2.6 using wxGTK2 v2.8.10
Running on: Linux 2.6.32-25-generic i686
[2] ?? in amule[0x8084a89]
[3] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.8.so.0[0x36ea56]
[4] ?? in [0x1c8400]
[5] ?? in amule[0x8094943]
[6] ?? in amule[0x80b9890]
[7] ?? in amule[0x80997cc]
[8] ?? in amule[0x80a0a39]
[9] ?? in amule[0x80a1030]
[10] ?? in amule[0x808a68f]
[11] wxAppConsole::HandleEvent(wxEvtHandler*, void (wxEvtHandler::*)(wxEvent&), wxEvent&) const in /usr/lib/libwx_baseu-2.8.so.0[0x2cba9f]
[12] wxEvtHandler::ProcessEventIfMatches(wxEventTableEntryBase const&, wxEvtHandler*, wxEvent&) in /usr/lib/libwx_baseu-2.8.so.0[0x36a209]
[13] wxEventHashTable::HandleEvent(wxEvent&, wxEvtHandler*) in /usr/lib/libwx_baseu-2.8.so.0[0x36b2d4]
[14] wxEvtHandler::ProcessEvent(wxEvent&) in /usr/lib/libwx_baseu-2.8.so.0[0x36b3d3]
[15] wxEvtHandler::ProcessPendingEvents() in /usr/lib/libwx_baseu-2.8.so.0[0x36a6a9]
[16] wxAppConsole::ProcessPendingEvents() in /usr/lib/libwx_baseu-2.8.so.0[0x2cbde9]
[17] wxAppBase::ProcessIdle() in /usr/lib/libwx_gtk2u_core-2.8.so.0[0x119065f]
[18] ?? in /usr/lib/libwx_gtk2u_core-2.8.so.0[0x10e42c3]
[19] ?? in /lib/libglib-2.0.so.0[0x4f19661]
[20] g_main_context_dispatch in /lib/libglib-2.0.so.0[0x4f1b5e5]
[21] ?? in /lib/libglib-2.0.so.0[0x4f1f2d8]
[22] g_main_loop_run in /lib/libglib-2.0.so.0[0x4f1f817]
[23] gtk_main in /usr/lib/libgtk-x11-2.0.so.0[0x145d3c9]
[24] wxEventLoop::Run() in /usr/lib/libwx_gtk2u_core-2.8.so.0[0x10fd708]
[25] wxAppBase::MainLoop() in /usr/lib/libwx_gtk2u_core-2.8.so.0[0x11904de]
[26] wxAppBase::OnRun() in /usr/lib/libwx_gtk2u_core-2.8.so.0[0x11900d1]
[27] wxEntry(int&, wchar_t**) in /usr/lib/libwx_baseu-2.8.so.0[0x30579a]
[28] wxEntry(int&, char**) in /usr/lib/libwx_baseu-2.8.so.0[0x305977]
[29] ?? in amule[0x815a5db]
[30] __libc_start_main in /lib/tls/i686/cmov/libc.so.6[0x642bd6]
[31] ?? in amule[0x8083a31]
--------------------------------------------------------------------------------
this is on Ubuntu 10.04.
until a few days ago no problem, running fine, from one point on aMule crashes after a short time running.
gdb backtrace might be a little difficult, since this box is not set up as a developing machine, not sure if it will compile amule at all...
Regards
Eumel
-
This is probably fixed in the SVN version.
-
hmmm... or it is/was an Ubuntu problem.
I updated to Maverick r.c. this morning and aMule runs for ~4 hours without crash now.
Let's see...
Regards
Eumel
-
If it is what I have in mind it depends on timing in client communication. Some clients responding with a certain delay can cause it. And if you finish the download these clients share the problem goes away.
Oh, and why bother with Maverick rc now that Maverick release is available? I installed it this morning.
-
I keep watching the topic ;)
I just updated the last of my machines (the netbook) and stil got no official Maverick :-(
But the r.c. becomes the official with the next bunch of updates, so no problem.:-)
Regards
Eumel
-
Hi,
I still sometimes have crashes when I have many files in the download list. So I invented a simple workaround. I wrote a shell script that checks every minute if aMule is running. If not it issues the current time and a short message (for my couriosity :-) ) the restarts aMule.
here it is:
#!/bin/bash
echo .
date
echo aMule Watchdog gestartet
echo .
while [ True ]; do
pgrep amule > nul
notfound=$?
#echo ${notfound}
if [ $notfound -eq 1 ]; then
echo .
echo .
echo ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
echo .
date
echo "amule nicht gefunden => starte"
echo .
echo ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
echo .
# nohup amule
amule &
fi
sleep 10
done
I called it watchdog an run it from a shell window. So aMule may crash but when running unattended I do not lose hours to the manual restart.
Maybe it helps someone...
Greetings
Eumel