[Fwd: TARGET_WAITKIND_THREAD_[CREATION || DELETION]]

Michael Snyder msnyder@cygnus.com
Mon Aug 16 16:38:00 GMT 1999


To : gdb-local@cygnus.com
Subject : TARGET_WAITKIND_THREAD_[CREATION || DELETION]
>From : Michael Snyder <msnyder@cygnus.com>
Date : Mon, 16 Aug 1999 16:34:27 -0700
Organization : Cygnus Solutions

I want to add two new entries to the list of reasons why
target_wait may return (ie. why the target may have stopped).
	THREAD_CREATION, and
	THREAD_DELETION.

These will allow GDB to perform any housekeeping it needs
to do to manage threads.  For instance, GDB may want to 
remove a step_resume breakpoint that was in use by the 
thread that has exited.  If used, these stops will also
insure that GDB's thread list is always up to date.
Of course, their use is optional, and if a target does not
use them, GDB will work no worse than it does today.
For instance GDB can still find out about new threads
"just in time" when the user asks for "info threads".

Comments?




More information about the Gdb mailing list