From: Tom Tromey <tom@tromey.com>
To: Philippe Waroquiers <philippe.waroquiers@skynet.be>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFAv2 1/3] Implement 'set print frame-info|frame-arguments presence'.
Date: Mon, 10 Jun 2019 20:10:00 -0000 [thread overview]
Message-ID: <871s0119rt.fsf@tromey.com> (raw)
In-Reply-To: <1560170884.22517.6.camel@skynet.be> (Philippe Waroquiers's message of "Mon, 10 Jun 2019 14:48:04 +0200")
>>>>> "Philippe" == Philippe Waroquiers <philippe.waroquiers@skynet.be> writes:
>> Is this a pre-existing bug? It seems like something we should change,
>> since my believe is that "no filters" should produce the same output as
>> the situation where there are actually no filters installed.
Philippe> Yes, it is a pre-existing "bug", but the difference of behaviour is
Philippe> between 'bt' and 'bt no-filters' *when there are some filters*.
[...]
Philippe> This difference of behaviour will be visible as long as there is
Philippe> one filter active, even if the filter is a 'no effect' filter.
Philippe> So, the question is: do we want to change the default output behaviour
Philippe> of python frame filters to be LOCATION ?
Philippe> That is of course a user visible change.
Yes, I think this ought to change. Installing a "no effect" filter
should not have any effect on the output.
Tom
prev parent reply other threads:[~2019-06-10 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 18:56 [RFAv2 0/3] Implement 'set print frame-info|frame-arguments Philippe Waroquiers
2019-05-11 18:56 ` [RFAv2 3/3] Document 'set print frame-info|frame-arguments presence' Philippe Waroquiers
2019-05-11 19:18 ` Eli Zaretskii
2019-05-11 18:56 ` [RFAv2 2/3] Test " Philippe Waroquiers
2019-06-04 17:15 ` Tom Tromey
2019-05-11 18:56 ` [RFAv2 1/3] Implement " Philippe Waroquiers
2019-06-04 17:15 ` Tom Tromey
2019-06-10 12:48 ` Philippe Waroquiers
2019-06-10 20:10 ` Tom Tromey [this message]
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=871s0119rt.fsf@tromey.com \
--to=tom@tromey.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