Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: John Hughes <john@Calva.COM>, gdb-patches@sourceware.cygnus.com
Subject: Re: minor fix for i386v-nat.c
Date: Thu, 28 Jun 2001 03:41:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010628134248.12284S-100000@is> (raw)
In-Reply-To: <3B3AB452.9000304@cygnus.com>

On Thu, 28 Jun 2001, Andrew Cagney wrote:

> Did anyone ever look at this?

Is any x86 port still using this code?  I'd expect them all to switch
to the new watchpoint support in i386-nat.c, by now.

> > In i386_insert_aligned_watchpoint the actual address being watched
> > was saved in address_loookup.  This is fine for aligned
> > watchpoints, the address gdb wants to watch is the same as the
> > actual address.  For non-aligned watchpoints we have to ask the
> > hadware to watch up to 3 different addresses.  We need to remember
> > the address gdb wants to watch so i386_remove_watchpoint knows
> > which registers to clean up.

Won't this do the wrong thing in i386_stopped_by_watchpoint?  You'll
report the wrong address there (not the one the debug register
actually watched).

I think a cleaner way to do this is to store the actual address being
watched by the DRi, but to modify i386_remove_watchpoint to break up
its act into several individual removals like
i386_insert_aligned_watchpoint does.  This is what the code in
i386-nat.c does.


      parent reply	other threads:[~2001-06-28  3:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <NCBBLMGKIKDGJMEOMNMEMEDEHEAA.john@Calva.COM>
2001-06-27 21:36 ` Andrew Cagney
2001-06-28  0:47   ` John Hughes
2001-06-28  2:58   ` John Hughes
2001-06-28  3:42     ` Eli Zaretskii
2001-06-28  9:23       ` Andrew Cagney
2001-06-28  3:41   ` Eli Zaretskii [this message]

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=Pine.SUN.3.91.1010628134248.12284S-100000@is \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=john@Calva.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