From: Joel Brobecker <brobecker@adacore.com>
To: Tristan Gingold <gingold@adacore.com>
Cc: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [RFA] Add set/show debug unwind command
Date: Fri, 15 Jun 2012 17:31:00 -0000 [thread overview]
Message-ID: <20120615173114.GV18729@adacore.com> (raw)
In-Reply-To: <FA7F98C8-BFF4-4F68-AB6A-AC75DE73C09A@adacore.com>
Hi Tristan,
> 2012-06-15 Tristan Gingold <gingold@adacore.com>
>
> * frame-unwind.c (show_unwind_debug): New function
> (unwind_debug): New variable.
> (_initialize_frame_unwind): Add show debug unwind command.
> * frame-unwind.h (unwind_debug): Declare.
Overall, I think this is OK, but since it's not used until your next
patch gets in, can you commit both at the same time?
You're missing a period at the of the first line.
A few comments...
> +/* Flag to control debugging. */
> +
> +int unwind_debug;
> +static void
Can you add an empty line between the two?
Also, I am really campaining for every single function to be
documented, no matter how obvious what the function does.
Can you please update this patch accordingly? For the function
below, you can just say "Implements the "show debug unwind"
command, for instance.
> + /* Debug this files internals. */
file's
> + add_setshow_zinteger_cmd ("unwind", class_maintenance, &unwind_debug, _("\
> +Set unwind debugging."), _("\
> +Show unwind debugging."), _("\
For such short descriptions, I don't think we should use the formatting
you chose. We discussed this a while back, and the consensus was that
we should try to avoid it unless it makes sense. Here, I find it does
not help reading the code (the contrary, IMO), and generally speaking
it screws up the -p option of "diff".
> +When non-zero, frame specific internal debugging is enabled."),
Even for this one, let's not use that formatting, let's just split it
in two strings, like so:
_("When non-zero, frame specific internal "
"debugging is enabled."),
Thanks,
--
Joel
next prev parent reply other threads:[~2012-06-15 17:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 7:51 Tristan Gingold
2012-06-15 17:31 ` Joel Brobecker [this message]
2012-06-15 17:40 ` Joel Brobecker
2012-06-15 18:18 ` Pedro Alves
2012-06-15 18:22 ` Joel Brobecker
2012-06-18 9:12 ` Tristan Gingold
2012-06-18 15:50 ` Joel Brobecker
2012-06-18 16:11 ` Eli Zaretskii
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=20120615173114.GV18729@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.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