From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org
Subject: [patch] Handle absent "/usr/sbin/" in prelink error output.
Date: Tue, 16 Nov 2010 21:11:00 -0000 [thread overview]
Message-ID: <20101116211114.EAB2A2460AB@ruffy.mtv.corp.google.com> (raw)
Hi.
I'm seeing the following output from prelink:
prelink: /g3/gnu/sourceware/pretty-printers/build/obj64/gdb/testsuite/gdb.base/attach-pie-misread.d/ld-linux-x86-64.so.2 does not have .gnu.prelink_undo section
which causes attach-pie-misread.exp to fail with:
FAIL: gdb.base/attach-pie-misread.exp: unprelink ld-linux-x86-64.so.2 pre-unprelink
I will check in the following patch in two days if there are no objections.
2010-11-16 Doug Evans <dje@google.com>
* lib/prelink-support.exp (prelink_no): Handle absent "/usr/sbin/"
in prelink error output.
Index: lib/prelink-support.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/lib/prelink-support.exp,v
retrieving revision 1.3
diff -u -p -r1.3 prelink-support.exp
--- lib/prelink-support.exp 12 Oct 2010 18:12:49 -0000 1.3
+++ lib/prelink-support.exp 16 Nov 2010 21:06:58 -0000
@@ -221,7 +221,7 @@ proc prelink_no {arg {name {}}} {
}
# Last line does miss the trailing \n. There can be multiple such messages
# as ARG may list multiple files.
- if {$result == 1 && [regexp {^(/usr/sbin/prelink[^\r\n]*: [^ ]* does not have .gnu.prelink_undo section\n?)*$} $output]} {
+ if {$result == 1 && [regexp {^((/usr/sbin/)?prelink[^\r\n]*: [^ ]* does not have .gnu.prelink_undo section\n?)*$} $output]} {
pass $test
return 1
} else {
next reply other threads:[~2010-11-16 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 21:11 Doug Evans [this message]
2010-11-16 21:23 ` Doug Evans
2010-11-16 22:36 ` Jan Kratochvil
2010-11-16 22:44 ` Doug Evans
2010-11-16 22:58 ` Jan Kratochvil
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=20101116211114.EAB2A2460AB@ruffy.mtv.corp.google.com \
--to=dje@google.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