From: "Simon Marchi (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Andrew Burgess <andrew.burgess@embecosm.com>, gdb-patches@sourceware.org
Subject: [review] gdb: Convert frame_show_address to return a bool
Date: Fri, 08 Nov 2019 16:38:00 -0000 [thread overview]
Message-ID: <20191108163847.51E6625B28@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1573230144000.Iaaa9ebd4ff6534db19c5329f1c604932c747bd7f@gnutoolchain-gerrit.osci.io>
Simon Marchi has posted comments on this change.
Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/541
......................................................................
Patch Set 1:
(1 comment)
Thanks Andrew for letting me use you as a guinea pig for this change :).
> --- gdb/stack.c
> +++ gdb/stack.c
> @@ -247,18 +247,18 @@ static int last_displayed_sal_valid = 0;
> static struct program_space *last_displayed_pspace = 0;
> static CORE_ADDR last_displayed_addr = 0;
> static struct symtab *last_displayed_symtab = 0;
> static int last_displayed_line = 0;
> \f
>
> /* See stack.h. */
>
> -int
> +bool
PS1, Line 255:
I think this is a really good change (take 5).
> frame_show_address (struct frame_info *frame,
> struct symtab_and_line sal)
> {
> /* If there is a line number, but no PC, then there is no location
> information associated with this sal. The only way that should
> happen is for the call sites of inlined functions (SAL comes from
> find_frame_sal). Otherwise, we would have some PC range if the
> SAL came from a line table. */
> if (sal.line != 0 && sal.pc == 0 && sal.end == 0)
--
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: Iaaa9ebd4ff6534db19c5329f1c604932c747bd7f
Gerrit-Change-Number: 541
Gerrit-PatchSet: 1
Gerrit-Owner: Andrew Burgess <andrew.burgess@embecosm.com>
Gerrit-Reviewer: Simon Marchi <simon.marchi@polymtl.ca>
Gerrit-Comment-Date: Fri, 08 Nov 2019 16:38:46 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
next prev parent reply other threads:[~2019-11-08 16:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 16:22 Andrew Burgess (Code Review)
2019-11-08 16:27 ` Simon Marchi (Code Review)
2019-11-08 16:28 ` Simon Marchi (Code Review)
2019-11-08 16:33 ` Simon Marchi (Code Review)
2019-11-08 16:38 ` Simon Marchi (Code Review) [this message]
2019-11-10 21:02 ` [pushed] " Sourceware to Gerrit sync (Code Review)
2019-11-10 21:02 ` Sourceware to Gerrit sync (Code Review)
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=20191108163847.51E6625B28@gnutoolchain-gerrit.osci.io \
--to=gerrit@gnutoolchain-gerrit.osci.io \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=gnutoolchain-gerrit@osci.io \
/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