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

On Fri, 2018-06-29 at 13:21 +0100, Andrew Burgess wrote:
> 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...

Counting in gdb.texinfo, I see 5 references to regexp 'frame.id'
(but I am not at all sure that these are referencing the #integer
that backtrace shows).

I see one reference to 'frame.level'.

I see 8 references to 'frame.number', and some of these
references are explicitly explaining that backtrace shows
a frame number.

In the code, I see a bunch of occurrences of 'frame.level'
and much more of 'frame.id', but as far as I can see, frame id
is rather the internal 'struct frame_id' concept.
frame.number seems not used too much in the code, except
as traceframe_number

So, for me, fine to replace
   Usage: frame apply id ID... [FLAG]... COMMAND
   ID is a space-separated list of IDs of frames to apply COMMAND on.
by
   Usage: frame apply level LEVEL... [FLAG]... COMMAND
   LEVEL is a space-separated list of frames identified by their level to apply COMMAND on.

But if we want to keep the current use of frame number, it should rather be 
   Usage: frame apply number NUMBER... [FLAG]... COMMAND
   NUMBER is a space-separated list of frames identified by their number to apply COMMAND on.

Whatever we take, we have to ensure that gdb.texinfo systematically use 
it to identify a frame as shown by backtrace (#integer).


All the above change is quite mechanical, but that is better done once feedback
is given e.g. by Pedro over this patch RFA_v3 and about your patch.

And then, we need to see in which order which patch is applied.
(I slightly prefer my patch first, but I guess you slightly prefer
your patch first :).

So let e.g. Pedro decide about which one is ready to go in first.

In summary: review needed, and then a decision about the above and
   about which patch goes first ...

Thanks

Philippe

  reply	other threads:[~2018-06-29 20:16 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 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 7/8] Modify gdb.threads/pthreads.exp to test FLAG qcs arguments for thread apply Philippe Waroquiers
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-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 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 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 5/8] Announce the user visible changes for frame/thread apply in NEWS Philippe Waroquiers
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-29 12:22 ` [RFA_v3 0/8] Implement 'frame apply COMMAND', enhance 'thread apply COMMAND' Andrew Burgess
2018-06-29 20:16   ` Philippe Waroquiers [this message]
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=1530303340.1512.15.camel@skynet.be \
    --to=philippe.waroquiers@skynet.be \
    --cc=andrew.burgess@embecosm.com \
    --cc=gdb-patches@sourceware.org \
    /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).