It crashed again, after about 12 hours running, again i wasnt at the machine when it happened and this time there isnt a ghost amule window running.
Oh and BTW i just realized i said i was using ubuntu, my mistake, its debian sarge what im using, ill see if i can edit the first post.
Surprise! the gdb commands only produce this output, weird, aint it?:
Adding file /xmule/Temp/003.part.met to shares
Adding file /xmule/Temp/011.part.met to shares
Adding file /xmule/Temp/046.part.met to shares
Adding file /xmule/Temp/042.part.met to shares
Adding file /xmule/Temp/051.part.met to shares
Adding file /xmule/Temp/013.part.met to shares
Adding file /xmule/Temp/075.part.met to shares
Adding file /xmule/Temp/004.part.met to shares
[New Thread 1130617776 (LWP 24879)]
[Thread 1130617776 (zombie) exited]
[New Thread 1130617776 (LWP 24885)]
[New Thread 1139006384 (LWP 24891)]
[New Thread 1122229168 (LWP 24892)]
[Thread 1130617776 (zombie) exited]
[Thread 1139006384 (zombie) exited]
[Thread 1122229168 (zombie) exited]
Couldn't get registers: No existe tal proceso.
(gdb) bt
Cannot fetch general-purpose registers for thread 1122229168: generic error
(gdb) bt full
Cannot fetch general-purpose registers for thread 1122229168: generic error
(gdb) thread apply all bt
Cannot find new threads: generic error
(gdb)
I edit the post to show you the output of gdb when i tried to run amule again:
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n)y
thread_db_get_info: cannot get thread info: generic error
looks like it was still running?? As it didnt let me run it again i had to exit gdb and start it again.
Thanks for looking into it.