* Cannot find thread XXXX: invalid thread handle
@ 2009-07-25 22:29 Jose Luis Marchetti
2009-07-25 23:22 ` Daniel Jacobowitz
0 siblings, 1 reply; 2+ messages in thread
From: Jose Luis Marchetti @ 2009-07-25 22:29 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-07-25 23:22 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-07-25 22:29 Cannot find thread XXXX: invalid thread handle Jose Luis Marchetti
2009-07-25 23:22 ` Daniel Jacobowitz
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox