aMule Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We're back! (IN POG FORM)

Author Topic: crash report (Debian testing version)  (Read 3059 times)

aidiaghe

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
crash report (Debian testing version)
« on: August 30, 2006, 12:14:44 AM »
I got the following crash twice in a few days.
I leave a little of context before in case it helps (not sure it is related).

Code: [Select]
Invalid Kad tag; type=0xce name=0x00
Error on CKademliaUDPListener::processPublishRequest received from: :
No ip match

(amule:4273): GLib-WARNING **: giounix.c:400Error while getting flags for FD: Bad file descriptor (9)


--------------------------------------------------------------------------------
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.3 using wxGTK2 v2.6.3 (Unicoded)
Running on: Linux 2.6.16-2-k7 i686

[2] wxThreadHelperThread::~wxThreadHelperThread() in amule [0x80807af]
[3] wxFatalSignalHandler in /usr/lib/libwx_baseu-2.6.so.0[0xa76cfb16]
[4] ?? in [0xffffe420]
[5] ?? in [0x915605d]
[6] ?? in /usr/lib/libgdk-x11-2.0.so.0 [0xa705837e]
[7] ?? in /usr/lib/libglib-2.0.so.0 [0xa6e2e7df]
[8] g_main_context_dispatch in /usr/lib/libglib-2.0.so.0[0xa6e05e2c]
[9] ?? in /usr/lib/libglib-2.0.so.0 [0xa6e09176]
[10] g_main_loop_run in /usr/lib/libglib-2.0.so.0[0xa6e09537]
[11] gtk_main in /usr/lib/libgtk-x11-2.0.so.0[0xa71ec4e1]
[12] wxEventLoop::Run() in /usr/lib/libwx_gtk2u_core-2.6.so.0[0xa784fceb]
[13] wxAppBase::MainLoop() in /usr/lib/libwx_gtk2u_core-2.6.so.0[0xa78e77ae]
[14] wxAppBase::OnRun() in /usr/lib/libwx_gtk2u_core-2.6.so.0[0xa78e6e51]
[15] wxEntry(int&, wchar_t**) in /usr/lib/libwx_baseu-2.6.so.0[0xa7673c0a]
[16] wxEntry(int&, char**) in /usr/lib/libwx_baseu-2.6.so.0[0xa7673cb6]
[17] CryptoPP::IteratedHash, 64u, CryptoPP::HashTransformation>::~IteratedHash() in amule [0x8127710]
[18] __libc_start_main in /lib/tls/libc.so.6[0xa73cdeb0]
[19] __gxx_personality_v0 in amule[0x807cd01]


--------------------------------------------------------------------------------

A suggestion: it is long and difficult to check one's crash does not already
look like one of the most frequent ones. Why not set up a small CGI to receive
them and recognize them, count the "popularity" of the various crashes, etc.?
Logged

aidiaghe

  • Approved Newbie
  • *
  • Karma: 0
  • Offline Offline
  • Posts: 7
RE: crash report (Debian testing version)
« Reply #1 on: August 30, 2006, 08:01:57 PM »
I compiled the program as suggested here:
http://www.amule.org/wiki/index.php/Backtraces

in order to produce an easier-to-use backtrace.

No luck though:

Code: [Select]
[New Thread - (LWP )]
[...]
[Thread - (zombie) exited]
Segmentation fault (core dumped)
$ file core
core: ELF 32-bit LSB core file Intel 80386, version 1 (SYSV), SVR4-style, from 'gdb'
What now? recompile gdb with debugging information? This will never end...

In case this helps: the core was dumped at the same time a file was completely downloaded
and saved locally (with a custom command I set up for that).

gdb quit but aMule continues to run apparently happily.
Logged