Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: "Garrod, David" <dgarrod@enterasys.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: How do I set a hard watchpoint with gdbserver?
Date: Fri, 18 Sep 2009 00:32:00 -0000	[thread overview]
Message-ID: <4AB2D4ED.3070804@vmware.com> (raw)
In-Reply-To: <B095CECB368F0946BF407966E809C354061310B817@MAEXCEVS2.ets.enterasys.com>

Garrod, David wrote:
> I'm using a configuration of gdb and gdbserver. Both the host (gdb) and the target (gdbserver) are running on Linux on Intel 486 or 586 sytstems.
> 
> I would like to be able to issue the command:
> 
> watch *(int*)addr
> 
> and have it set a "hard" watchpoint on the target. What seems to happening is that a soft watchpoint is being set since when I continue everything seems to hang until I ^C and remove the watchpoint.
> 
> How do I persuade gdbserver to set a hard watchpoint rather than a soft watchpoint? Breakpoints work fine in that they get set hard.
> 
> Thanks,
> 
> Dave Garrod
> 

When you give the "watch" command, does gdb respond by saying
that it has set a "hardware watchpoint", or just a "watchpoint"?

If it doesn't say "hardware watchpoint", then probably hardware
watchpoints are disabled.  You enable them like this:

	(gdb) set can-use-hw-watchpoints 1

If that doesn't solve your problem, then do this --

	(gdb) set debug remote 1

right before you say "continue".  You should see a number of
messages, one of which should look like "Z2," followed by the
address that you're trying to watch.

If you don't see that, then gdb is still not trying to send
a hardware watchpoint to gdbserver.  At that point, we would
need to ask what version of gdb, what version of gdbserver, etc.


  reply	other threads:[~2009-09-18  0:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 23:31 Garrod, David
2009-09-18  0:32 ` Michael Snyder [this message]
2009-09-18  9:45   ` Pedro Alves

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=4AB2D4ED.3070804@vmware.com \
    --to=msnyder@vmware.com \
    --cc=dgarrod@enterasys.com \
    --cc=gdb@sourceware.org \
    /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