Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Luis Machado <lgustavo@codesourcery.com>
Cc: Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>,
	 gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix wp-replication.exp for targets that provide only 1 hw watchpoint
Date: Fri, 24 May 2013 08:11:00 -0000	[thread overview]
Message-ID: <519F2084.3090104@codesourcery.com> (raw)
In-Reply-To: <519F17A0.2040607@codesourcery.com>

On 05/24/2013 09:32 AM, Luis Machado wrote:
>> current wp-replication.exp testcase counts 2 hw watchpoints even when
>> the target
>> provides only 1 hw watch, resulting in several unexpected errors.
>> Successfully
>> tested on x86 (with 4 hw watchpoints available) and ppc64 server (with
>> 1 hw
>> watch), this patch intends to fix this issue. Ok?
>
> I wonder why it is counting one more watchpoint. Is it not matching the
> output in the exit block here?

I think i see the problem here. "break" only really jumps out of the 
gdb_test_multiple block instead of breaking, so this would be a problem 
for all targets that do "on the fly" accounting of resources, thus not 
taking the error check leg of the test.

Maybe replace both "break" with "continue". We really just want to reach 
the top of the while loop here to either jump out of the loop or 
continue with it.

What do you think?

Luis


  reply	other threads:[~2013-05-24  8:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24  3:19 Edjunior Barbosa Machado
2013-05-24  3:26 ` Edjunior Barbosa Machado
2013-05-24  7:32   ` Luis Machado
2013-05-24  8:11     ` Luis Machado [this message]
2013-05-24 14:03       ` Edjunior Barbosa Machado

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=519F2084.3090104@codesourcery.com \
    --to=lgustavo@codesourcery.com \
    --cc=emachado@linux.vnet.ibm.com \
    --cc=gdb-patches@sourceware.org \
    /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