From: Markus Deuling <deuling@de.ibm.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Daniel Jacobowitz <drow@false.org>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [patch] Remove comments from user_code in gdb_test_multiple
Date: Fri, 28 Mar 2008 09:16:00 -0000 [thread overview]
Message-ID: <47ECB74F.9020501@de.ibm.com> (raw)
In-Reply-To: <200803271751.m2RHpwJj005352@d12av02.megacenter.de.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
Ulrich Weigand schrieb:
> Daniel Jacobowitz wrote:
>
>> That becomes:
>>
>>> -re "SPU Outbound Mailbox.*0x.*SPU Outbound Interrupt Mailbox.*0x.*$gdb_prompt $" {
>>> # Older kernels had a bug that caused them to return arbitrary values when
>>> # attempting to read from an empty mailbox via spufs.
>>> xfail "$msg"
>>> }
>
> I agree that this seems the best solution -- I wasn't trying to
> do anything special, I just didn't think of the where exactly
> to place the comment ...
Here is a new version. Ok ?
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
[-- Attachment #2: fix-spu-mailbox --]
[-- Type: text/plain, Size: 1050 bytes --]
diff -urpN src/gdb/testsuite/gdb.arch/spu-info.exp dev/gdb/testsuite/gdb.arch/spu-info.exp
--- src/gdb/testsuite/gdb.arch/spu-info.exp 2008-01-01 23:53:18.000000000 +0100
+++ dev/gdb/testsuite/gdb.arch/spu-info.exp 2008-03-28 09:53:47.000000000 +0100
@@ -200,9 +200,17 @@ gdb_test "finish" "" "finish"
# Mailbox Test
# 'info spu mailbox' should be empty.
c_to "Marker Mbox"
-gdb_test "info spu mailbox" \
- "SPU Outbound Mailbox.*0xc0000000.*SPU Outbound Interrupt Mailbox.*0xc0000000.*" \
- "info spu mailbox"
+set msg "info spu mailbox"
+gdb_test_multiple "info spu mailbox" $msg {
+ -re "SPU Outbound Mailbox.*0x00000000.*SPU Outbound Interrupt Mailbox.*0x00000000.*$gdb_prompt $" {
+ pass $msg
+ }
+ -re "SPU Outbound Mailbox.*0x.*SPU Outbound Interrupt Mailbox.*0x.*$gdb_prompt $" {
+ # Older kernels had a bug that caused them to return arbitrary values
+ # when attempting to read from an empty mailbox via spufs.
+ xfail $msg
+ }
+}
# 'info spu mailbox' should now contain data.
c_to "Marker MboxEnd"
next prev parent reply other threads:[~2008-03-28 9:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 15:24 Markus Deuling
2008-03-27 15:32 ` Daniel Jacobowitz
2008-03-27 15:47 ` Markus Deuling
2008-03-27 15:55 ` Daniel Jacobowitz
2008-03-27 17:52 ` Ulrich Weigand
2008-03-28 9:16 ` Markus Deuling [this message]
2008-03-28 16:00 ` Ulrich Weigand
2008-03-31 8:42 ` Markus Deuling
2008-03-27 16:35 ` Andrew STUBBS
2008-03-28 8:57 ` Markus Deuling
2008-03-28 9:40 ` Andrew STUBBS
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=47ECB74F.9020501@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.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