From: Eli Zaretskii <eliz@gnu.org>
To: Michael Eager <eager@eagerm.com>
Cc: keiths@redhat.com, gdb-patches@sourceware.org, tromey@redhat.com
Subject: Re: [PATCH] Revised display-linkage-name
Date: Wed, 17 Jul 2013 19:14:00 -0000 [thread overview]
Message-ID: <83oba10zj3.fsf@gnu.org> (raw)
In-Reply-To: <51E6E797.30709@eagerm.com>
> Date: Wed, 17 Jul 2013 11:51:03 -0700
> From: Michael Eager <eager@eagerm.com>
> CC: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>,
> Tom Tromey <tromey@redhat.com>
>
> I believe I have addressed your comments, as well as Eli's previous
> notes about the docs. I didn't merge the tests cases into a single proc.
>
> BTW, "prepend" appears in several places in the docs. I replaced it this
> patch with prefix. If there is a concern that "prepend" sounds like jargon,
> then the other uses should be changed as well.
>
>
>
> gdb/
> 2013-07-17 Michael Eager <eager@eagercon.com>
>
> * NEWS: Announcement.
> * ada-lang.c: Update calls to find_frame_funname (pass NULL for linkname).
> * disasm.c: Likewise.
> * python/py-frame.c: Likewise.
> * annotate.c (annotate_linkage_name): New.
> * annotate.h (annotate_linkage_name): New decl.
> * 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.
> * annotate.c (annotate_linkage_name): New.
> * annotate.h (annotate_linkage_name): Declare.
> * 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-07-17 Michael Eager <eager@eagercon.com>
>
> * gdb.texinfo: Add description.
>
> gdb/testsuite
> 2013-07-17 Michael Eager <eager@eagercon.com>
>
> * gdb.cp/display-linkage-name.exp: New.
> * gdb.cp/display-linkage-name.cc: New.
>
Thanks, the documentation parts are OK.
next prev parent reply other threads:[~2013-07-17 19:14 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
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 [this message]
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=83oba10zj3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eager@eagerm.com \
--cc=gdb-patches@sourceware.org \
--cc=keiths@redhat.com \
--cc=tromey@redhat.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