Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[JAngel2000]

Terminated after throwing an instance of 'std::bad_alloc'
        what(): St9bad_alloc

--------------------------------------------------------------------------------
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.8.1 (Unicoded)
Running on: Linux 2.6.20-16-generic i686

* Could not get symbol names for backtrace


--------------------------------------------------------------------------------
Cancelado (core dumped)



That's what I get after some few hours of starting aMule. Any idea of how to solve it?

Thanks a lot everybody

[wuischke]

You are on FreeBSD, aren't you?

Anyway, can you give use some details on this crash? Also try to use "make -g" (iirc) when compiling aMule to enable debug information on BSD.

[JAngel2000]

No

It's Ubuntu Feisty Fawn. That's all I can say. I start the aMule and after some hours it crashes and after a while it closes itself.

[wuischke]

Oh, yes, stupid me. It even says so in the output...but there are no debug information, so we don't know why it crashes.

Anyway, could you please try a developmental version? (See http://forum.amule.org/index.php?topic=12458.0 for Ubuntu packages) Hopefully this is already fixed there.

[mr_hyde]

Noticed same problem with CVS version 20071106 on KUbuntu 7.10, wxWidgets 2.8.6

I will re-build aMule with debug options to get more info.

I was forgetting; I don't know if this can be useful: I'm sure that a lot of file were "in hashing" (I started aMule with about 350 files to hash and when I re-started aMule this morning after the crash I noticed about 10 files remaining to hash)

Bye,
  Mr Hyde