aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Crashing after a while.  (Read 1306 times)

jonas

  • Newbie
  • Karma: 0
  • Offline Offline
  • Posts: 2
    • Jonas Kvinge
Crashing after a while.
« on: July 30, 2007, 07:17:03 PM »

Terminated after throwing an instance of 'std::bad_alloc'
   what(): St9bad_alloc
* Could not get symbol names for backtrace

--------------------------------------------------------------------------------
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.1.3 using wxGTK2 v2.6.3 (Unicoded)
Running on: Linux 2.6.18.8-0.5-default i686

* Could not get symbol names for backtrace


--------------------------------------------------------------------------------
Initialising aMule
Checking if there is an instance already running...
No other instances are running.
HTTP download thread started
Loading temp files from /home/jonas/.aMule/Temp.

Loading PartFile 1 of 20
Loading PartFile 2 of 20
Loading PartFile 3 of 20
Loading PartFile 4 of 20
Loading PartFile 5 of 20
Loading PartFile 6 of 20
Loading PartFile 7 of 20
Loading PartFile 8 of 20
Loading PartFile 9 of 20
Loading PartFile 10 of 20
Loading PartFile 11 of 20
Loading PartFile 12 of 20
Loading PartFile 13 of 20
Loading PartFile 14 of 20
Loading PartFile 15 of 20
Loading PartFile 16 of 20
Loading PartFile 17 of 20
Loading PartFile 18 of 20
Loading PartFile 19 of 20
Loading PartFile 20 of 20
All PartFiles Loaded.
ListenSocket: Ok.

External connections disabled in config file
*** Server UDP socket (TCP+3) at 0.0.0.0:4665
*** TCP socket (TCP) listening on 0.0.0.0:4662
*** Client UDP socket (extended eMule) at 0.0.0.0:4672
Adding file /home/jonas/.aMule/Temp/021.part.met to shares
Adding file /home/jonas/.aMule/Temp/016.part.met to shares
Adding file /home/jonas/.aMule/Temp/014.part.met to shares
Adding file /home/jonas/.aMule/Temp/013.part.met to shares
Adding file /home/jonas/.aMule/Temp/012.part.met to shares
Adding file /home/jonas/.aMule/Temp/011.part.met to shares
Adding file /home/jonas/.aMule/Temp/010.part.met to shares
Adding file /home/jonas/.aMule/Temp/009.part.met to shares
Adding file /home/jonas/.aMule/Temp/007.part.met to shares
Adding file /home/jonas/.aMule/Temp/006.part.met to shares
Adding file /home/jonas/.aMule/Temp/002.part.met to shares
Empty dir /home/jonas/Shared/ shared
Host: amule.sourceforge.net:80
URL: http://amule.sourceforge.net/lastversion
Response: 200 (Error: 0)
Download size: 6
HTTP download thread ended
/home/jonas/bin/amule.sh: line 31: 30915 Aborted                 $amulebinfile
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4319
Re: Crashing after a while.
« Reply #1 on: July 30, 2007, 07:36:52 PM »

Sorry, unforunately there are no information pointing to the source of the crash.

Also we prefer bug reports for current aMule snapshots (http://amule.hirnriss.net) compiled against wxGTK 2.8 as most bugs of 2.1.3 are already fixed and we dropped support for wx2.6 some time ago.
Logged