- Package:
- amule-daemon
- Source:
- amule
- Description:
- non-graphic version of aMule, a client for the eD2k and Kad networks
- Submitter:
- Marc Coll
- Date:
- 2014-09-07 14:45:18 UTC
- Severity:
- normal
Dear Maintainer, Sometimes amule daemon crashes on system startup. It doesn't seem to be following any kind of patterm, it just crashes randomly from time to time. But when I start it again it works fine. This is the error message I get on the console: [....] Starting aMule daemon: amuled -------------------------------------------------------------------------------- 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/index.php?board=67.0 If possible, please try to generate a real backtrace of this crash: http://wiki.amule.org/index.php/Backtraces ----------------------------=| BACKTRACE FOLLOWS: |=---------------------------- Current version is: aMuleD 2.3.1 compiled with wxGTK2 v2.8.12 Running on: Linux 3.12-1-amd64 x86_64 [2] wxStringData::Unlock() in /usr/bin/amuled[0x43199f] [3] wxFatalSignalHandler in /usr/lib/x86_64-linux- gnu/libwx_baseu-2.8.so.0[0x7f731113e9fc] [4] ?? in /lib/x86_64-linux-gnu/libpthread.so.0[0x7f7312551890] [5] CryptoPP::RandomPool::~RandomPool() in /usr/bin/amuled[0x5602cf] [6] CryptoPP::RandomPool::~RandomPool() in /usr/bin/amuled[0x5614ee] [7] CryptoPP::RandomPool::~RandomPool() in /usr/bin/amuled[0x5667d0] [8] wxStringData::Unlock() in /usr/bin/amuled[0x4340d0] [9] wxStringData::Unlock() in /usr/bin/amuled[0x43acb8] [10] ?? in /usr/bin/amuled[0x430c70] [11] wxEntry(int&, wchar_t**) in /usr/lib/x86_64-linux- gnu/libwx_baseu-2.8.so.0[0x7f73110e8f6c] [12] ?? in /usr/bin/amuled[0x42a042] [13] __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6[0x7f73104a7b45] [14] ?? in /usr/bin/amuled[0x42ed0b] -------------------------------------------------------------------------------- Aborted [FAIL] startpar: service(s) returned failure: amule-daemon ... failed!
Hello Marc, sadly this error by itself is not helpful to debug it. Could you please install amule-dbg and run amuled into gdb and - when the crash happens - issue these commands: bt bt full thread apply all bt ? Thanks, Sandro
Hello. I installed the amule-dbg package as you suggested, and today it has crashed again. Perphaps this will be more helpful:----------------------------=| BACKTRACE FOLLOWS: |=---------------------------- Current version is: aMuleD 2.3.1 compiled with wxGTK2 v2.8.12 Running on: Linux 3.12-1-amd64 x86_64 [2] CamuleApp::OnFatalException() in amule.cpp:1021 [3] wxFatalSignalHandler in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7fa567cb49fc] [4] ?? in /lib/x86_64-linux-gnu/libpthread.so.0[0x7fa5690c7890] [5] CUPnPService::Execute(std::string const&, std::vector<CUPnPArgumentValue, std::allocator<CUPnPArgumentValue> > const&) const in stl_tree.h:1803 [6] std::_Rb_tree_iterator<std::pair<std::string const, CUPnPService*> [7] CUPnPControlPoint::AddPortMappings(std::vector<CUPnPPortMapping, std::allocator<CUPnPPortMapping> >&) in UPnPBase.cpp:968 [8] ~wxStringBase in string.h:396 [9] CamuleApp::OnInit() in amule.cpp:519 [10] CamuleDaemonApp::OnInit() in amuled.cpp:612 [11] wxEntry(int&, wchar_t**) in /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0[0x7fa567c5ef6c] [12] main in amuled.cpp:118 [13] __libc_start_main in /lib/x86_64-linux-gnu/libc.so.6[0x7fa56701db45] [14] ?? in /usr/bin/amuled[0x42ed0b] -------------------------------------------------------------------------------- Aborted [FAIL] startpar: service(s) returned failure: amule-daemon ... failed!
Hello Marc, it is not :( as said in the first reply, you have to run amuled with gdb ($ gdb amuled ; run), else the amule-dbg symbols won't be loaded. Regards,
I have already tried runing it with gdb, but the error doesn't show up. It only crashes from time to time.
Then I suggest to run amuled every time in gdb and wait for it to crash: without the gdb tracebacks we don't have enough information to work on it. Regards,