From: Wu Zhou <woodzltc@cn.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: nathan@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: adjust watchpoint testing
Date: Wed, 14 Jun 2006 01:21:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0606140914210.2888@localhost.localdomain> (raw)
In-Reply-To: <ur71t3qux.fsf@gnu.org>
On Tue, 13 Jun 2006, Eli Zaretskii wrote:
> > Date: Tue, 13 Jun 2006 14:43:13 +0800 (CST)
> > From: Wu Zhou <woodzltc@cn.ibm.com>
> > cc: gdb-patches@sourceware.org
> >
> > Do you mean to hard-wire the number of the hw watchpoint the underlying target
> > support into these base board files, or just set the number to 1?
> >
> > I guess that we might need to work out a way to detect the number
> > automatically. Any thought?
>
> 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? If this
is still target dependent, we can overwrite it in the relevant tdep file.
For x86 case, maybe we can take them as only one watchpoint if they are
watching on the same address of same length?
My very initial idea though. Feel free to correct me if I am wrong.
Thanks
- Wu Zhou
next prev parent reply other threads:[~2006-06-14 1:21 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 [this message]
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=Pine.LNX.4.64.0606140914210.2888@localhost.localdomain \
--to=woodzltc@cn.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nathan@codesourcery.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