From: Daniel Jacobowitz <drow@false.org>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: threaded watchpoint test
Date: Tue, 27 Jul 2004 23:27:00 -0000 [thread overview]
Message-ID: <20040727232634.GA32379@nevyn.them.org> (raw)
In-Reply-To: <4106E42F.3010304@redhat.com>
On Tue, Jul 27, 2004 at 07:24:31PM -0400, Jeff Johnston wrote:
> Daniel Jacobowitz wrote:
> >On Tue, Jul 27, 2004 at 02:56:19PM -0400, Jeff Johnston wrote:
> >
> >>+# Watch values that will be modified by distinct threads.
> >>+gdb_test "watch args\[0\]" "Hardware watchpoint 2: args\\\[0\\\]"
> >>+gdb_test "watch args\[1\]" "Hardware watchpoint 3: args\\\[1\\\]"
> >
> >
> >What about platforms without hardware watchpoints? This test will
> >generate a lot of FAILs in that case.
> >
>
> I mentioned this both in my original posting and in the test case itself.
> There is a test for hardware watchpoints and if there are no hardware
> watchpoints, it returns 0.
>
> # This test verifies that a watchpoint is detected in the proper thread
> # so the test is only meaningful on a system with hardware watchpoints.
> if [target_info exists gdb,no_hardware_watchpoints] {
> return 0;
> }
OK. Unfortunately I don't think this test is conclusive; unix.exp will
always claim to have hardware watchpoints, and on many systems it does
not (for instance powerpc-linux). If that turns out to be true we can
introduce gdb_has_hardware_watchpoints or something along those lines.
--
Daniel Jacobowitz
next prev parent reply other threads:[~2004-07-27 23:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 18:56 Jeff Johnston
2004-07-27 22:56 ` Michael Chastain
2004-07-27 23:02 ` Daniel Jacobowitz
2004-07-27 23:24 ` Jeff Johnston
2004-07-27 23:27 ` Daniel Jacobowitz [this message]
2004-07-27 23:41 ` Jeff Johnston
2004-07-28 0:13 ` Michael Chastain
2004-07-29 15:26 ` Daniel Jacobowitz
2004-07-29 23:39 ` Mark Kettenis
2004-07-30 0:55 ` Michael Chastain
2004-07-30 22:33 ` Andrew Cagney
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=20040727232634.GA32379@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@redhat.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