This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/524: Exact meaning of Hg packet?
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 3 May 2002 19:54:40 -0000
- Subject: gdb/524: Exact meaning of Hg packet?
- Reply-to: ac131313 at redhat dot com
>Number: 524
>Category: gdb
>Synopsis: Exact meaning of Hg packet?
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Fri May 03 12:58:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: ac131313@redhat.com
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
> 4. exact meaning of Hg - last time I checked it was related to registers
It is similar to current frame VS selected frame.
When the target stops, there is single identifyable ``current thread'' that is considered responsible for the stop.
The user can then select another thread for examination. This changes the ``selected thread'' but does not affect the ``current thread''. A Hg packet is sent to the target to notify it that a new thread has been selected and that this new thread's registers should be operated on by the [Gg] and [pP] register packets.
Changing ``selected thread'' does not affect things like the scheduler.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: