From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Doug Evans <dje@google.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>,
pfee@talk21.com
Subject: Re: [RFC] stept, nextt, finisht, untilt, continuet
Date: Tue, 30 Aug 2011 17:13:00 -0000 [thread overview]
Message-ID: <m37h5uddr2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201108301621.55098.pedro@codesourcery.com> (Pedro Alves's message of "Tue, 30 Aug 2011 16:21:54 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> I'm currently working towards adding (run control) ptset/itset
Pedro> support to gdb. Working on instructure still (I can run all-stop on
Pedro> top of a target running in non-stop mode now), and the final syntax
Pedro> will obviously need discussion, but I think we could come up with
Pedro> syntax for this within that framework.
I think it would be good to flesh out the syntax details now.
Maybe you could post your proposal; or even just a link to the earlier
proposal if you plan to follow it.
It would be helpful to the ambiguous linespec work if the basic ptset
code (stuff relating to the data structure itself, not wiring it into
inferior control) were available "early" -- I'm away for a bit, and I
don't know your schedule, so it all may be fine; but I mean sometime in
October.
Tom
next prev parent reply other threads:[~2011-08-30 17:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 1:49 Doug Evans
2011-08-30 9:16 ` Jan Kratochvil
2011-08-30 10:01 ` pfee
2011-08-30 11:56 ` Jan Kratochvil
2011-08-30 12:42 ` pfee
2011-08-30 14:21 ` Jan Kratochvil
2011-08-30 15:09 ` Doug Evans
2011-08-30 15:22 ` Pedro Alves
2011-08-30 17:13 ` Tom Tromey [this message]
2011-08-30 17:29 ` Pedro Alves
2011-09-02 16:48 ` Doug Evans
2011-08-30 17:00 ` Tom Tromey
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=m37h5uddr2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pedro@codesourcery.com \
--cc=pfee@talk21.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