From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: RFC: Two small remote protocol extensions
Date: Thu, 26 Sep 2002 18:39:00 -0000 [thread overview]
Message-ID: <3D93B6E6.8030805@redhat.com> (raw)
In-Reply-To: <20020828133445.GA16642@nevyn.them.org>
> OK, I suppose that makes sense. It's pretty much where I was to begin
> with: if Hc is non-zero, lock to that thread; if Hc is 0, resume all
> threads, but where do we step? How would you like to see us specify
> this - I used Hs, a new step packet taking a thread argument might work
> too... etc.
Yes, to come full circle, I can see two choices:
- (me back down) and Hg be made as per your proposal - as well as the
registers, it also specify the thread to step when there isn't thread
locking.
- we define something properly
- we modify GDB so that, when asked to step a thread other than current
(i.e., selected) GDB first forces the target to switch to that thread,
and then steps it. This means doing a software single step even though
the hardware might think it has hardware single step.
Separate to this GDB needs to be changed to that resume() has all the
information it needs to implement all of the above operations (and it
isn't relying on that implied global state :-( ).
>
> There's also the question of whether any other simulators or targets
> handle this, and how they behave; I'm not familiar with them. Do they
> treat "HcTID, s" as single-step-one-thread-only? I guess they probably
> do.
I really don't know. (For ``s'', should you be stepping all threads?)
Anyway, I think, to do this right, we're left needing a new packet. Try:
>> > step one, stop others
>
>>
>> Hardware single-step off of breakpoint.
>> TPID, STEP, !OTH
>> HcTID, s
HtTID;s
>> > step one, continue others
>
>>
>> Hardware single-step.
>> TPID, STEP, OTH
>> H???, s
HtPID,0;s
or even:
Ht0;s
I.e., step all threads. Let GDB sort out the mess.
>> > continue one, stop others
>
>>
>> Schedule lock.
>> Software single-step off breakpoint.
>> TPID, !STEP, !OTH (wiered)
>> HcTID, c
HtTID;c
>> > continue one, continue others
>
>>
>> Software single-step.
>> General resume.
>> TPID, !STEP, OTH
>> Hc0, c
Ht0;c
or
c
And also:
HtTID;g
HtTID,TID,TID;Z...
HtTID,TID,TID;c
etc.
Andrew
next prev parent reply other threads:[~2002-09-27 1:39 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 19:25 Daniel Jacobowitz
2002-05-02 8:38 ` Andrew Cagney
2002-05-02 8:52 ` Daniel Jacobowitz
2002-05-02 9:39 ` Andrew Cagney
2002-05-02 12:14 ` Daniel Jacobowitz
2002-05-02 12:22 ` Kevin Buettner
2002-05-02 12:34 ` Daniel Jacobowitz
2002-05-02 13:13 ` Andrew Cagney
2002-05-02 14:09 ` Daniel Jacobowitz
2002-05-03 11:24 ` Andrew Cagney
2002-05-03 14:28 ` Daniel Jacobowitz
2002-05-03 15:18 ` Andrew Cagney
2002-05-03 15:22 ` Daniel Jacobowitz
2002-05-04 19:59 ` Andrew Cagney
2002-05-02 13:13 ` Quality Quorum
2002-05-02 14:13 ` Daniel Jacobowitz
2002-05-03 13:07 ` Andrew Cagney
2002-08-16 7:30 ` Daniel Jacobowitz
2002-08-16 7:42 ` Andrew Cagney
2002-08-16 7:52 ` Daniel Jacobowitz
2002-08-16 8:21 ` Andrew Cagney
2002-08-22 19:23 ` Andrew Cagney
2002-08-22 19:36 ` Daniel Jacobowitz
2002-08-23 7:24 ` Quality Quorum
2002-08-23 7:26 ` Daniel Jacobowitz
2002-08-23 7:49 ` Quality Quorum
2002-08-23 8:57 ` Andrew Cagney
2002-08-23 11:16 ` Quality Quorum
2002-08-23 12:39 ` Andrew Cagney
2002-08-23 13:10 ` Quality Quorum
2002-08-27 20:23 ` Andrew Cagney
2002-08-28 8:31 ` Quality Quorum
2002-08-28 9:44 ` Andrew Cagney
2002-08-28 9:49 ` Daniel Jacobowitz
2002-08-22 21:08 ` Andrew Cagney
2002-08-23 5:44 ` Daniel Jacobowitz
2002-08-23 12:10 ` Andrew Cagney
2002-08-23 12:53 ` Andrew Cagney
2002-08-23 13:15 ` Daniel Jacobowitz
2002-08-27 21:07 ` Andrew Cagney
2002-08-28 6:33 ` Daniel Jacobowitz
2002-09-25 8:51 ` Daniel Jacobowitz
2002-09-25 11:17 ` Andrew Cagney
2002-09-26 18:39 ` Andrew Cagney [this message]
2002-09-26 18:48 ` Andrew Cagney
2003-06-29 7:51 ` Daniel Jacobowitz
2003-09-03 23:41 ` Andrew Cagney
2003-09-17 15:51 ` Daniel Jacobowitz
2003-09-17 16:19 ` Andrew Cagney
2003-09-17 16:23 ` Daniel Jacobowitz
2003-09-22 0:27 ` Andrew Cagney
2003-09-22 1:01 ` Daniel Jacobowitz
2003-09-22 3:02 ` Andrew Cagney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D93B6E6.8030805@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox