Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Steve Ellcey <sellcey@cavium.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: prelink -u on aarch64 question
Date: Wed, 26 Jul 2017 20:05:00 -0000	[thread overview]
Message-ID: <1501099506.28549.109.camel@cavium.com> (raw)
In-Reply-To: <20170726194415.GA12866@host1.jankratochvil.net>

On Wed, 2017-07-26 at 21:44 +0200, Jan Kratochvil wrote:
> On Wed, 26 Jul 2017 19:37:46 +0200, Steve Ellcey wrote:
> > 
> > I was wondering if anyone could tell me anything about prelink on
> > aarch64?
> prelink probably is not supported on aarch64 at all, I have not checked.
> 
> But even on x86* prelink has been discontinued - on its "core" distro:
> 	Don't enable prelink by default in Fedora
> 	https://pagure.io/fesco/issue/1183
> 
> I think at least the prelink testfile gdb.base/break-interp.exp could be even
> disabled by default nowadays (saying that as author of the testfile) as even
> when it PASSes it is very slow given the huge number of combinations
> it does
> test.
> 
> 
> Jan

I don't see any indication that gdb.base/break-interp.exp is disabled
by default, though it is part of the slow_tests list so if you don't
run slow tests then it would not show up.  I actually have four tests
that fail due to prelink:

gdb.base/attach-pie-misread.exp
gdb.base/break-interp.exp
gdb.base/prelink.exp
gdb.threads/dlopen-libpthread.exp

It also seems to get used in:

gdb.server/connect-stopped-target.exp
gdb.server/solib-list.exp
gdb.base/nostdlib.exp
gdb.base/relativedebug.exp
gdb.base/solib-overlap.exp

Although those did not show up in my FAIL list.

Should we just remove all the gdb tests that use prelink?

Steve Ellcey
sellcey@cavium.com


      reply	other threads:[~2017-07-26 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-26 17:37 Steve Ellcey
2017-07-26 19:44 ` Jan Kratochvil
2017-07-26 20:05   ` Steve Ellcey [this message]

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=1501099506.28549.109.camel@cavium.com \
    --to=sellcey@cavium.com \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /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