From: Andreas Schwab <schwab@linux-m68k.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Luis Machado <luisgpm@linux.vnet.ibm.com>,
gdb-patches@sourceware.org,
Pedro Alves <pedro@codesourcery.com>,
Edjunior Barbosa Machado <emachado@linux.vnet.ibm.com>
Subject: Re: [PATCH] testcases: Fix assorted problems related to powerpc
Date: Sat, 27 Nov 2010 22:09:00 -0000 [thread overview]
Message-ID: <m239qmzafc.fsf@igel.home> (raw)
In-Reply-To: <20101109044704.GA24214@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Tue, 9 Nov 2010 05:47:05 +0100")
Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> --- src/gdb/testsuite/gdb.base/watchpoint.exp 2010/09/04 15:30:09 1.31
> +++ src/gdb/testsuite/gdb.base/watchpoint.exp 2010/11/09 04:44:17 1.32
> @@ -683,7 +683,13 @@
> "$watchpoint_msg \[0-9\]+: \\*\\(int \\*\\) 0"
> delete_breakpoints
>
> - gdb_test "watch *global_ptr" "$watchpoint_msg \[0-9\]+: \\*global_ptr"
> + # This step requires two HW watchpoints. Since PPC Server only has
> + # a single one, it will use a SW watchpoint in this case.
> + if [istarget powerpc64-*] {
Why powerpc64?
> + set watchpoint_msg "Watchpoint"
> + }
> +
> + gdb_test "watch *global_ptr" "$watchpoint_msg \[0-9\]+: \\\*global_ptr"
That has an extra backslash.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-11-27 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 16:32 Luis Machado
2010-11-09 4:47 ` Jan Kratochvil
2010-11-09 5:46 ` Doug Evans
2010-11-27 22:09 ` Andreas Schwab [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-09-28 21:47 Luis Machado
2010-09-28 21:48 ` Pedro Alves
2010-09-29 15:04 ` Luis 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=m239qmzafc.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=emachado@linux.vnet.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=luisgpm@linux.vnet.ibm.com \
--cc=pedro@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).