This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch][python] 5 of 5 - Frame filter documentation changes
- From: Tom Tromey <tromey at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Phil Muldoon <pmuldoon at redhat dot com>, gdb-patches at sourceware dot org
- Date: Wed, 05 Dec 2012 12:11:21 -0700
- Subject: Re: [patch][python] 5 of 5 - Frame filter documentation changes
- References: <50B8C35F.9040000@redhat.com> <83boeet4wh.fsf@gnu.org>
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Eli> So in CLI, each filter can be enabled and disabled individually, but
Eli> in MI they can only be enabled en masse, and cannot be disabled? is
Eli> that a good idea?
In MI it is fine. It is no extra effort for an MI client to request
unfiltered output on each invocation it cares to.
The reason for the enablement command for MI is just so that clients
don't get filtered output without expecting it. This would work ok --
the output is backward compatible -- but could be surprising to users.
An MI client could disable filters individually. The commands are
always there.
Tom