aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: another crash  (Read 2614 times)

IWantMyMule

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 21
another crash
« on: February 01, 2006, 09:34:24 PM »

... but the backtrace doesn't seem to be very useful ... I followed the instructions at http://www.amule.org/wiki/index.php/Backtraces.

Code: [Select]
Program received signal SIGILL, Illegal instruction.
[Switching to Thread 1085278368 (LWP 4477)]
0x08f80ec2 in ?? ()
(gdb) continue
Continuing.

--------------------------------------------------------------------------------
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:
    [URL]http://forum.amule.org/board.php?boardid=67[/URL]
If possible, please try to generate a real backtrace of this crash:
    [URL]http://www.amule.org/wiki/index.php/Backtraces[/URL]

----------------------------=| BACKTRACE FOLLOWS: |=----------------------------
Current version is: aMule 2.1.0 using wxGTK1 v2.6.2
Running on: Linux 2.6.14 i686


Program received signal SIGILL, Illegal instruction.
0x08f80ec1 in ?? ()
(gdb) continue
Continuing.
Couldn't get registers: No such process.
(gdb) bt
#0  0x08f80ec1 in ?? ()
Cannot fetch general-purpose registers for thread 1085278368: generic error
(gdb) bt full
#0  0x08f80ec1 in ?? ()
No symbol table info available.
(gdb) thread apply all bt
Cannot find new threads: generic error
(gdb)

Any ideas...?  :]
Logged

Xaignar

  • Admin and Code Junky
  • Hero Member
  • *****
  • Karma: 19
  • Offline Offline
  • Posts: 1103
Re: another crash
« Reply #1 on: February 01, 2006, 10:50:17 PM »

Yeah, not very helpful I'm afraid. Next time, you should not try to do a "continue" before creating the backtrace. Also using "thread apply all bt" would be a good idea, since aMule is a multi-threaded application, and in many cases it helps to know what's happening in all the threads.
Logged

IWantMyMule

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 21
Re: another crash
« Reply #2 on: February 02, 2006, 12:07:33 PM »

Well, that's exactly what I did  8) Perhaps the backtrace of the next crash will be more useful...
Logged