public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Cc: Philippe Waroquiers <philippe.waroquiers@skynet.be>,
	Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCHv5 0/2] gdb: Change how frames are selected for 'frame' and 'info frame'.
Date: Mon, 27 Aug 2018 11:04:00 -0000	[thread overview]
Message-ID: <20180827110353.GE32506@embecosm.com> (raw)
In-Reply-To: <cover.1534197786.git.andrew.burgess@embecosm.com>

Ping!

Eli:

  In this message:
      https://sourceware.org/ml/gdb-patches/2018-07/msg00670.html
  Philippe highlighted that you might have some reservations about
  this patch series, which I think is currently the main blocker for
  this patch getting approval.

  In the thread started here:
      https://sourceware.org/ml/gdb-patches/2018-05/msg00299.html
  and ending here:
      https://sourceware.org/ml/gdb-patches/2018-06/msg00142.html
  you did review and approve one of the original patch variants, which
  is most like the "level" variant of the patch submitted here:
      https://sourceware.org/ml/gdb-patches/2018-08/msg00337.html

  I would be really grateful if you could let me know your current
  thoughts on this patch, are you happy to have the "level" variant
  merged based on your previous approval, or has you position changed?

  Thanks.

Philippe:

  Thanks for the review and feedback in:
      https://sourceware.org/ml/gdb-patches/2018-08/msg00349.html

  I wasn't sure if the second part of you mail was suggesting that
  those instances of level vs number needed to be resolved as part of
  this patch for you to be happy, or if this was just identifying what
  we should clean up if/when this patch is merged.  Additional clarity
  here would help me figure out my next steps for getting this patch
  merged.

  Thanks.

Many thanks to everyone who's taken time to review this for me.

Thanks,
Andrew



* Andrew Burgess <andrew.burgess@embecosm.com> [2018-08-13 23:20:09 +0100]:

> Given a lack of feedback on v4, I've put together two alternative
> versions to pick between...
> 
>   (A) In this version I took onboard the feedback from Eli and
>       Philippe that using "level" might be confusing to users, as
>       "number" is historically what has been used for the integer
>       label we give to frames.
> 
>       The command for selecting a frame by integer is now, 'frame
>       number <NUMBER>' and almost all references to "level" have now
>       been removed from the patch.
> 
>   (B) In this version I've taken onboard the advice from Philippe,
>       identifying places in the patch where I was mixing use of
>       "level" and "number".  I've doubled down on "level" and removed
>       most uses of "number" from the patch.
> 
> If we select patch 'A' then me might want to update 'frame apply level
> ...' to 'frame apply number ...' for consistency.
> 
> If we select patch 'B' then we will probably need a follow up patch
> that goes through the documentation to tighten up references to
> "number" vs "level".
> 
> I really don't mind which approach we take, I guess I'd probably pick
> 'B' over 'A' given we already have 'frame apply level ...' in GDB, but
> if there's preference for 'A' then that's fine.
> 
> I'm also happy to do the follow up patches once we have some agreement
> on which way to go.
> 
> Thanks,
> Andrew
> 
> ---
> 
> Andrew Burgess (1):
>   gdb: Change how frames are selected for 'frame' and 'info frame'.
> 
>  gdb/ChangeLog                               |  36 ++
>  gdb/NEWS                                    |   8 +
>  gdb/cli/cli-decode.c                        |  44 ++-
>  gdb/command.h                               |  14 +
>  gdb/doc/ChangeLog                           |   8 +
>  gdb/doc/gdb.texinfo                         | 108 ++++--
>  gdb/mi/mi-cmd-stack.c                       |   4 +-
>  gdb/stack.c                                 | 535 +++++++++++++++++++---------
>  gdb/stack.h                                 |   2 +-
>  gdb/testsuite/ChangeLog                     |   7 +
>  gdb/testsuite/gdb.base/frame-selection.c    |  52 +++
>  gdb/testsuite/gdb.base/frame-selection.exp  | 157 ++++++++
>  gdb/testsuite/gdb.mi/mi-frame-selection.c   |  34 ++
>  gdb/testsuite/gdb.mi/mi-frame-selection.exp |  89 +++++
>  14 files changed, 896 insertions(+), 202 deletions(-)
>  create mode 100644 gdb/testsuite/gdb.base/frame-selection.c
>  create mode 100644 gdb/testsuite/gdb.base/frame-selection.exp
>  create mode 100644 gdb/testsuite/gdb.mi/mi-frame-selection.c
>  create mode 100644 gdb/testsuite/gdb.mi/mi-frame-selection.exp
> 
> -- 
> 2.14.4
> 

  parent reply	other threads:[~2018-08-27 11:04 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-08 16:58 [PATCHv2 0/2] Changes to frame selection Andrew Burgess
2018-05-08 16:58 ` [PATCHv2 1/2] gdb: Split func_command into two parts Andrew Burgess
2018-05-18 19:57   ` Pedro Alves
2018-05-21 15:52     ` Andrew Burgess
2018-05-21 16:06       ` Pedro Alves
2018-05-08 16:59 ` [PATCHv2 2/2] gdb: Change how frames are selected for 'frame' and 'info frame' Andrew Burgess
2018-05-11 15:44   ` Eli Zaretskii
2018-05-21 12:16     ` Andrew Burgess
2018-05-21 17:46       ` Eli Zaretskii
2018-06-05 18:53         ` Andrew Burgess
2018-06-05 21:16           ` Philippe Waroquiers
2018-06-06  8:22             ` Andrew Burgess
2018-06-06 14:56               ` Eli Zaretskii
2018-06-07 16:19   ` [PATCHv3] " Andrew Burgess
2018-06-29 12:23     ` Andrew Burgess
2018-07-17 15:58     ` [PATCHv4] " Andrew Burgess
2018-07-23 20:46       ` Philippe Waroquiers
2018-07-25 18:14         ` Andrew Burgess
2018-08-13 22:20           ` [PATCHv5_A 1/2] " Andrew Burgess
2018-08-13 22:20           ` [PATCHv5 0/2] " Andrew Burgess
2018-08-14 10:31             ` Philippe Waroquiers
2018-08-21 13:10               ` Joel Brobecker
2018-08-27 11:04             ` Andrew Burgess [this message]
2018-08-27 15:23               ` Eli Zaretskii
2018-08-28  8:43                 ` Andrew Burgess
2018-08-28  9:08                   ` Eli Zaretskii
2018-08-28 18:03                     ` [PATCHv6] " Andrew Burgess
2018-08-28 18:20                       ` Eli Zaretskii
2018-09-05  7:46                       ` PING: " Andrew Burgess
2018-09-13 18:02                       ` Pedro Alves
2018-09-18 23:01                         ` Andrew Burgess
2018-09-19 16:26                           ` Pedro Alves
2018-09-26 23:06                             ` Andrew Burgess
2018-09-27 20:58                               ` Pedro Alves
     [not found]           ` <cover.1534197765.git.andrew.burgess@embecosm.com>
2018-08-13 22:20             ` [PATCHv5_B 2/2] " Andrew Burgess

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=20180827110353.GE32506@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=philippe.waroquiers@skynet.be \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).