Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Eager <eager@eagerm.com>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH] Revised display-linkage-name
Date: Wed, 10 Jul 2013 16:17:00 -0000	[thread overview]
Message-ID: <51DD891D.7090009@eagerm.com> (raw)
In-Reply-To: <51BF47DB.6070709@eagerm.com>

Ping!

Can someone review and approve this patch?

On 06/17/13 10:31, Michael Eager wrote:
> Ping!
>
> On 05/22/2013 11:03 AM, Michael Eager wrote:
>> Attached is a revised patch to display the linkage name (the linker symbol)
>> along with the function name when setting, listing, or hitting a breakpoint.
>> This is a revision of http://sourceware.org/ml/gdb-patches/2013-03/msg00806.html.
>> (BTW, the gdb-patches mailing list archive doesn't show the original email from
>> 3/18/13, quoted in the referenced message.)
>>
>> Changes:
>>    Add NEWS and docs.
>>    Add linkage name to "info break" listing.
>>    Add MI annotations.
>>    Add command to set/show display length limit, remove define.
>>    Add test case.
>>
>> There is a minor inconsistency where the linkage name is displayed.
>> When setting/hitting a breakpoint, the linkage name is displayed
>> within brackets following the source name, before the arguments.  In
>> the "info breakpoint" command, the linkage name is displayed in brackets
>> after the arguments.  This is because SYMBOL_PRINT_NAME(sym) returns a
>> complete function signature, not just the function name.
>>
>> The test case was added to gdb.cp for convenience, since it uses
>> the C++ compiler.  The patch is not dependent on C++.
>>
>> Tom -- can you verify that the MI support is correct?   I don't have
>> any way to test this.
>>
>>
>> gdb/
>> 2013-05-23  Michael Eager <eager@eagercon.com>
>>
>>        * NEWS: Announcement.
>>        * ada-lang.c: Update calls to find_frame_funname.
>>        * disasm.c: Likewise.
>>        * python/py-frame.c: Likewise.
>>        * annotate.c (annotate_linkage_name): New.
>>        * annotate.h (annotate_linkage_name): Declare.
>>        * breakpoint.c (print_breakpoint_location): Print linkage name.
>>        * defs.h (build_address_symbolic): Add linkname arg.
>>        * printcmd.c (print_address_symbolic): Print linkage name.
>>        (build_address_symbolic): Return linkage name.
>>        * stack.c (find_frame_funname): Return linkage name.
>>        (print_frame): Print linkage name.
>>        * stack.h (find_frame_funname): Update declaration.
>>        * top.c (display_linkage_name, display_linkage_name_len): New.
>>        (show_display_linkage_name, show_display_linkage_name_len): New cmds.
>>        * top.h (display_linkage_name, display_linkage_name_len): Declare.
>>
>> gdb/doc
>> 2013-05-23  Michael Eager <eager@eagercon.com>
>>
>>        * gdb.texinfo: Add description.
>>
>> gdb/testsuite
>> 2013-05-23  Michael Eager <eager@eagercon.com>
>>
>>        * gdb.cp/display-linkage-name.exp: New.
>>        * gdb.cp/display-linkage-name.cc: New.
>>
>
>


-- 
Michael Eager	 eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306  650-325-8077


  reply	other threads:[~2013-07-10 16:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 18:28 Michael Eager
2013-05-22 19:28 ` Eli Zaretskii
2013-05-22 21:42   ` Michael Eager
2013-06-17 17:35 ` Michael Eager
2013-07-10 16:17   ` Michael Eager [this message]
2013-07-11 23:28     ` Keith Seitz
2013-07-12 21:17       ` Michael Eager
2013-07-17 18:51         ` Michael Eager
2013-07-17 19:14           ` Eli Zaretskii
2013-07-22 17:48           ` Keith Seitz
2013-07-22 20:07             ` Michael Eager
2013-07-22 21:55               ` Keith Seitz
2013-07-24 15:55                 ` Michael Eager
2013-07-26 18:42                   ` Tom Tromey
2013-07-26 20:18                     ` Michael Eager
2013-07-29 17:48                       ` Tom Tromey
2013-08-01 19:36                         ` Michael Eager
2013-08-01 20:56                           ` Tom Tromey
2013-08-02 18:00                             ` Michael Eager

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=51DD891D.7090009@eagerm.com \
    --to=eager@eagerm.com \
    --cc=gdb-patches@sourceware.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