Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: muller@ics.u-strasbg.fr, gdb-patches@sourceware.org,
	pedro@codesourcery.com
Subject: Re: [RFC] Remove i386 low level debug register function from nm- header file.
Date: Tue, 12 May 2009 15:17:00 -0000	[thread overview]
Message-ID: <83octyxsgb.fsf@gnu.org> (raw)
In-Reply-To: <200905121500.n4CF0Z1B016661@d12av02.megacenter.de.ibm.com>

> Date: Tue, 12 May 2009 17:00:35 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
> Cc: gdb-patches@sourceware.org, pedro@codesourcery.com ('Pedro Alves'),
>         eliz@gnu.org ('Eli Zaretskii')
> 
> > > I think you should provide everything in i386-nat.c (and
> > > the new i386-nat.h) unconditionally, and eliminate the
> > > various definitions of I386_USE_GENERIC_WATCHPOINTS in the
> > > nm- header files.
> > 
> >   The only drawback is that "maint show-debug--regs" command
> > will then also appear on target that do not support
> > debug registers... Anyhow, it will just be a no-op in that case.
> > Is that a problem?
> 
> I don't think so.  The command simply says: "whenever the hardware
> debug registers are changed, display their contents".  Being able
> to set that flag on a system that happens to never use hardware
> debug register should be fine, the condition just never occurs.

I'd rather we displayed an error message when this command is used on
platforms where it has no effect.  Silently doing nothing is not a
good UI.  But that's me.


  reply	other threads:[~2009-05-12 15:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-10 14:54 Pierre Muller
2009-05-10 17:37 ` Eli Zaretskii
2009-05-12 13:02 ` Ulrich Weigand
2009-05-12 14:37   ` Pierre Muller
2009-05-12 15:00     ` Ulrich Weigand
2009-05-12 15:17       ` Eli Zaretskii [this message]
2009-05-12 15:45         ` Pierre Muller
2009-05-12 16:06           ` Ulrich Weigand
2009-05-12 16:19             ` Pedro Alves
2009-05-12 21:28     ` [RFC-v2] " Pierre Muller
2009-05-13 15:33       ` Ulrich Weigand
2009-05-13 18:09         ` Eli Zaretskii
2009-05-13 18:35           ` Ulrich Weigand
2009-05-13 18:25         ` Doug Evans
2009-05-13 18:38           ` Ulrich Weigand
2009-05-13 22:21           ` Pierre Muller
2009-05-13 23:16             ` Doug Evans
2009-05-13 23:39         ` [RFA-v3] " Pierre Muller
2009-05-14  9:06           ` Ulrich Weigand
2009-05-14  9:10             ` Joel Brobecker
2009-05-14  9:40             ` Pierre Muller
2009-05-14 15:32             ` Macros in config files Pierre Muller
2009-05-14 18:31               ` Ulrich Weigand

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=83octyxsgb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    --cc=pedro@codesourcery.com \
    --cc=uweigand@de.ibm.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