Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Christopher Layne <clayne@anodized.com>, 	gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Add support to control auto-display behavior
Date: Sat, 07 Apr 2007 17:25:00 -0000	[thread overview]
Message-ID: <20070407172539.GB24650@caradoc.them.org> (raw)
In-Reply-To: <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


  reply	other threads:[~2007-04-07 17:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-06 11:04 Christopher Layne
2007-04-06 13:53 ` Eli Zaretskii
2007-04-07 17:25   ` Daniel Jacobowitz [this message]
2007-04-07 20:20     ` Christopher Layne
2007-04-07 22:18       ` Daniel Jacobowitz
2007-04-07 22:27         ` Christopher Layne
2007-04-08  3:08           ` Daniel Jacobowitz
2007-04-08  8:05       ` Eli Zaretskii

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=20070407172539.GB24650@caradoc.them.org \
    --to=drow@false.org \
    --cc=clayne@anodized.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    /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