public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: "Paul E. Murphy" <murphyp@linux.ibm.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH v2] nptl_db: disable DT_RELR on libthread_db.so
Date: Tue, 7 Jun 2022 18:56:17 -0400	[thread overview]
Message-ID: <207e5e80-3b82-5ebd-9a7a-f2b8739f315f@redhat.com> (raw)
In-Reply-To: <20220603145037.126797-1-murphyp@linux.ibm.com>

On 6/3/22 10:50, Paul E. Murphy via Libc-alpha wrote:
> Continued from
> 
> https://sourceware.org/pipermail/libc-alpha/2022-June/139357.html

LGTM.

Reviewed-by: Carlos O'Donell <carlos@redhat.com>

> ---8<---
> 
> Some nptl tests inadvertently use the host's gdb to verify
> libthread_db.so, which is loaded with the host's runtime.  This causes
> a couple of test failures when the host glibc does not support DT_RELR.
> 
> The not correct, but simple, workaround is to build without DT_RELR
> as this library is otherwise likely to load on glibc 2.17 and newer
> today.
> 
> This allows tst-pthread-gdb-attach{,-static} to continue working
> when testing on a gdb loaded with an older glibc.

OK.

> 
> This avoids a failure in tst-pthread-gdb-attach similar to:
> 
>   Trying host libthread_db library: .../build/glibc/nptl_db/libthread_db.so.1.
>   dlopen failed: /lib64/libc.so.6: version `GLIBC_ABI_DT_RELR' not found (required by .../build/glibc/nptl_db/libthread_db.so.1).

OK.

> ---
>  nptl_db/Makefile | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/nptl_db/Makefile b/nptl_db/Makefile
> index ed923a41e5..2360e53c88 100644
> --- a/nptl_db/Makefile
> +++ b/nptl_db/Makefile
> @@ -49,6 +49,12 @@ libthread_db-inhibit-o = $(filter-out .os,$(object-suffixes))
>  # The ps_* callback functions are not defined.
>  libthread_db.so-no-z-defs = yes
>  
> +# This is a hack.  This is not the correct solution.  When this glibc
> +# is tested, the gdb used could be loaded by the host glibc, which
> +# may not support DT_RELR, and report a failure instead of unsupported.
> +# For now, build this without DT_RELR support to avoid this situation.

OK. *Great* comment :-)

> +libthread_db.so-no-dt-relr = yes
> +
>  tests-special += $(objpfx)db-symbols.out
>  
>  include ../Rules


-- 
Cheers,
Carlos.


  reply	other threads:[~2022-06-07 22:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 14:50 Paul E. Murphy
2022-06-07 22:56 ` Carlos O'Donell [this message]
2022-06-08 18:58   ` Paul E Murphy

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=207e5e80-3b82-5ebd-9a7a-f2b8739f315f@redhat.com \
    --to=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=murphyp@linux.ibm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).