public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA_v3 0/8] Implement 'frame apply COMMAND', enhance 'thread apply COMMAND'
Date: Fri, 29 Jun 2018 12:22:00 -0000	[thread overview]
Message-ID: <20180629122158.GH15881@embecosm.com> (raw)
In-Reply-To: <20180624183708.888-1-philippe.waroquiers@skynet.be>

* Philippe Waroquiers <philippe.waroquiers@skynet.be> [2018-06-24 20:37:00 +0200]:

> This is the fourth iteration of the patch series that:
>  * implements a new command
>      'frame apply [all | COUNT | -COUNT | id ID...] [FLAG]... COMMAND'.

I still have this patch pending (which I need to ping) but I still
hope to get it merged:

  https://sourceware.org/ml/gdb-patches/2018-06/msg00170.html

This patch makes it much clearer (I think) that there are multiple was
to IDentify a frame, level, address, function-name.

I wonder if using the keyword 'id' might be confusing were my patch to
end up being merged?  Would a consistent 'level' be better?

Interested to hear your thoughts...

Thanks,
Andrew





>  * enhance 'thread apply COMMAND' by adding FLAG arguments.
>  * adds some shortcuts commands.
>  * documents the above in gdb.texinfo and NEWS.
>  * adds a unit test for cli-utils.c.
>  * adds test for 'frame apply'.
>  * modify gdb.threads/pthreads.exp to test 'thread apply' FLAG arguments.
> 
> The fourth version is RFA v3. It handles the comments given by Pedro.
> The main changes compared to RFA v2 are:
>   * The -q (quiet) flag replaces the verbosity/-v/-q concept.
>   * Addition of 'frame apply id ID... [FLAG]... COMMAND' to allow
>     applying a command on a selected list of frames.
>   * [FLAG]... arguments are now parsed iteratively.
>   * Documentation and on-line help updated accordingly.
>   * tests updated accordingly.
> 
> The third version was RFA v2, handling the comments of Pedro about giving
> the flags individually.
> The changes compared to RFA v1 is:
>   * The flags must be given individually, such as -v -v -c.
>   * The documentation and on-line help was updated accordingly.
>   * ChangeLog information is distributed in each commit log message.
> 
> The second version was RFA v1, changes compared to RFC are:
>   * Replied to all comments of Eli and Simon.
>   * Tests and ChangeLog entries added.
>   * Comments received from Pedro
> 
> The first version was an RFC
>   * Code and doc was complete, but was lacking ChangeLog and tests.
>   * Comments received from Eli and Simon.
> 
> 
> 
> 
> 

  parent reply	other threads:[~2018-06-29 12:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-24 18:37 Philippe Waroquiers
2018-06-24 18:37 ` [RFA_v3 8/8] Add a self-test for cli-utils.c Philippe Waroquiers
2018-07-09 19:27   ` Pedro Alves
2018-06-24 18:37 ` [RFA_v3 7/8] Modify gdb.threads/pthreads.exp to test FLAG qcs arguments for thread apply Philippe Waroquiers
2018-06-24 18:37 ` [RFA_v3 2/8] Implement frame apply [all | COUNT | -COUNT | id ID... ] [FLAG]... COMMAND Philippe Waroquiers
2018-07-09 19:16   ` Pedro Alves
2018-07-10 21:50     ` Philippe Waroquiers
2018-06-24 18:37 ` [RFA_v3 4/8] Documents the new commands 'frame apply', faas, taas, tfaas Philippe Waroquiers
2018-07-09 19:16   ` Pedro Alves
2018-06-24 18:37 ` [RFA_v3 3/8] Add [FLAG]... arguments to 'thread apply' Philippe Waroquiers
2018-07-09 19:18   ` Pedro Alves
2018-06-24 18:37 ` [RFA_v3 5/8] Announce the user visible changes for frame/thread apply in NEWS Philippe Waroquiers
2018-06-24 18:37 ` [RFA_v3 1/8] Add helper functions parse_flags and parse_flags_qcs Philippe Waroquiers
2018-07-09 19:14   ` Pedro Alves
2018-06-24 18:37 ` [RFA_v3 6/8] Add a test for 'frame apply' Philippe Waroquiers
2018-07-09 19:19   ` Pedro Alves
2018-06-29 12:22 ` Andrew Burgess [this message]
2018-06-29 20:16   ` [RFA_v3 0/8] Implement 'frame apply COMMAND', enhance 'thread apply COMMAND' Philippe Waroquiers
2018-06-29 20:38     ` Philippe Waroquiers
2018-07-09 19: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=20180629122158.GH15881@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --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).