Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Tom Tromey (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Luis Machado <luis.machado@linaro.org>, gdb-patches@sourceware.org
Cc: Andrew Burgess <andrew.burgess@embecosm.com>
Subject: [review v2] [ARM, Thumb] Fix disassembling bug after reloading a symbol file
Date: Wed, 30 Oct 2019 15:15:00 -0000	[thread overview]
Message-ID: <20191030151516.4245320AF6@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1572442722000.I22c3e6ebe9bfedad66d56fe9656994fa1761c485@gnutoolchain-gerrit.osci.io>

Tom Tromey has posted comments on this change.

Change URL: https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/447
......................................................................


Patch Set 2:

(2 comments)

Thank you for the patch.  I had one question that I think should
be answered before landing; plus one nit.

https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/447/2//COMMIT_MSG 
Commit Message:

https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/447/2//COMMIT_MSG@62 
PS2, Line 62: 
53 | 	(arm_bfd_data_key): ... this.
54 | 	(arm_find_mapping_symbol): Adjust access to new bfd_key-based
55 | 	data.
56 | 	(arm_record_special_symbol): Likewise.
57 | 
58 | gdb/testsuite/ChangeLog:
59 | 
60 | 2019-01-29  Luis Machado  <luis.machado@linaro.org>
61 | 
62 | 	* gdb.arch/pr25124.S: New file.

If there's a PR open for this, then each ChangeLog should
mention it, like "PR arch/25124".  This syntax lets the
commit script log the commit in bugzilla.


https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/447/2/gdb/arm-tdep.c 
File gdb/arm-tdep.c:

https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/447/2/gdb/arm-tdep.c@117 
PS2, Line 117: 
108 |      symbol value (address).  */
109 |   std::unique_ptr<arm_mapping_symbol_vec[]> section_maps;
110 | 
111 |   /* For each corresponding element of section_maps above, is this vector
112 |      sorted.  */
113 |   std::unique_ptr<bool[]> section_maps_sorted;
114 | };
115 | 
116 | /* Per-bfd data used for mapping symbols.  */
117 | static bfd_key<arm_per_bfd> arm_bfd_data_key;

I wonder if `arm_exidx_data_key` needs this treatment as well?



-- 
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: I22c3e6ebe9bfedad66d56fe9656994fa1761c485
Gerrit-Change-Number: 447
Gerrit-PatchSet: 2
Gerrit-Owner: Luis Machado <luis.machado@linaro.org>
Gerrit-Reviewer: Luis Machado <luis.machado@linaro.org>
Gerrit-CC: Andrew Burgess <andrew.burgess@embecosm.com>
Gerrit-CC: Tom Tromey <tromey@sourceware.org>
Gerrit-Comment-Date: Wed, 30 Oct 2019 15:15:16 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment


  parent reply	other threads:[~2019-10-30 15:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-30 13:38 [review] " Luis Machado (Code Review)
2019-10-30 14:01 ` Andrew Burgess (Code Review)
2019-10-30 14:11 ` Luis Machado (Code Review)
2019-10-30 14:22 ` [review v2] " Luis Machado (Code Review)
2019-10-30 15:15 ` Tom Tromey (Code Review) [this message]
2019-10-30 15:22 ` Luis Machado (Code Review)
2019-10-30 15:59 ` [review v3] " Luis Machado (Code Review)
2019-10-31 16:44 ` [review v5] " Luis Machado (Code Review)
2019-10-31 16:45 ` Luis Machado (Code Review)
2019-11-01  1:09 ` Andrew Burgess (Code Review)
2019-11-01 13:14 ` [pushed] [ARM, thumb] " Sourceware to Gerrit sync (Code Review)
2019-11-01 13:14 ` 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=20191030151516.4245320AF6@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 \
    --cc=luis.machado@linaro.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