Re: RFC: Two small remote protocol extensions

Daniel Jacobowitz
2002-08-23T02:36:20Z

On Thu, Aug 22, 2002 at 10:23:15PM -0400, Andrew Cagney wrote:
> Lets get rid of the easy one (...) `Hg':
>
> ``
>
> @item @code{Hg}@var{id} --- set general thread
> @cindex @code{Hc} packet
>
> Select the general thread. Register and memory read and write
> operations apply to the most recently selected general thread.
> @var{id}, a hex encoded cardinal, is the identifier of the selected thread.
>
> After a target stop, the general thread is reset to the thread
> identifier of the stopped thread.
>
> @emph{Implementation note: The @code{Hg} packet can not be used to
> determine the most recently selected thread (using the @samp{thread
> @var{thread-id} command). This is because @value{GDBN} can cache
> per-thread data and avoid the need to re-query the target on each
> @samp{thread} command.}
>
> @c Note the word ``can'' is used, not ``does'' :-)
>
> Reply:
> @table @samp
> @item OK
> for success
> @item E00
> unspecified error
> @c ESRCH --- no such proces/thread?
> @item @samp{}
> unsupported
> @end table
>
> ''

Sure. So, we need a way for it to know the current thread that doesn't
have that niggling little comment :)

--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer