From: Markus Deuling <deuling@de.ibm.com>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb-patches@sourceware.org, drow@false.org
Subject: Re: [RFA]: gdb/testsuite/gdb.arch/altivec-regs.exp Broken testcase
Date: Thu, 18 Jan 2007 09:15:00 -0000 [thread overview]
Message-ID: <45AF3A99.3020105@de.ibm.com> (raw)
In-Reply-To: <200701172148.l0HLmPGJ021678@brahms.sibelius.xs4all.nl>
Hi,
Mark Kettenis schrieb:
>> Date: Wed, 17 Jan 2007 07:36:59 +0100
>> From: Markus Deuling <deuling@de.ibm.com>
>>
>> But I think inserting
>> +set endianness ""
>> is a good idea. Then the testcase would have FAILed instead of abort
>> with an error.
>
> I agree. Feel free to commit that bit.
>
> Mark
>
this is the patch without the new branch. Could you please commit it?
Thank you very much.
ChangeLog:
*gdb.arch/altivec-regs.exp: Initialise variable
endianness in every case.
=============================================================
--- src/gdb/testsuite/gdb.arch/altivec-regs.exp 2007-01-17 06:57:45.000000000 +0100
+++ dev/gdb/testsuite/gdb.arch/altivec-regs.exp 2007-01-18 10:12:24.000000000 +0100
@@ -89,6 +89,7 @@
gdb_test "next" "" ""
send_gdb "show endian\n"
+set endianness ""
gdb_expect {
-re "(The target endianness is set automatically .currently )(big|little)( endian.*)$gdb_prompt $" {
pass "endianness"
Regards,
Markus
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
next prev parent reply other threads:[~2007-01-18 9:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 6:48 Markus Deuling
2007-01-16 21:28 ` Mark Kettenis
2007-01-17 4:50 ` Markus Deuling
2007-01-17 5:59 ` Daniel Jacobowitz
2007-01-17 6:37 ` Markus Deuling
2007-01-17 8:31 ` Markus Deuling
2007-01-17 21:48 ` Mark Kettenis
2007-01-18 9:15 ` Markus Deuling [this message]
2007-01-20 18:32 ` Daniel Jacobowitz
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=45AF3A99.3020105@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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