From: Yao Qi <qiyaoltc@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Update help of the "frame" command
Date: Tue, 10 Jan 2017 11:00:00 -0000 [thread overview]
Message-ID: <20170110110032.GE9518@E107787-LIN> (raw)
In-Reply-To: <47dca06e2fcc932db67832e6c1867e92@polymtl.ca>
On 17-01-09 13:13:42, Simon Marchi wrote:
> Indeed, it's the commit "Initial creation of sourceware repository".
> I checked out that commit and looked at the code, but couldn't find
> anything that would suggest that the output of the frame command
> would not be printed when it's executing in a script or user
> command.
>
> I went earlier using the old tarballs on the website [1], and found
> that in old gdb's, there was code like this:
>
> 965 if (!from_tty)
> 966 return;
> 967
> 968 print_stack_frame (selected_frame, selected_frame_level, 1);
>
> The (!from_tty) check disappeared in gdb 4.3. I think it's this change:
>
> 873 Thu Oct 24 09:33:44 1991 John Gilmore (gnu at cygnus.com)
> 874
> 875 * stack.c (frame_command): Always print. Use new
> 876 frame_select_command to select a frame without printing.
>
> after that, the frame_command function becomes simply:
>
> 974 static void
> 975 frame_command (level_exp, from_tty)
> 976 char *level_exp;
> 977 int from_tty;
> 978 {
> 979 select_frame_command (level_exp, from_tty);
> 980 print_stack_frame (selected_frame, selected_frame_level, 1);
> 981 }
>
> So I think it's safe.
Thanks for digging it up. Patch is OK.
>
> Side-question, is there a git repo somewhere with all these old gdb
> versions, those that predate what's in the current git tree? It
> would be useful to have a repo with one commit per version. Here I
> had to download many tarballs and bisect manually, but if they had
> been in a repo it would have been trivial. If it doesn't exist yet,
> I think I'll do it.
>
> [1] ftp://sourceware.org/pub/gdb/old-releases/
They were imported into the git repository. The change you found
above is in b00771232fab861fb31e42dfd5f6643ba1b43cc9
--
Yao (é½å°§)
next prev parent reply other threads:[~2017-01-10 11:00 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
2017-01-09 18:13 ` Simon Marchi
2017-01-10 11:00 ` Yao Qi [this message]
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=20170110110032.GE9518@E107787-LIN \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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