From: Fernando Nasser <fnasser@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: David Taylor <taylor@cygnus.com>, gdb-patches@sourceware.cygnus.com
Subject: Re: [RFA] parse_frame_specification (stack.c)
Date: Mon, 05 Mar 2001 12:57:00 -0000 [thread overview]
Message-ID: <3AA3FCEC.AABDDE25@redhat.com> (raw)
In-Reply-To: <3AA3F900.39AF9860@cygnus.com>
Andrew Cagney wrote:
>
> Fernando Nasser wrote:
> >
> > David,
> >
> > The real problem here is that there is an ambiguity in this command
> > argument specification. If a frame is specified as an address, it
> > should be proceeded by a "*" as we do in the break command.
> >
> > It seems that problems like this have been encountered before. here is
> > the comment in the code that refers to s similar situation:
>
> See:
>
> http://sources.redhat.com/gdb/onlinedocs/gdb_7.html#SEC43
>
> I believe David is preserving documented behavour.
>
You got that right. I mentioned that we could fix the syntax (manual
included) so it is not any longer ambiguous.
Instead of inventing a syntax, I suggested that we do as we already do
with breakpoints. Numbers are breakpoints *NNNNNNNN are addresses. I
don't particularly like the breakpoints syntax. I wish people had used
"#N" to indicate a breakpoint number or a stack level. That would also
make things unambiguous.
But, anyway, frames at very low addresses are not very likely so I guess
we should just leave things as they are.
--
Fernando Nasser
Red Hat Canada Ltd. E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
next prev parent reply other threads:[~2001-03-05 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 9:07 David Taylor
2001-03-05 9:30 ` Fernando Nasser
2001-03-05 12:39 ` Andrew Cagney
2001-03-05 12:57 ` Fernando Nasser [this message]
2001-03-06 2:12 ` Eli Zaretskii
2001-03-06 2:11 ` Eli Zaretskii
2001-03-06 9:37 ` Fernando Nasser
2001-03-05 12:42 ` Andrew Cagney
2001-03-05 10:31 David Taylor
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=3AA3FCEC.AABDDE25@redhat.com \
--to=fnasser@redhat.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=taylor@cygnus.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