From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Matt Rice <ratmice@gmail.com>, Tom Tromey <tromey@redhat.com>,
Stan Shebs <stanshebs@earthlink.net>
Subject: Re: Toward multicore GDB - Set theory
Date: Tue, 08 Nov 2011 14:50:00 -0000 [thread overview]
Message-ID: <201111081450.30461.pedro@codesourcery.com> (raw)
In-Reply-To: <CACTLOFp0qgnmcMPW4+nkbxM5nFJcWPMmezUVNFVLE0ryBYk8zQ@mail.gmail.com>
On Tuesday 08 November 2011 05:17:28, Matt Rice wrote:
> On Thu, Nov 3, 2011 at 2:01 PM, Tom Tromey <tromey@redhat.com> wrote:
>
> > (gdb) break [0-13] function # "semi-prefix"
>
> I personally prefer to avoid this one because the square brackets it
> would seem difficult to
> disambiguate between thread sets and objective-c methods, at least
> when naming threads is added.
>
Yeah, that was one of the reasons the current WIP prototype does:
[TRIGGER-SET] break -stop [STOP-SET] (--) LINESPEC
That is [TRIGGER-SET] is a prefix, because it really is
the same meaning as applying the prefix in other commands.
That is, "the command applies to this set". For breakpoints,
it naturally means "the breakpoint applies/triggers to/on
this set". For "continue" it'd mean "continue this set",
for print, it'd mean "print this expression in the context
of this set", etc., etc..
The "-stop" option is required when specifying a
stop set (compared to not requiring "-stop" and just
accepting the [] part, and LINESPEC is last. This gets rid
of LINESPEC ambiguity with obj-c at least, and leaves a saner
path open for other future options too. I've left the
`--' option separator too for the same reason (like in your
info macro & friends changes).
--
Pedro Alves
next prev parent reply other threads:[~2011-11-08 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 0:04 Stan Shebs
2011-11-03 21:01 ` Tom Tromey
2011-11-04 13:20 ` Pedro Alves
2011-11-07 17:38 ` Joel Brobecker
2011-11-08 1:14 ` Daniel Jacobowitz
2011-11-08 5:17 ` Matt Rice
2011-11-08 14:50 ` Pedro Alves [this message]
2011-11-08 15:04 ` Tom Tromey
2011-11-08 15:45 ` Pedro Alves
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=201111081450.30461.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=ratmice@gmail.com \
--cc=stanshebs@earthlink.net \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).