This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Fwd: Re: [RFA v2 00/13] various frame filter fixes and cleanups
- From: Phil Muldoon <pmuldoon at redhat dot com>
- To: "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
- Date: Fri, 18 Aug 2017 11:50:17 +0100
- Subject: Fwd: Re: [RFA v2 00/13] various frame filter fixes and cleanups
- Authentication-results: sourceware.org; auth=none
- References: <0e1254bf-7a85-1611-0f22-52908f942d85@redhat.com>
Forwarding to list for completeness due to the Sourceware data loss.
-------- Forwarded Message --------
Subject: Re: [RFA v2 00/13] various frame filter fixes and cleanups
Date: Tue, 15 Aug 2017 13:35:39 +0100
From: Phil Muldoon <pmuldoon@redhat.com>
To: Tom Tromey <tom@tromey.com>
CC: Pedro Alves <palves@redhat.com>, gdb-patches@sourceware.org
> But on that note, it's a suggestion, not an objection to the current
> patch. I also acknowledge that my proposal is somewhat orthogonal to
> the original functionality proposed in this patch.
>
> Cheers
>
> Phil
>
Oops, one last point I forgot to make. Controlling visibility from the
FrameDecorator allows frame filters to react appropriately to Python
GDB parameters. So, for example, in the spider monkey patch set, you
could have a parameter like "set sm-show-elided on". The Frame
Decorator, when printing, could query the Python variable holding this
value and make decisions on what to print when the backtrace is
invoked. In your patch set, you could have a few tuneable parameters
with the set command that could be used to focus backtraces for
different scenarios/developers.
Cheers
Phil