Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: nathan@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: adjust watchpoint testing
Date: Wed, 14 Jun 2006 03:32:00 -0000	[thread overview]
Message-ID: <u7j3k4dlo.fsf@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0606140914210.2888@localhost.localdomain> (message 	from Wu Zhou on Wed, 14 Jun 2006 09:21:52 +0800 (CST))

> Date: Wed, 14 Jun 2006 09:21:52 +0800 (CST)
> From: Wu Zhou <woodzltc@cn.ibm.com>
> cc: nathan@codesourcery.com, gdb-patches@sourceware.org
> 
> > I don't think there's any practical way to detect the number of
> > supported watchpoints.  It depends on the particulars of the watched
> > regions, and different targets have different peculiarities.  For
> > example, x86 can set an unlimited number of watchpoints provided that
> > they watch the same address and length.
> 
> What about adding a gdbarch specific member function to do this?

What would that function do?  I thought I explained that the question
``how many watchpoints can the target give us'' has no meaningful
answer, unless you also supply the specific mix of addresses and sizes
of the regions you wish to watch.


  parent reply	other threads:[~2006-06-14  3:32 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 [this message]
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=u7j3k4dlo.fsf@gnu.org \
    --to=eliz@gnu.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