aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: Amule Crash  (Read 8037 times)

Hetfield

  • Developer
  • Jr. Member
  • *****
  • Karma: 0
  • Offline Offline
  • Posts: 74
Amule Crash
« on: November 15, 2003, 10:37:43 PM »

here amule on debugger, while viewing a file with lots of sources:

cur_datarate = 0
m_nDownDatarate = 0
cur_datarate = 0
m_nDownDatarate = 0
cur_datarate = 0
m_nDownDatarate = 0
cur_datarate = 0

[CUTTED]...

cur_datarate = 0
m_nDownDatarate = 0
cur_datarate = 0
m_nDownDatarate = 0
cur_datarate = 0

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 20846)]
0x406a4f80 in mallopt () from /lib/i686/libc.so.6
(gdb) bt
#0  0x406a4f80 in mallopt () from /lib/i686/libc.so.6
#1  0x406a3dfc in free () from /lib/i686/libc.so.6
#2  0x4058bf83 in operator delete(void*) () from /usr/lib/libstdc++.so.5
(gdb)
Logged

Hetfield

  • Developer
  • Jr. Member
  • *****
  • Karma: 0
  • Offline Offline
  • Posts: 74
Re: Amule Crash
« Reply #1 on: November 15, 2003, 10:39:29 PM »

i'm just seeing that it's the real download rate.

so post is pretty useless.

sorry.
Logged

Hetfield

  • Developer
  • Jr. Member
  • *****
  • Karma: 0
  • Offline Offline
  • Posts: 74
Re: Amule Crash
« Reply #2 on: November 15, 2003, 10:40:27 PM »

m_nDownDatarate = 19058
cur_datarate = 19058

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 20918)]
0x0808c342 in CList::RemoveHead() ()
(gdb) bt
#0  0x0808c342 in CList::RemoveHead() ()
#1  0x0000000c in ?? ()
(gdb)



pretty sure it's something about lists management, expecially sorting
Logged

Hetfield

  • Developer
  • Jr. Member
  • *****
  • Karma: 0
  • Offline Offline
  • Posts: 74
Re: Amule Crash
« Reply #3 on: November 15, 2003, 10:49:14 PM »

what about this wonderful speed bug?

cur_datarate = 9474069
m_nDownDatarate = 2524
cur_datarate = 2524
m_nDownDatarate = 9474069
cur_datarate = 9474069
m_nDownDatarate = 2524
cur_datarate = 2524
m_nDownDatarate = 9474069
cur_datarate = 9474069
m_nDownDatarate = 2524
cur_datarate = 2524
m_nDownDatarate = 9474069
cur_datarate = 9474069
m_nDownDatarate = 2524
cur_datarate = 2524
m_nDownDatarate = 9474069
cur_datarate = 9474069


9MB/s!!!
and speed in the toolbar says the same.

but i have adsl 256kbit :(((
Logged

Hetfield

  • Developer
  • Jr. Member
  • *****
  • Karma: 0
  • Offline Offline
  • Posts: 74
Re: Amule Crash
« Reply #4 on: November 15, 2003, 10:55:27 PM »

always when i say to shutdown.



cur_datarate = 1442
m_nDownDatarate = 1442
cur_datarate = 1442
Signaling hashing thread to terminate

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 21013)]
0x406a4f80 in mallopt () from /lib/i686/libc.so.6
(gdb) bt
#0  0x406a4f80 in mallopt () from /lib/i686/libc.so.6
#1  0x406a3dfc in free () from /lib/i686/libc.so.6
#2  0x4058bf83 in operator delete(void*) () from /usr/lib/libstdc++.so.5
(gdb)
Logged

deltaHF

  • Evil Admin
  • Former Developer
  • Hero Member
  • *****
  • Karma: 6
  • Offline Offline
  • Posts: 3920
  • .. Legends may sleep, but they never die ..
    • http://www.amule.org
Re: Amule Crash
« Reply #5 on: November 16, 2003, 01:21:09 PM »

[jokemodus=on] damn heti .. edit your post and don't spam our board  :wink: [schild=19 fontcolor=000000 shadowcolor=C0C0C0 shieldshadow=1]uhoh, my life is too short to read your post..[/schild] [jokemodus=off]

ok, i noticed -> aMule crash if u have a lot of files in dl .. with 2 files aMule cvs was running the whole night without crash ..

Citroklar

  • Full Member
  • ***
  • Karma: 0
  • Offline Offline
  • Posts: 148
Re: Amule Crash
« Reply #6 on: November 19, 2003, 01:22:11 AM »

Creteil did a lot this night; although he has fixed most of the bugs, at least one isn't fixed yet, but aMule appears much more stable to me now.

Client sorting bug has been fixed.
Thx to Creteil!
Logged
#!/bin/ssh
#The Unix Guru's View of Sex
unzip ; strip ; touch ; grep ; finger ; mount ; fsck ; more ; yes ; umount ; sleep