From: Simon Marchi <simark@simark.ca>
To: Scott Linder <scott@scottlinder.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] [gdb] Support frames inlined into the outer frame
Date: Thu, 4 Jun 2020 12:11:43 -0400 [thread overview]
Message-ID: <9e2832f3-c3c4-76da-9c40-85b8055bdee5@simark.ca> (raw)
In-Reply-To: <20200331191856.31222-1-scott@scottlinder.com>
On 2020-03-31 3:18 p.m., Scott Linder wrote:
> @@ -763,6 +760,24 @@ frame_id_eq (struct frame_id l, struct frame_id r)
> return eq;
> }
>
> +int
> +outer_frame_id_p (struct frame_id l)
> +{
> + int p;
> +
> + /* The artificial_depth can vary so we ignore it when checking if this is
> + an outer_frame_id. */
> + l.artificial_depth = 0;
> + p = memcmp (&l, &outer_frame_id, sizeof (outer_frame_id));
This should be `memcmp (...) == 0`. Currently, the function returns true when
the frame is not an outer frame id, which is the opposite of what it is supposed
to do.
With this, the test gdb.base/break.exp on AArch64 runs fine. I will launch a full
test run to see if there are any other problems.
You can make the new function return "bool" instead of "int", and use true/false instead
of zero/non-zero (both in the code and comments).
Simon
next prev parent reply other threads:[~2020-06-04 16:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 20:43 [RFC][PATCH] " scott
2020-03-18 21:17 ` scott
2020-03-18 21:27 ` Simon Marchi
2020-03-18 21:42 ` scott
2020-03-18 21:45 ` Simon Marchi
2020-03-18 22:06 ` Scott Linder
2020-03-18 22:11 ` [PATCH] [gdb] " Scott Linder
2020-03-24 10:22 ` Andrew Burgess
2020-03-30 22:22 ` scott
2020-03-31 19:18 ` [PATCH v2] " Scott Linder
2020-04-03 17:00 ` Andrew Burgess
2020-04-17 20:41 ` Scott Linder
2020-04-03 19:37 ` Luis Machado
2020-04-17 20:51 ` Scott Linder
2020-06-04 16:11 ` Simon Marchi [this message]
2020-06-04 19:23 ` Simon Marchi
2020-06-08 12:00 ` Luis Machado
2020-06-08 16:01 ` Simon Marchi
2020-06-08 16:10 ` Luis Machado
2020-04-02 19:30 ` [PATCH] " Pedro Alves
2020-04-17 20:35 ` Scott Linder
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=9e2832f3-c3c4-76da-9c40-85b8055bdee5@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=scott@scottlinder.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