Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: dje@google.com (Doug Evans)
To: gdb-patches@sourceware.org
Subject: [patch] break-interp.exp: handle /usr/sbin/prelink.bin
Date: Thu, 18 Mar 2010 06:15:00 -0000	[thread overview]
Message-ID: <20100318061507.102F084414@ruffy.mtv.corp.google.com> (raw)

Hi.

On one system I use /usr/sbin/prelink is a wrapper script around
/usr/sbin/prelink.bin.
This breaks break-interp.exp.

I will check in the following patch in a day if there are no objections.

2010-03-17  Doug Evans  <dje@google.com>

	* gdb.base/break-interp.exp (prelinkNO): Handle prelink binaries
	named /usr/sbin/prelink<foo>.

Index: testsuite/gdb.base/break-interp.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/break-interp.exp,v
retrieving revision 1.7
diff -u -p -r1.7 break-interp.exp
--- testsuite/gdb.base/break-interp.exp	11 Mar 2010 22:07:03 -0000	1.7
+++ testsuite/gdb.base/break-interp.exp	18 Mar 2010 06:11:38 -0000
@@ -141,7 +141,7 @@ proc prelinkNO {arg {name {}}} {
 	set output [lindex $run 1]
     }
     # Last line does miss the trailing \n.
-    if {$result == 1 && [regexp {^(/usr/sbin/prelink: [^ ]* does not have .gnu.prelink_undo section\n?)*$} $output]} {
+    if {$result == 1 && [regexp {^(/usr/sbin/prelink[^ ]*: [^ ]* does not have .gnu.prelink_undo section\n?)*$} $output]} {
 	pass $test
 	return 1
     } else {


             reply	other threads:[~2010-03-18  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18  6:15 Doug Evans [this message]
2010-03-18  7:15 ` Mike Frysinger
2010-03-18  7:26   ` Doug Evans
2010-03-18  7:43     ` Mike Frysinger
2010-03-18 13:59 ` Joel Brobecker

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=20100318061507.102F084414@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