Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: Nathan Sidwell <nathan@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: adjust watchpoint testing
Date: Tue, 13 Jun 2006 13:11:00 -0000	[thread overview]
Message-ID: <20060613131109.GB4737@nevyn.them.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0606131405060.2766@localhost.localdomain>

On Tue, Jun 13, 2006 at 02:12:30PM +0800, Wu Zhou wrote:
> I am now using a test and trial method.  If rwatch command reports that 
> this type of hw watchpoint is not supported, then I will assume this 
> target don't support hardware watchpoint; if it replys with a message 
> "Hardware read watchpoint...", then I assume it is supported.  But I 
> don't figure out how to get precisely how many hw watchpoints the 
> target support?  How did you make that?  Can you share your idea with 
> me?  Thanks a lot!

This is the right way to do it in the testsuite.  Nathan's suggestion
just makes it easier for GDB to give the right responses when doing
this on a remote target.

-- 
Daniel Jacobowitz
CodeSourcery


      parent reply	other threads:[~2006-06-13 13:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 20:58 Nathan Sidwell
2006-06-12 16:30 ` Wu Zhou
2006-06-12 16:40   ` Nathan Sidwell
2006-06-13  6:12     ` Wu Zhou
2006-06-13  6:23       ` Nathan Sidwell
2006-06-13  6:43         ` Wu Zhou
2006-06-13  7:07           ` Nathan Sidwell
2006-06-13 10:20             ` Wu Zhou
2006-06-13 10:25               ` Nathan Sidwell
2006-06-13 17:30           ` Eli Zaretskii
2006-06-14  1:21             ` Wu Zhou
2006-06-14  2:52               ` Daniel Jacobowitz
2006-06-14  3:32               ` Eli Zaretskii
2006-06-13 13:11       ` Daniel Jacobowitz [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=20060613131109.GB4737@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nathan@codesourcery.com \
    --cc=woodzltc@cn.ibm.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