From: Eli Zaretskii <eliz@gnu.org>
To: luisgpm@linux.vnet.ibm.com
Cc: gdb@sourceware.org
Subject: Re: Assumptions on the number of hw watchpoints for some testcases
Date: Thu, 16 Sep 2010 15:42:00 -0000 [thread overview]
Message-ID: <E1OwGbl-0005IH-LW@fencepost.gnu.org> (raw)
In-Reply-To: <1284648970.2721.9.camel@gargoyle> (message from Luis Machado on Thu, 16 Sep 2010 11:56:10 -0300)
> From: Luis Machado <luisgpm@linux.vnet.ibm.com>
> Reply-To: luisgpm@linux.vnet.ibm.com
> Date: Thu, 16 Sep 2010 11:56:10 -0300
>
> I don't think GDB has a handy maint command to tell the testcases how
> many HW watches a target can use.
It doesn't, and it can't: the amount of HW watches available depends
on the alignment and size of the region being watched, and sometimes
on other factors.
The only way of dealing intelligently with these limitations is to
modify the test cases so that they dynamically detect when the HW
resources are exhausted and skip the affected tests. Not sure how
much labor that would need or whether it's worth the hassle.
prev parent reply other threads:[~2010-09-16 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 14:56 Luis Machado
2010-09-16 15:42 ` Eli Zaretskii [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=E1OwGbl-0005IH-LW@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=luisgpm@linux.vnet.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