aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Pages: 1 [2]

Author Topic: crash in ubuntu jaunty  (Read 11265 times)

Festor

  • Hero Member
  • *****
  • Karma: 79
  • Offline Offline
  • Posts: 935
  • Offline -> Studying...
Re: crash in ubuntu jaunty
« Reply #15 on: July 02, 2009, 06:05:32 PM »

You saw this?

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: crash in ubuntu jaunty
« Reply #16 on: July 02, 2009, 06:08:51 PM »

@Festor: Huh? I believe Saahk did everything right - he made a nice GDB backtrace containing good information just as our wiki instructions say.
Logged

Festor

  • Hero Member
  • *****
  • Karma: 79
  • Offline Offline
  • Posts: 935
  • Offline -> Studying...
Re: crash in ubuntu jaunty
« Reply #17 on: July 02, 2009, 06:17:36 PM »

@Festor: Huh? I believe Saahk did everything right - he made a nice GDB backtrace containing good information just as our wiki instructions say.

I have not said it has not done so. Just answered what he wrote.

i don't know gdb, maybe i haven't  done things correctly !

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: crash in ubuntu jaunty
« Reply #18 on: July 02, 2009, 06:28:09 PM »

Ah, OK. I interpreted your reply as "rtfm", but it seems you intended to say "yes, everything done as in the wiki".
Logged

Saahk

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 5
Re: crash in ubuntu jaunty
« Reply #19 on: July 02, 2009, 10:09:53 PM »

I've seen the wiki but this is the first time i use gdb  so i do things without necessarily understanding.

I just saw i forgot to create the ~/.gdbinit file. With this file, the backtrace seems much smaller :

Code: [Select]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fee1f8cb7e0 (LWP 18400)]
0x0000000000464f63 in CUpDownClient::ClearDownloadBlockRequests (this=0x41a3490)
    at ../../src/BaseClient.cpp:1177
1177 in ../../src/BaseClient.cpp
Logged

wuischke

  • Developer
  • Hero Member
  • *****
  • Karma: 183
  • Offline Offline
  • Posts: 4292
Re: crash in ubuntu jaunty
« Reply #20 on: July 03, 2009, 06:31:51 AM »

You might notice two things:
a) There's a different file mentioned this time, i.e. the crash manifested at a different place.
Quote from: the last backtrace
[Switching to Thread 0x7f48c6ff47e0 (LWP 11480)]
0x0000000000626816 in CPartFile::ClientStateChanged (this=0x3200000070,
    oldState=0, newState=1) at ../../src/PartFile.cpp:3629
b) No one typed "bt", "bt full" or "thread apply bt all" the second time and hence there's no output to these commands. ;)
Logged

Stu Redman

  • Administrator
  • Hero Member
  • *****
  • Karma: 214
  • Offline Offline
  • Posts: 3739
  • Engines screaming
Re: crash in ubuntu jaunty
« Reply #21 on: July 03, 2009, 09:29:31 PM »

Quote from: the last backtrace
[Switching to Thread 0x7f48c6ff47e0 (LWP 11480)]
0x0000000000626816 in CPartFile::ClientStateChanged (this=0x3200000070,
    oldState=0, newState=1) at ../../src/PartFile.cpp:3629

Do you remember what you did? Especially - did you cancel a download shortly before? Or was a download finished shortly before?
« Last Edit: July 03, 2009, 09:31:53 PM by Stu Redman »
Logged
The image of mother goddess, lying dormant in the eyes of the dead, the sheaf of the corn is broken, end the harvest, throw the dead on the pyre -- Iron Maiden, Isle of Avalon
Pages: 1 [2]