Re: [PATCH] Add support to control auto-display behavior

[Christopher Layne <clayne@anodized.com>]

On Sat, Apr 07, 2007 at 01:25:39PM -0400, Daniel Jacobowitz wrote:
> On Fri, Apr 06, 2007 at 04:52:59PM +0300, Eli Zaretskii wrote:
> > > initially setup some auto-displays and then begin stepping. I don't see
> > > any reason why, in the event an object is not accessible, the auto-display
> > > should be disabled.
> > 
> > Thanks.  I agree that it's a good idea to have an option to control
> > this, unless we agree that what you want as an option should be how
> > GDB behaves in all cases.
> 
> I think changing the behavior unconditionally would be a good idea.
> Showing the error is more sensible; it's always bugged me that my
> displays get turned off (and sometimes deleted instead of disabled - I
> do not know why that happens).

My thinking is the same as well - it bugged me enough that I decided to
do something about it. Kinda funny, I went on a research hunt for exactly
where the line of output "avoid infinite recursion" had been added, hoping
to find some rationale, and it looks like it's been there since the early 90s.

I originally had it as "disable-on-error" but changed it to "strict" and
non-default as I wasn't sure if the original intended behavior had a real
reason for being there. If it's okay with you guys, I'll restructure the
patch to fix some of the documentation issues and semantics to assume it
as default behavior.

-cl