Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
To: Simon Marchi <simon.marchi@ericsson.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Update help of the "frame" command
Date: Fri, 06 Jan 2017 16:25:00 -0000	[thread overview]
Message-ID: <8d8974b9-4d78-62ba-bd66-d991fdcf2be7@codesourcery.com> (raw)
In-Reply-To: <20170106151610.28872-1-simon.marchi@ericsson.com>

On 01/06/2017 09:16 AM, Simon Marchi wrote:
> The help message of the "frame" command states that nothing is printed
> if the command is executed from the command file or user-defined
> command.  My testing leads me to think that this is not true (at least
> today).
>
>   (gdb) bt
>   #0  bar (n=17) at test.c:9
>   #1  0x00000000004006e0 in foo (v=17) at test.c:13
>   #2  0x00000000004006f0 in main () at test.c:21
>   (gdb) frame
>   #0  bar (n=17) at test.c:9
>   9	    baz(n);
>   (gdb) define foo
>   Type commands for definition of "foo".
>   End with a line saying just "end".
>   >frame 1
>   >end
>   (gdb) foo
>   #1  0x00000000004006e0 in foo (v=17) at test.c:13
>   13	    bar(v);
>
> This patch simply removes that bit from the help message.  I didn't find
> anything corresponding to this in the documentation that needs to be
> fixed.
>
> gdb/ChangeLog:
>
> 	* stack.c (_initialize_stack): Update "frame" command help message.
> ---
>  gdb/stack.c | 4 +---
>  1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/gdb/stack.c b/gdb/stack.c
> index 64224d0aad..201a358833 100644
> --- a/gdb/stack.c
> +++ b/gdb/stack.c
> @@ -2666,9 +2666,7 @@ This is useful in command scripts."));
>  Select and print a stack frame.\nWith no argument, \
>  print the selected stack frame.  (See also \"info frame\").\n\
>  An argument specifies the frame to select.\n\
> -It can be a stack frame number or the address of the frame.\n\
> -With argument, nothing is printed if input is coming from\n\
> -a command file or a user-defined command."));
> +It can be a stack frame number or the address of the frame.\n"));
>
>    add_com_alias ("f", "frame", class_stack, 1);
>
>

Sounds reasonable to me. I ran into other help text block 
inconsistencies. It looks like there is potential for more corrections 
in that area.


  reply	other threads:[~2017-01-06 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 15:16 Simon Marchi
2017-01-06 16:25 ` Luis Machado [this message]
2017-01-06 16:28   ` Simon Marchi
2017-01-06 16:30     ` Luis Machado
2017-01-09 17:27 ` Yao Qi
2017-01-09 18:13   ` Simon Marchi
2017-01-10 11:00     ` Yao Qi
2017-01-10 15:20       ` Simon Marchi
2017-01-10 16:01       ` Pedro Alves

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=8d8974b9-4d78-62ba-bd66-d991fdcf2be7@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@ericsson.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