Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Steven Johnson <sjohnson@neurizon.net>
Cc: gdb@sources.redhat.com
Subject: Re: Hardware Watchpoints
Date: Thu, 02 Jan 2003 15:16:00 -0000	[thread overview]
Message-ID: <3E1457CA.8070201@redhat.com> (raw)
In-Reply-To: <3E13EC74.8090802@neurizon.net>

> Does anyone know if hardware watchpoints are supposed to work with the GDB standard remote protocol.  They are documented in the protocol (Z packets), and there even appears to be code in remote.c, but there seems to be no way to activate them.  What am I missing?
> 
> Yes, i tried "set remote Z-packet on" which seems to do not much useful.
> 
> Im using a very late snapshot just prior GDB 5.3, I don't recall seeing anything about this in the GDB 5.3 release notes.

They, er, almost work.  I found a problem when testing them just before 
taking my summer break.  Need to get the patch integrated.

Briefly, GDB thinks that the target supports zero hardware breakpoints 
and there is no way (minus editing a file) of changing this.

Andrew



  reply	other threads:[~2003-01-02 15:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-02  7:48 Steven Johnson
2003-01-02 15:16 ` Andrew Cagney [this message]
     [not found] <np3dv6k64w.fsf@zwingli.cygnus.com>
     [not found] ` <19991019235249.917DC1B494@ocean.lucon.org>
1999-10-20  7:02   ` Hardware watchpoints Eli Zaretskii
     [not found]     ` <npvh82htxn.fsf@zwingli.cygnus.com>
     [not found]       ` <199910221200.IAA24556@mescaline.gnu.org>
     [not found]         ` <npn1tbnr5f.fsf@zwingli.cygnus.com>
1999-10-23  3:48           ` Eli Zaretskii
1999-10-24 12:22             ` Jim Blandy
1999-10-24 21:40               ` Jim Blandy
     [not found]               ` <npu2ndmzyh.fsf@zwingli.cygnus.com>
1999-10-27 13:07                 ` 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=3E1457CA.8070201@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=sjohnson@neurizon.net \
    /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