Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Tom Tromey (Code Review)" <gerrit@gnutoolchain-gerrit.osci.io>
To: Andrew Burgess <andrew.burgess@embecosm.com>,	gdb-patches@sourceware.org
Subject: [review] gdb/mi: Add new commands -symbol-info-{functions,variables,types}
Date: Wed, 30 Oct 2019 15:02:00 -0000	[thread overview]
Message-ID: <20191030150229.D9F8F20AF6@gnutoolchain-gerrit.osci.io> (raw)
In-Reply-To: <gerrit.1571909344000.Ic2fc6a6750bbce91cdde2344791014e5ef45642d@gnutoolchain-gerrit.osci.io>

Tom Tromey has posted comments on this change.

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


Patch Set 1: Code-Review+2

(1 comment)

Thank you, this looks good to me.

https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/266/1/gdb/mi/mi-symbol-cmds.c 
File gdb/mi/mi-symbol-cmds.c:

https://gnutoolchain-gerrit.osci.io/r/c/binutils-gdb/+/266/1/gdb/mi/mi-symbol-cmds.c@117 
PS1, Line 117: 
102 | mi_symbol_info (enum search_domain kind, const char *regexp,
    | ...
111 |   /* The outer container for all the matched symbols.  */
112 |   ui_out_emit_tuple all_matching_symbols (uiout, "symbols");
113 | 
114 |   /* The order of these optional emitters is critical as they will be
115 |      deleted in reverse order, which is important as these are popped from
116 |      the uiout stack as they are destroyed.  */
117 |   gdb::optional<ui_out_emit_list> debug_func_emitter_outer;
118 |   gdb::optional<ui_out_emit_tuple> debug_func_emitter_symtab;
119 |   gdb::optional<ui_out_emit_list> debug_func_emitter_symbols;
120 |   gdb::optional<ui_out_emit_list> nondebug_func_emitter;

I wonder if there's a better way.  It's ok if not, this is just
giving me bad memories of the way the disassembly code manages
this stuff.



-- 
Gerrit-Project: binutils-gdb
Gerrit-Branch: master
Gerrit-Change-Id: Ic2fc6a6750bbce91cdde2344791014e5ef45642d
Gerrit-Change-Number: 266
Gerrit-PatchSet: 1
Gerrit-Owner: Andrew Burgess <andrew.burgess@embecosm.com>
Gerrit-Reviewer: Tom Tromey <tromey@sourceware.org>
Gerrit-Comment-Date: Wed, 30 Oct 2019 15:02:29 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Gerrit-MessageType: comment


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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gerrit.1571909344000.Ic2fc6a6750bbce91cdde2344791014e5ef45642d@gnutoolchain-gerrit.osci.io>
2019-10-30 15:02 ` Tom Tromey (Code Review) [this message]
2019-11-01  1:28 ` [review v2] " Andrew Burgess (Code Review)
2019-11-01  1:36 ` Andrew Burgess (Code Review)
2019-11-08  0:50 ` [review v3] " Andrew Burgess (Code Review)
2019-11-08 10:10   ` Eli Zaretskii
2019-11-21  5:39 ` Simon Marchi (Code Review)
2019-11-22 16:42 ` [review v4] " Andrew Burgess (Code Review)
2019-11-22 19:29   ` Eli Zaretskii
2019-11-22 17:32 ` [review v5] " Andrew Burgess (Code Review)
2019-11-26 23:26 ` [review v6] " Andrew Burgess (Code Review)
2019-11-26 23:46 ` [review v7] " Andrew Burgess (Code Review)
2019-11-27  4:08 ` Simon Marchi (Code Review)
2019-11-27  4:11 ` Simon Marchi (Code Review)
2019-11-27 13:03 ` [pushed] " 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=20191030150229.D9F8F20AF6@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