This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Add support to control auto-display behavior
- From: Daniel Jacobowitz <drow at false dot org>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: Christopher Layne <clayne at anodized dot com>, gdb-patches at sources dot redhat dot com
- Date: Sat, 7 Apr 2007 13:25:39 -0400
- Subject: Re: [PATCH] Add support to control auto-display behavior
- References: <20070406110435.GC27568@ns1.anodized.com> <u1wix4nk4.fsf@gnu.org>
On Fri, Apr 06, 2007 at 04:52:59PM +0300, Eli Zaretskii wrote:
> > Date: Fri, 6 Apr 2007 04:04:35 -0700
> > From: Christopher Layne <clayne@anodized.com>
> >
> > This patch is to allow setting how auto-displays are affected when memory is
> > not accessible. It's very common to, when single-stepping, or stepping over,
> > 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).
--
Daniel Jacobowitz
CodeSourcery