Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: adjust watchpoint testing
Date: Mon, 12 Jun 2006 16:40:00 -0000	[thread overview]
Message-ID: <448D98E7.7030806@codesourcery.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606130003580.6222@localhost.localdomain>

Wu Zhou wrote:
> Nathan,
> 
> I had similar concerns about these watchpoint tests with you.  However, 
> I'd like to propose a somewhat different solution.

> This target-dependent feature might incur confusion some where.  One 
> may have difficulty in knowing for sure what this case is trying to 
> test: s/w watchpoint, or h/w watchpoint, or both?  If there are errors 
> reported, what type of watchpoint trigger that?  To track into the root 
> cause, which code to look at? 
> 
> To clarify the situation, I propose to let recurse.exp based on totally on 
> software simulated watchpoint.  This can be done easily, by using "set 
> can-use-hardware-watchpoint 0".

Thanks for your comments. Over the weekend, I had a thought that the problem is 
the remote stub not telling gdb how many watchpoints it can support.  I think 
this is a thing for qPacketInfo to deal with, and I can talk to Dan about that.

nathan
-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::         CodeSourcery
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk


  reply	other threads:[~2006-06-12 16:40 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 [this message]
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

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=448D98E7.7030806@codesourcery.com \
    --to=nathan@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --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