Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Update help of the "frame" command
Date: Mon, 09 Jan 2017 17:27:00 -0000	[thread overview]
Message-ID: <20170109172726.GA9518@E107787-LIN> (raw)
In-Reply-To: <20170106151610.28872-1-simon.marchi@ericsson.com>

On 17-01-06 10:16:10, Simon Marchi wrote:
> @@ -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"));
>  

These two lines were added many years ago,

c906108c (Stan Shebs       1999-04-16 01:35:26 +0000 2632) It can be a stack frame number or the address of the frame.\n\
c906108c (Stan Shebs       1999-04-16 01:35:26 +0000 2633) With argument, nothing is printed if input is coming from\n\

Did you do some archaeology to see how GDB did at that time? and then
we may know these help doc is a leftover of some changes.  If we can
find them, we are confident to remove these doc.  I spent 30 minutes
on c906108c, but didn't find any evidence.

-- 
Yao (齐尧)


  parent reply	other threads:[~2017-01-09 17:27 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
2017-01-06 16:28   ` Simon Marchi
2017-01-06 16:30     ` Luis Machado
2017-01-09 17:27 ` Yao Qi [this message]
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=20170109172726.GA9518@E107787-LIN \
    --to=qiyaoltc@gmail.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