From: Andrew Cagney <ac131313@redhat.com>
To: "J. Johnston" <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: frame id enhancement
Date: Wed, 15 Oct 2003 21:09:00 -0000 [thread overview]
Message-ID: <3F8DB78A.4090409@redhat.com> (raw)
In-Reply-To: <3F81DB50.6020202@redhat.com>
> @@ -288,6 +297,9 @@
> eq = 0;
> else if (l.stack_addr != r.stack_addr)
> /* If .stack addresses are different, the frames are different. */
> + eq = 0;
> + else if (l.special_addr != r.special_addr)
> + /* If .special addresses are different, the frames are different. */
> eq = 0;
> else if (l.code_addr == 0 || r.code_addr == 0)
> /* A zero code addr is a wild card, always succeed. */
Looking at the full code:
> int
> frame_id_eq (struct frame_id l, struct frame_id r)
> {
> int eq;
> if (l.stack_addr == 0 || r.stack_addr == 0)
> /* Like a NaN, if either ID is invalid, the result is false. */
> eq = 0;
> else if (l.stack_addr != r.stack_addr)
> /* If .stack addresses are different, the frames are different. */
> eq = 0;
> else if (l.code_addr == 0 || r.code_addr == 0)
> /* A zero code addr is a wild card, always succeed. */
> eq = 1;
> else if (l.code_addr == r.code_addr)
> /* The .stack and .code are identical, the ID's are identical. */
> eq = 1;
> else
> /* No luck. */
> eq = 0;
> if (frame_debug)
> {
> fprintf_unfiltered (gdb_stdlog, "{ frame_id_eq (l=");
> fprint_frame_id (gdb_stdlog, l);
> fprintf_unfiltered (gdb_stdlog, ",r=");
> fprint_frame_id (gdb_stdlog, r);
> fprintf_unfiltered (gdb_stdlog, ") -> %d }\n", eq);
> }
> return eq;
> }
Is there a need to allow wild card SPECIAL_ADDRs here? The user can
specify:
(gdb) frame <frame-id-stack-addr>
and on some architectures:
(gdb) frame <frame-id.stack-addr> <frame-id.code-addr>
and have GDB jump to that frame. It relies on the wild-card mechanism
to give approx matches (otherwize the user will have to fully specify
<stack-addr>, <code-addr> and <special-addr>).
Looking at:
> int
> frame_id_inner (struct frame_id l, struct frame_id r)
> {
> int inner;
> if (l.stack_addr == 0 || r.stack_addr == 0)
> /* Like NaN, any operation involving an invalid ID always fails. */
> inner = 0;
> else
> /* Only return non-zero when strictly inner than. Note that, per
> comment in "frame.h", there is some fuzz here. Frameless
> functions are not strictly inner than (same .stack but
> different .code). */
> inner = INNER_THAN (l.stack_addr, r.stack_addr);
> if (frame_debug)
> {
> fprintf_unfiltered (gdb_stdlog, "{ frame_id_inner (l=");
> fprint_frame_id (gdb_stdlog, l);
> fprintf_unfiltered (gdb_stdlog, ",r=");
> fprint_frame_id (gdb_stdlog, r);
> fprintf_unfiltered (gdb_stdlog, ") -> %d }\n", inner);
> }
> return inner;
> }
does SPECIAL_ADDR add further ordering? If it doesn't then the comment
needs to be updated (and the description in "frame.h" clarified).
Andrew
next prev parent reply other threads:[~2003-10-15 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 21:15 J. Johnston
2003-10-14 21:59 ` J. Johnston
2003-10-15 21:09 ` Andrew Cagney [this message]
2003-10-15 23:12 ` J. Johnston
2003-10-16 16:09 ` Andrew Cagney
2003-10-16 19:06 ` J. Johnston
2003-10-16 21:06 ` Andrew Cagney
2003-10-16 21:49 ` J. Johnston
2003-10-16 23:32 ` J. Johnston
2003-10-17 13:30 ` Andrew Cagney
2003-10-17 16:32 ` J. Johnston
2003-10-17 18:11 ` Kevin Buettner
2003-10-17 19:34 ` J. Johnston
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=3F8DB78A.4090409@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@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