From: Thiago Jung Bauermann <bauerman@br.ibm.com>
To: gdb-patches <gdb-patches@sourceware.org>
Subject: [PATCH] changed output in altivec-regs.exp
Date: Mon, 05 Mar 2007 20:18:00 -0000 [thread overview]
Message-ID: <1173125923.21352.34.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 356 bytes --]
Hi,
This makes the test script expect the new output of the "show endian"
command, which for PPC architecture changed sometime between GDB 6.5 and
GDB 6.6.
2007-03-05 Thiago Jung Bauermann <bauerman@br.ibm.com>
* gdb.arch/altivec-regs.exp: Match new "show endian" output.
--
[]'s
Thiago Jung Bauermann
Software Engineer
IBM Linux Technology Center
[-- Attachment #2: altivec-regs.diff --]
[-- Type: text/x-patch, Size: 677 bytes --]
Index: gdb.arch/altivec-regs.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.arch/altivec-regs.exp,v
retrieving revision 1.13
diff -u -r1.13 altivec-regs.exp
--- gdb.arch/altivec-regs.exp 19 Jan 2007 11:14:52 -0000 1.13
+++ gdb.arch/altivec-regs.exp 5 Mar 2007 18:17:55 -0000
@@ -91,7 +91,7 @@
send_gdb "show endian\n"
set endianness ""
gdb_expect {
- -re "(The target endianness is set automatically .currently )(big|little)( endian.*)$gdb_prompt $" {
+ -re "(The target is assumed to be )(big|little)( endian.*)$gdb_prompt $" {
pass "endianness"
set endianness $expect_out(2,string)
}
next reply other threads:[~2007-03-05 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 20:18 Thiago Jung Bauermann [this message]
2007-03-05 20:30 ` Daniel Jacobowitz
2007-03-06 18:47 ` Thiago Jung Bauermann
2007-03-05 22:05 ` Andreas Schwab
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=1173125923.21352.34.camel@localhost.localdomain \
--to=bauerman@br.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