aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  


We're back! (IN POG FORM)

Author Topic: aMule has crashed: BACKTRACE  (Read 1790 times)


  • Jr. Member
  • **
  • Karma: 1
  • Offline Offline
  • Posts: 54
aMule has crashed: BACKTRACE
« on: September 14, 2014, 10:46:54 PM »

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule 2.3.1 compiled with wxGTK2 v2.8.12
Running on: Linux 3.2.0-4-amd64 x86_64

[2] ?? in amule[0x46288f]
[3] wxFatalSignalHandler in /usr/lib/x86_64-linux-gnu/[0x7f040ba6a54c]
[4] ?? in /lib/x86_64-linux-gnu/[0x7f040d765030]
[5] ?? in amule[0x57e8d0]
[6] ?? in amule[0x4e158d]
[7] ?? in amule[0x5d1019]
[8] wxThreadInternal::PthreadStart(wxThread*) in /usr/lib/x86_64-linux-gnu/[0x7f040ba6630b]
[9] ?? in /lib/x86_64-linux-gnu/[0x7f040d75cb50]
[10] clone in /lib/x86_64-linux-gnu/[0x7f040acf7e6d]
- Operating System: Debian wheezy (stable)
- aMule version:  aMule 2.3.1
- Platform: 64 bits with 8GiB RAM.
- What you were doing when the problem occurred: nothing: I was out of the house.
- Using amule gui.
- At last but not least, it would be a great help to generate a backtrace to facilitate the work of the developers.   --->  The requested URL /index.php/Backtraces was not found on this server.

I don't know if this information can be useful. I have followed the instructions:
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:
If possible, please try to generate a real backtrace of this crash:




  • The current man in charge of most things.
  • Administrator
  • Hero Member
  • *****
  • Karma: 166
  • Offline Offline
  • Posts: 2683
Re: aMule has crashed: BACKTRACE
« Reply #1 on: September 15, 2014, 10:59:36 AM »   --->  The requested URL /index.php/Backtraces was not found on this server.
Fixed the link.

Unfortunately this backtrace is of no use, because it doesn't contain any debugging information. Therefore we can't tell where and what went wrong, and, most importantly, why.
concordia cum veritate