From: "Doug Evans" <dje@google.com>
To: "Joel Brobecker" <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] mixed source+assembly from cli disassemble
Date: Wed, 16 Apr 2008 21:22:00 -0000 [thread overview]
Message-ID: <e394668d0804161231t61f3507fj11ade43e8a4faa69@mail.gmail.com> (raw)
In-Reply-To: <20080416185535.GB3626@adacore.com>
On Wed, Apr 16, 2008 at 11:55 AM, Joel Brobecker <brobecker@adacore.com> wrote:
> Doug,
>
>
> > 2008-04-03 Doug Evans <dje@google.com>
> >
> > * cli/cli-cmds.c (print_disassembly): New fn.
> > (disassemble_current_function): New fn.
> > (disassemble_command): Recognize /s modifier, print mixed
> > source+assembly.
> > (init_cli_cmds): Update disassemble help text.
>
> MichaelS already approved the patch, and I agree with him. I had some
> comments, and a request so I'm sending them now.
>
> First, the request: Can you also write up a NEWS entry? I think this
> is a great addition and it deserves a mention in NEWS.
Ok.
>
> The ChangeLog is missing the entry for the documentation update. Please
> make sure that EliZ has seen it before checking in. I'm not sure
> whether this is the case or not anymore.
Sorry, creature of habit. Way back when such changelog entries were
never done (per gnu coding standards).
> I also personally prefer to avoid abbreviations such as "fn", although
> the GNU coding standards say nothing against them - so it may only be
> a personally preference. I see that it has been use a few times in
> the past, but most uses is in the 90s. Don't change it unless other
> maintainers agree that it should be changed.
>
>
> > + printf_filtered ("from ");
> > + deprecated_print_address_numeric (low, 1, gdb_stdout);
> > + printf_filtered (" to ");
> > + deprecated_print_address_numeric (high, 1, gdb_stdout);
> > + printf_filtered (":\n");
>
> While you are modifying this code, I think the following should work too:
>
> printf_filtered ("form %s to %s:\n", paddress (low), paddress (high));
>
> Not only does this help us get rid of a couple of uses of deprecated
> functions, I believe it's also better for i18n.
Righto.
next prev parent reply other threads:[~2008-04-16 19:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 3:26 Doug Evans
2008-04-04 9:17 ` Michael Snyder
2008-04-04 9:26 ` Doug Evans
2008-04-04 9:58 ` Eli Zaretskii
2008-04-09 22:27 ` Michael Snyder
2008-04-10 12:35 ` Joel Brobecker
2008-04-11 8:55 ` Michael Snyder
2008-04-15 20:32 ` Michael Snyder
2008-04-16 21:16 ` Joel Brobecker
2008-04-16 21:22 ` Doug Evans [this message]
2008-04-16 22:49 ` Doug Evans
2008-04-17 21:29 ` Joel Brobecker
2008-04-17 22:01 ` Daniel Jacobowitz
2008-04-17 22:45 ` Joel Brobecker
2008-04-28 18:52 ` Fwd: " Doug Evans
2008-04-29 0:54 ` Eli Zaretskii
2008-05-06 3:15 ` Doug Evans
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=e394668d0804161231t61f3507fj11ade43e8a4faa69@mail.gmail.com \
--to=dje@google.com \
--cc=brobecker@adacore.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