Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Stan Shebs <shebs@apple.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
	"Maciej W. Rozycki" <macro@mips.com>,
	gdb-patches@sources.redhat.com
Subject: Re: Support for "break *ADDRESS thread THREADNO"
Date: Tue, 12 Apr 2005 19:21:00 -0000	[thread overview]
Message-ID: <20050412192141.GA11186@nevyn.them.org> (raw)
In-Reply-To: <425C1ECE.9060907@apple.com>

On Tue, Apr 12, 2005 at 12:17:34PM -0700, Stan Shebs wrote:
> Eli Zaretskii wrote:
> 
> >
> >Or maybe a command option "break --thread=ID *ADDR".  (Or did we
> >decide to not use such syntax?)
> >
> "--" is still valid expression syntax, though unlikely in
> that context.
> 
> Looking at the keyboard, I don't see much that is not already
> part of language or GDB syntax. How about '/', which has no
> unary usage, and is already used for command modifiers?

Fortunately, break does not take an expression; in 'break *FOO' FOO can
be an expression, but the * is not part of it.

(The question of using -- options is a different one.  Response was
pretty negative the last time we discussed this, IIRC.  But I like it.)

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-04-12 19:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 15:54 Maciej W. Rozycki
2005-04-12 18:13 ` Daniel Jacobowitz
2005-04-12 18:24   ` Maciej W. Rozycki
2005-04-12 18:51   ` Eli Zaretskii
2005-04-12 18:55     ` Daniel Jacobowitz
2005-04-12 19:05       ` Eli Zaretskii
2005-04-12 19:17         ` Stan Shebs
2005-04-12 19:21           ` Daniel Jacobowitz [this message]
2005-04-12 19:22         ` Daniel Jacobowitz
2005-04-13 10:36       ` Maciej W. Rozycki
2005-04-13 12:09         ` Daniel Jacobowitz
2005-04-13 16:05           ` Maciej W. Rozycki
2005-04-13 17:37         ` Eli Zaretskii
2005-04-13 17:41           ` Daniel Jacobowitz

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=20050412192141.GA11186@nevyn.them.org \
    --to=drow@false.org \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=macro@mips.com \
    --cc=shebs@apple.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