From: Tom Tromey <tromey@redhat.com>
To: Samuel Bronson <naesten@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Add "set/show debug unwinder" prefix commands.
Date: Thu, 04 Jun 2009 22:05:00 -0000 [thread overview]
Message-ID: <m33aafwt7x.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1243638987-4533-2-git-send-email-naesten@gmail.com> (Samuel Bronson's message of "Fri\, 29 May 2009 19\:16\:27 -0400")
>>>>> "Samuel" == Samuel Bronson <naesten@gmail.com> writes:
Samuel> Also add one subcommand for tracing the sniffing of stack
Samuel> frames by unwinders.
This is also basically ok; just needs a ChangeLog and some formatting
fixlets, nothing serious.
Samuel> +/* trace unwinders called */
Samuel> +static int trace_unwinders;
In the GNU style, comments should be sentences, so should start with a
capital letter and end with a period followed by two spaces. Yes,
we're that nit picky ;)
There are a few instances of this.
Samuel> + if (trace_unwinders) {
Samuel> + fprintf_unfiltered (gdb_stdlog, "[ Searching for unwinder for frame ...\n");
Samuel> + }
Drop the braces.
Samuel> for (entry = table->list; entry != NULL; entry = entry->next)
Samuel> {
Samuel> struct cleanup *old_cleanup;
Samuel> + const char *uname = entry->unwinder->unwinder_name;
Samuel> +
Samuel> + if (trace_unwinders) {
The opening brace is misplaced here, in the GNU style it goes on the
next line. There are a couple instances of this.
Samuel> + add_setshow_boolean_cmd ("trace-tried", class_maintenance, &trace_unwinders,
I think this could just be "set debug unwinder", rather than
"set debug unwinder trace-tried".
If you do plan to send another "debug unwinder" sub-command, maybe we
could discuss the naming now, before the patch.
Tom
next prev parent reply other threads:[~2009-06-04 22:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 23:09 [PATCH 1/2] Add an undwinder_name field to "struct frame_unwind" for use by "info frame" Samuel Bronson
2009-05-29 23:10 ` [PATCH 2/2] Add "set/show debug unwinder" prefix commands Samuel Bronson
2009-05-30 6:57 ` Eli Zaretskii
2009-05-30 19:25 ` Doug Evans
2009-05-31 15:50 ` Samuel Bronson
2009-06-04 22:05 ` Tom Tromey [this message]
2009-06-09 0:49 ` Samuel Bronson
2009-06-09 19:44 ` Tom Tromey
2009-06-04 22:00 ` [PATCH 1/2] Add an undwinder_name field to "struct frame_unwind" for use by "info frame" Tom Tromey
2009-06-09 0:24 ` Samuel Bronson
2009-06-09 19:41 ` Tom Tromey
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=m33aafwt7x.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=naesten@gmail.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