Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: ac131313@ges.redhat.com
Cc: gdb@sources.redhat.com
Subject: Re: Getting the i386 watchpoints into the taget vector?
Date: Sat, 21 Sep 2002 01:32:00 -0000	[thread overview]
Message-ID: <3099-Sat21Sep2002113200+0300-eliz@is.elta.co.il> (raw)
In-Reply-To: <3D8BB499.7080306@ges.redhat.com> (message from Andrew Cagney on Fri, 20 Sep 2002 19:51:53 -0400)

> Date: Fri, 20 Sep 2002 19:51:53 -0400
> From: Andrew Cagney <ac131313@ges.redhat.com>
> 
> GDB can implement watchpoints, for a remote target, using two mechanism:
> 
> - sending the remote target the watchpoint request (the Z packet) and 
> let the remote target implement the details
> 
> - manipulate the h/w watchpoint registers directly, sending the remote 
> target register read/write operations - what I believe i386-nat.c does.

It doesn't really matter, IMHO, which way we choose to go.  What is
important is that we provide in GDB a module that can be used by i386
targets, either native or remote, and that this module has the same
machinery that is now implemented for native i386 debugging.  To wit,
the replica of the machine debug registers should be maintained by
that module, and it should use reference counts to allow sharing of
debug registers between different watchpoints.

In other words, if we go the first way, target ends should not need
to invent the implementation, but instead should call functions in a
module supplied as part of the GDB sources.


      reply	other threads:[~2002-09-21  8:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19 18:57 Andrew Cagney
2002-09-20  0:38 ` Kevin Buettner
2002-09-20  6:32 ` Paul Koning
2002-09-20  8:26   ` Andrew Cagney
2002-09-20 14:42 ` Eli Zaretskii
2002-09-20 16:51   ` Andrew Cagney
2002-09-21  1:32     ` 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=3099-Sat21Sep2002113200+0300-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@ges.redhat.com \
    --cc=gdb@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