Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Handle absent "/usr/sbin/" in prelink error output.
Date: Tue, 16 Nov 2010 22:36:00 -0000	[thread overview]
Message-ID: <20101116223618.GB2703@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <AANLkTimxE8a7rBrCwPGWjm_cCQzvkLZi5zZfXV_jaiJc@mail.gmail.com>

On Tue, 16 Nov 2010 22:23:35 +0100, Doug Evans wrote:
> On Tue, Nov 16, 2010 at 1:11 PM, Doug Evans <dje@google.com> wrote:
> > --- 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 {
> >
> 
> Well, this shouldn't have caused a regression, but break-interp.exp
> breaks badly with it.
> So there's a deeper bug here.  Blech.

I do not have any of the problems reproducible on Fedora 14 x86_64 (which is
understandable as the testcases were written on this platform).  I do not see
why your proposed patch should break anything.

But speaking specifically about gdb.base/attach-pie-misread.exp I am free to
drop it whole.  The problem is very difficult to reliably reproduce, various
memory alignments must match to make the former problem reproducible.


Thanks,
Jan


  reply	other threads:[~2010-11-16 22:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16 21:11 Doug Evans
2010-11-16 21:23 ` Doug Evans
2010-11-16 22:36   ` Jan Kratochvil [this message]
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=20101116223618.GB2703@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --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