From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
gdb-patches@sources.redhat.com,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: Support for "break *ADDRESS thread THREADNO"
Date: Wed, 13 Apr 2005 12:09:00 -0000 [thread overview]
Message-ID: <20050413120904.GA15220@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0504131120260.14950@perivale.mips.com>
On Wed, Apr 13, 2005 at 11:35:29AM +0100, Maciej W. Rozycki wrote:
> On Tue, 12 Apr 2005, Daniel Jacobowitz wrote:
>
> > > Why was it done like this? because "*ADDRESS" is interpreted as an
> > > expression in the current language, or is there some other reason?
> >
> > I assume so. It is parsed as an expression, not just an address; for
> > instance "break *thread" would actually work if thread is a pointer to
> > a function.
>
> I think the actual problem is the expression parser cannot be told to
> stop successfully on an unparseable token as long as the expression
> collected so far is valid and let the caller deal with that. AFAICS the
> parser can only stop on a string terminator or optionally a comma,
> otherwise it issues an error.
And - can yacc do that?
Are you sure that there's no C expression that's valid with and without
a trailing identifier, by the way? I certainly find that believable,
but I haven't thought about it too hard.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-04-13 12:09 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
2005-04-12 19:22 ` Daniel Jacobowitz
2005-04-13 10:36 ` Maciej W. Rozycki
2005-04-13 12:09 ` Daniel Jacobowitz [this message]
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=20050413120904.GA15220@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=macro@linux-mips.org \
--cc=macro@mips.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