public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Make "bt N" print correct number of frames when using a frame filter
Date: Sun, 25 Feb 2018 18:29:00 -0000	[thread overview]
Message-ID: <22ad5930-4d62-5b4a-83dd-eb0d3e9332c3@simark.ca> (raw)
In-Reply-To: <87muzy9uxf.fsf@tromey.com>

On 2018-02-24 12:09 PM, Tom Tromey wrote:
>>>>>> "Tom" == Tom Tromey <tom@tromey.com> writes:
> 
> Tom> There's a follow-up as well (to change the enum to use
> Tom> DEF_ENUM_FLAGS_TYPE), but that one was OK'd; but still pending since it
> Tom> touched the same code as this patch.
> 
> Tom> This is still pending review.
> 
> Tom> Some discussion here:
> Tom> https://sourceware.org/ml/gdb-patches/2017-07/msg00200.html
> 
> Tom> Original patch here:
> Tom> https://sourceware.org/ml/gdb-patches/2017-04/msg00630.html
> 
> Tom> I have a branch with this patch plus the previously-approved patch to
> Tom> change frame_filter_flags to use DEF_ENUM_FLAGS_TYPE, so if/when this
> Tom> one is ok'd, both will go in.
> 
> Ping again.
> 
> Tom
> 

The patch LGTM, considering all previously made comments are addressed.

Did you post the patch that makes frame_filter_frames an enum flags type?  I
don't see it.  If you think it's obvious enough to push it directly, make sure
to post it on the ML afterwards.

I also noticed that the frame filter flags are documented at many different places:

- above gdbpy_apply_frame_filter
- above extension_language_ops::apply_frame_filter
- above apply_ext_lang_frame_filter
- in enum frame_filter_flags

This is a recipe for them to become out of date, so I think we should only have
it in the enum declaration.  We can address that after your patches have merged.

Simon

  reply	other threads:[~2018-02-25 18:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-23 16:04 Tom Tromey
2017-04-25 18:27 ` Sergio Durigan Junior
2017-04-26  0:17   ` Tom Tromey
2017-05-29 17:21 ` Tom Tromey
2017-09-30 20:38   ` Tom Tromey
2018-02-12 16:45     ` Tom Tromey
2018-02-24 17:09       ` Tom Tromey
2018-02-25 18:29         ` Simon Marchi [this message]
2018-02-26 16:35           ` Tom Tromey
2017-05-31 15:19 ` Phil Muldoon
2017-06-27 18:37 ` Pedro Alves
2017-07-14 18:56   ` Tom Tromey
2017-08-14 14:19     ` 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=22ad5930-4d62-5b4a-83dd-eb0d3e9332c3@simark.ca \
    --to=simark@simark.ca \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).