From: "Maciej W. Rozycki" <macro@mips.com>
To: Daniel Jacobowitz <drow@false.org>
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 16:05:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.61.0504131411520.15023@perivale.mips.com> (raw)
In-Reply-To: <20050413120904.GA15220@nevyn.them.org>
On Wed, 13 Apr 2005, Daniel Jacobowitz wrote:
> > > 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?
No idea. With bison, according to documentation, the special "error"
token might be a way of implementing that. But I haven't done any real
lex/yacc coding for years, so I'd have to refresh my dusty memory.
> 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.
Well, with C it seems to be true -- I can't recall any expression where a
trailing identifier would be valid if not preceded by either a type cast,
which by itself is not a valid expression, or an operator that accepts a
right-side operand, which cannot be left dangling either. But I'd have to
have a look at the grammar spec to be sure I don't miss any obscure corner
case.
Maciej
next prev parent reply other threads:[~2005-04-13 16:05 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
2005-04-13 16:05 ` Maciej W. Rozycki [this message]
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=Pine.LNX.4.61.0504131411520.15023@perivale.mips.com \
--to=macro@mips.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=macro@linux-mips.org \
/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