Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] command trace / source verbose mode
Date: Thu, 20 Jul 2006 19:24:00 -0000	[thread overview]
Message-ID: <u64hshyg9.fsf@gnu.org> (raw)
In-Reply-To: <44BFB35D.9080609@st.com> (message from Andrew STUBBS on Thu, 20 	Jul 2006 17:46:21 +0100)

> Date: Thu, 20 Jul 2006 17:46:21 +0100
> From: Andrew STUBBS <andrew.stubbs@st.com>
> Cc: gdb-patches@sources.redhat.com
> 
> Here is an updated version of my patch. I think I have addressed all 
> your points.

Thanks.

> -  if (file == NULL)
> +  if (file == NULL || strlen (file) == 0)
                         ^^^^^^^^^^^^^^^^^^
Nitpicking: isn't it better to use *file == 0 instead?

>        error (_("source command requires pathname of file to source."));

Another nit: the GNU project does not like to use ``pathname''; please
use ``file name'' (yes, two words) instead.

> +Optional -v switch (before the filename) causes each command in\n\
> +FILE to be echo as it is executed.\n\
        ^^^^^^^^^^
You meant "to be echoed", right?

>  Note that the file \"%s\" is read automatically in this way\n\
>  when gdb is started."), gdbinit);

I think "gdb" should be up-cased.

> +If you need to debug user-defined commands or sourced files you may find it
> +useful to enable command tracing.

This paragraph could benefit from two small changes:

 . enclose "command tracing" in the above sentence in @dfn{}, to make
   it stand out--this is a new term you are introducing here
 . add "@cindex command tracing" before the paragraph

Otherwise, the patch is okay with me.  Thanks.


  reply	other threads:[~2006-07-20 19:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 18:01 Andrew STUBBS
2005-11-16 20:11 ` Eli Zaretskii
2005-11-17 16:21   ` Andrew STUBBS
2006-07-06 13:16     ` Daniel Jacobowitz
2006-07-06 17:23       ` Andrew STUBBS
2006-07-06 17:33         ` Daniel Jacobowitz
2006-07-07 16:18           ` Andrew STUBBS
2006-07-08 12:02             ` Eli Zaretskii
2006-07-20 16:46               ` Andrew STUBBS
2006-07-20 19:24                 ` Eli Zaretskii [this message]
2006-07-21 14:48                   ` Andrew STUBBS
2006-07-21 14:49                     ` Daniel Jacobowitz
2006-07-20 19:38                 ` Daniel Jacobowitz

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=u64hshyg9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrew.stubbs@st.com \
    --cc=gdb-patches@sources.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