Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: eliz@gnu.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: [COMMIT] HP-UX hardware watchpoint fallout
Date: Sat, 25 Dec 2004 12:36:00 -0000	[thread overview]
Message-ID: <200412251020.iBPAK4Zn026042@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <01c4ea68$Blat.v2.2.2$e9ac5460@zahav.net.il> (eliz@gnu.org)

   Date: Sat, 25 Dec 2004 12:01:50 +0200
   From: "Eli Zaretskii" <eliz@gnu.org>

   > Date: Fri, 24 Dec 2004 23:58:14 +0100 (CET)
   > From: Mark Kettenis <kettenis@gnu.org>
   > 
   > from  Mark Kettenis  <kettenis@gnu.org>
   > 
   > 	* target.h (TARGET_DISABLE_HW_WATCHPOINTS)
   > 	(TARGET_ENABLE_HW_WATCHPOINTS): Remove macros.

   Thanks.

   Please also remove their documentation from gdbint.texinfo.  (In
   general, when a macro is removed from target.h, one should search
   gdbint.texinfo for that macro.)

Oops, I forgot to commit that part.  Here it is.  Guess it's obvious,
so it's committed now.

Mark

P.S. Still working on that general description about implementing
hardware watchpoints using memory protections.


Index: doc/ChangeLog
===================================================================
RCS file: /cvs/src/src/gdb/doc/ChangeLog,v
retrieving revision 1.464
diff -u -p -r1.464 ChangeLog
--- doc/ChangeLog	8 Dec 2004 05:28:31 -0000	1.464
+++ doc/ChangeLog	25 Dec 2004 10:15:54 -0000
@@ -1,3 +1,8 @@
+2004-12-24  Mark Kettenis  <kettenis@gnu.org>
+
+	* gdbint.texinfo (Algorithms): Remove description of
+	TARGET_DISABLE_HW_WATCHPOINTS and TARGET_ENABLE_HW_WATCHPOINTS.
+
 2004-12-07  Jim Blandy  <jimb@redhat.com>
 
 	* gdb.texinfo (General Query Packets): Specify that thread ID's in
Index: doc/gdbint.texinfo
===================================================================
RCS file: /cvs/src/src/gdb/doc/gdbint.texinfo,v
retrieving revision 1.227
diff -u -p -r1.227 gdbint.texinfo
--- doc/gdbint.texinfo	4 Dec 2004 14:02:44 -0000	1.227
+++ doc/gdbint.texinfo	25 Dec 2004 10:16:01 -0000
@@ -440,20 +440,6 @@ whose size is @var{size}.  @value{GDBN} 
 fall-back, in case @code{TARGET_REGION_OK_FOR_HW_WATCHPOINT} is not
 defined.
 
-@findex TARGET_DISABLE_HW_WATCHPOINTS
-@item TARGET_DISABLE_HW_WATCHPOINTS (@var{pid})
-Disables watchpoints in the process identified by @var{pid}.  This is
-used, e.g., on HPPA-RISC machines running HP-UX, which provide
-operations to disable and enable the page-level memory protection that
-implements hardware watchpoints on that platform.
-
-@findex TARGET_ENABLE_HW_WATCHPOINTS
-@item TARGET_ENABLE_HW_WATCHPOINTS (@var{pid})
-Enables watchpoints in the process identified by @var{pid}.  This is
-used, e.g., on HPPA-RISC machines running HP-UX, which provide
-operations to disable and enable the page-level memory protection that
-implements hardware watchpoints on that platform.
-
 @cindex insert or remove hardware watchpoint
 @findex target_insert_watchpoint
 @findex target_remove_watchpoint



      reply	other threads:[~2004-12-25 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-25  1:58 Mark Kettenis
2004-12-25 10:03 ` Daniel Jacobowitz
2004-12-25 10:20 ` Eli Zaretskii
2004-12-25 12:36   ` Mark Kettenis [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=200412251020.iBPAK4Zn026042@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --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