From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: lgustavo@codesourcery.com
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] wp-replication: Fix test case loop
Date: Fri, 05 Jul 2013 17:10:00 -0000 [thread overview]
Message-ID: <87li5laq6w.fsf@br87z6lw.de.ibm.com> (raw)
In-Reply-To: <51D6F295.2070306@codesourcery.com> (Luis Machado's message of "Fri, 05 Jul 2013 13:21:41 -0300")
Luis Machado <lgustavo@codesourcery.com> writes:
> On 07/05/2013 01:10 PM, Andreas Arnez wrote:
>> When executing wp-replication.exp on S/390, the loop that counts the
>> number of available hardware watchpoints does not terminate properly,
>> because *all* "watch" commands yield "hardware watchpoints".
>>
>> Since the C source code is not prepared for more than NR_THREADS
>> hardware watchpoints anyhow, I suggest to add the appropriate exit
>> condition to the loop.
>
> That's an interesting behavior. Are the resources on s390 nearly
> unlimited for hardware watchpoints? Does it run out of hardware
> watchpoints eventually?
Well, that would be nice, wouldn't it? But sorry, no. On s390 the
hardware can generate so-called "PER storage alteration events" (PER =
program event recording) for a single contiguous memory area.
s390-nat.c chooses this area such that all desired watchpoints lie
within.
Thus what happens in wp-replication.exp is that the PER ending address
is increased with every loop iteration, but no hardware limit is
reached.
> If s390 doesn't run out of hardware watchpoints, i'd add a comment to
> the testcase explaining why we have this condition.
Sure. How about this then?
diff --git a/gdb/testsuite/gdb.threads/wp-replication.exp b/gdb/testsuite/gdb.threads/wp-replication.exp
index 8927a43..c6a13b9 100644
--- a/gdb/testsuite/gdb.threads/wp-replication.exp
+++ b/gdb/testsuite/gdb.threads/wp-replication.exp
@@ -81,6 +81,14 @@ while { $done == 0 } {
gdb_test_multiple "continue" "watchpoint created successfully" {
-re ".*Breakpoint 2, empty_cycle \\(\\).*$gdb_prompt $" {
incr hwatch_count
+
+ # Some targets (like S/390) behave as though supporting
+ # unlimited hardware watchpoints. In this case we just take a
+ # safe exit out of the loop.
+ if { $hwatch_count == $NR_THREADS } {
+ set done 1
+ break
+ }
}
-re ".*Could not insert hardware watchpoint.*$gdb_prompt $" {
set done 1
next prev parent reply other threads:[~2013-07-05 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 16:10 Andreas Arnez
2013-07-05 16:21 ` Luis Machado
2013-07-05 17:10 ` Andreas Arnez [this message]
2013-07-05 17:15 ` Luis Machado
2013-07-05 17:26 ` Andreas Arnez
2013-07-08 11:36 ` Ulrich Weigand
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=87li5laq6w.fsf@br87z6lw.de.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@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