From: Michael Eager <eager@eagerm.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Keith Seitz <keiths@redhat.com>,
"gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Revised display-linkage-name
Date: Fri, 02 Aug 2013 18:00:00 -0000 [thread overview]
Message-ID: <51FBF3B9.9020008@eagerm.com> (raw)
In-Reply-To: <874nb9f7vr.fsf@fleche.redhat.com>
On 08/01/13 13:55, Tom Tromey wrote:
>>>>>> "Michael" == Michael Eager <eager@eagerm.com> writes:
>
> Michael> I eliminated the annotations and made the other requested changes.
>
> Michael> + if (strlen (SYMBOL_LINKAGE_NAME (msymbol.minsym))
> Michael> + > display_linkage_name_length)
> Michael> + {
>
> I think this should also check ui_out_is_mi_like_p.
>
> Michael> + /* Print linkage name after source name if requested and different. */
> Michael> + if ((display_linkage_name || ui_out_is_mi_like_p (uiout))
> Michael> + && linkname != NULL && strcmp (funname, linkname) != 0)
> Michael> + {
> Michael> + ui_out_text (uiout, " [");
> Michael> +
> Michael> + if (strlen (linkname) > display_linkage_name_length)
> Michael> + {
>
> Here too.
>
> Michael> + char *lname = alloca (display_linkage_name_length + 4);
> Michael> +
> Michael> + strncpy (lname, linkname, display_linkage_name_length);
> Michael> + lname[display_linkage_name_length] = '\0';
> Michael> + strcat (lname, "...");
> Michael> + ui_out_text (uiout, lname);
>
> Here you emit it as text...
>
> Michael> + }
> Michael> + else
> Michael> + ui_out_field_string (uiout, "linkage name", linkname);
>
> ... here with a field name with spaces...
>
> Michael> +
> Michael> + ui_out_text (uiout, "]");
> Michael> + ui_out_field_stream (uiout, "linkage_name", stb);
>
> ... and here with an underscore. Another part of the patch used
> "linkage-name", with a hyphen. I think the hyphen one should be
> preferred.
>
> Also, this last bit looks the same as an earlier revision to me.
> "stb" simply isn't valid here -- your code isn't printing to it, it was
> set up earlier; I'm surprised it is even still live.
Thanks. I'll rework the MI stuff. I have no experience/understanding
of how this is supposed to work.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
prev parent reply other threads:[~2013-08-02 18:00 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
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 [this message]
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=51FBF3B9.9020008@eagerm.com \
--to=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