From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: dje@google.com
Cc: Eli Zaretskii <eliz@gnu.org>, gdb-patches@sourceware.org
Subject: [patch] testsuite: Fix gdb.mi/* regression on RHEL-6 [Re: [RFA, doc RFA] New option set use-deprecated-index-sections]
Date: Wed, 25 Jul 2012 14:33:00 -0000 [thread overview]
Message-ID: <20120725143307.GA14336@host2.jankratochvil.net> (raw)
In-Reply-To: <20489.40174.602435.247343@ruffy2.mtv.corp.google.com>
On Fri, 20 Jul 2012 20:01:18 +0200, dje@google.com wrote:
> And I committed this to the 7.5 branch.
c3a09919048a2dcd937655d12acdb000d905841b is the first bad commit
commit c3a09919048a2dcd937655d12acdb000d905841b
Author: Doug Evans <dje@google.com>
Date: Fri Jul 20 17:38:00 2012 +0000
* NEWS: Document new options "set/show use-deprecated-index-sections",
[...]
-&"warning: Skipping deprecated .gdb_index section in /usr/lib/debug/lib64/ld-2.12.so.debug, pass --use-deprecated-index-sections to use them anyway\n"^M
+&"warning: Skipping deprecated .gdb_index section in /usr/lib/debug/lib64/ld-2.12.so.debug.\nDo \"set use-deprecated-index-sections on\" before the file is read\nto use the section anyway."^M
+&"\n"^M
(gdb) ^M
[...]
+ERROR: Unable to start target
This affects mostly any gdb.mi/*.exp testcase on RHEL-6.
I will check it in today; in two parts (the "\.gdb_index" regex fix is
unrelated).
Regards,
Jan
gdb/testsuite/
2012-07-25 Jan Kratochvil <jan.kratochvil@redhat.com>
Fix testsuite regression after --use-deprecated-index-sections removal.
* lib/mi-support.exp (gdbindex_warning_re): Update the expect string.
diff --git a/gdb/testsuite/lib/mi-support.exp b/gdb/testsuite/lib/mi-support.exp
index 401565d..5235944 100644
--- a/gdb/testsuite/lib/mi-support.exp
+++ b/gdb/testsuite/lib/mi-support.exp
@@ -31,7 +31,7 @@ global mi_inferior_tty_name
set MIFLAGS "-i=mi"
set thread_selected_re "=thread-selected,id=\"\[0-9\]+\"\r\n"
-set gdbindex_warning_re "&\"warning: Skipping \[^\r\n\]+ \.gdb_index section in \[^\"\]+\"\r\n"
+set gdbindex_warning_re "&\"warning: Skipping \[^\r\n\]+ \\.gdb_index section in \[^\r\n\]+\"\r\n(?:&\"\\\\n\"\r\n)?"
set library_loaded_re "=library-loaded\[^\n\]+\"\r\n(?:$gdbindex_warning_re)?"
set breakpoint_re "=(?:breakpoint-created|breakpoint-deleted)\[^\n\]+\"\r\n"
next prev parent reply other threads:[~2012-07-25 14:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 21:24 [RFA, doc RFA] New option set use-deprecated-index-sections dje
2012-07-17 21:43 ` Jan Kratochvil
2012-07-17 22:10 ` Doug Evans
2012-07-18 22:34 ` dje
2012-07-18 23:33 ` Jan Kratochvil
2012-07-18 23:53 ` dje
2012-07-19 7:03 ` Jan Kratochvil
2012-07-19 16:09 ` Eli Zaretskii
2012-07-19 16:28 ` Doug Evans
2012-07-19 16:45 ` Eli Zaretskii
2012-07-19 18:26 ` dje
2012-07-19 19:02 ` Eli Zaretskii
2012-07-20 18:01 ` dje
2012-07-25 14:33 ` Jan Kratochvil [this message]
2012-07-25 20:36 ` [commit+7.5] [patch] testsuite: Fix gdb.mi/* regression on RHEL-6 [Re: [RFA, doc RFA] New option set use-deprecated-index-sections] Jan Kratochvil
2012-07-27 21:39 ` [commit#2+7.5] " Jan Kratochvil
2012-07-19 16:11 ` [RFA, doc RFA] New option set use-deprecated-index-sections Eli Zaretskii
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=20120725143307.GA14336@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=eliz@gnu.org \
--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