This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Cannot find thread XXXX: invalid thread handle
- From: Jose Luis Marchetti <joseluismarchetti at yahoo dot com dot br>
- To: gdb at sourceware dot org
- Date: Sat, 25 Jul 2009 15:29:15 -0700 (PDT)
- Subject: Cannot find thread XXXX: invalid thread handle
Hi,
This happens right after a process that my program forked exits.
I can see GDB logging thread 6151 was created when I fork the process, then later I also can see GDB logging the thread 6151 exited when the forked process exit(0).
So far so good, but then later GDB shows the error message and I can't do anything to make it work again, it respond with the error message at every command I tried ( including trying to exit from GDB ).
I have found a similar post in this list, but there is no useful answer in the reply.
Also I have seen some old posts complaining about problems with thread exit in GDB.
But I am not sure what it is. Fork is a very powerful tool to abandon.
Here is exactly what GDB shows:
[Thread 6151 (LWP 299) exited]
Cannot find thread 6151: invalid thread handle
(gdb) c
Cannot find thread 6151: invalid thread handle
Thanks in advance!
José Luís Marchetti
____________________________________________________________________________________
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com