Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Cc: Doug Evans <dje@google.com>
Subject: Re: [patch] break-interp.exp: handle /usr/sbin/prelink.bin
Date: Thu, 18 Mar 2010 07:43:00 -0000	[thread overview]
Message-ID: <201003180343.34183.vapier@gentoo.org> (raw)
In-Reply-To: <e394668d1003180026k4c44b4dldf19abcb8ac1a5ed@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1149 bytes --]

On Thursday 18 March 2010 03:26:20 Doug Evans wrote:
> On Thu, Mar 18, 2010 at 12:15 AM, Mike Frysinger <vapier@gentoo.org> wrote:
> > On Thursday 18 March 2010 02:15:07 Doug Evans wrote:
> >> -    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]} {
> > 
> > since the prelink filename shouldnt have a colon in it, should that be
> > used in the regex instead ?
> > /usr/sbin/prelink[^:]*:
> 
> Either is arguably wrong IMO.  Why can't the program have a colon or
> space in its name?

i said "shouldnt", not "cant".  i was thinking from a practical standpoint -- 
spaces are much more common than colons in filenames, and colons are generally 
discouraged from paths because they break fundamental things like colon-
separated variables such as $PATH.

> But I don't have a strong opinion on which one to actually use, or
> something else.

just a suggestion; i dont particularly care as i dont deal with prelink.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-03-18  7:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18  6:15 Doug Evans
2010-03-18  7:15 ` Mike Frysinger
2010-03-18  7:26   ` Doug Evans
2010-03-18  7:43     ` Mike Frysinger [this message]
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=201003180343.34183.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=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