public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Fangrui Song <maskray@google.com>
Cc: Florian Weimer <fweimer@redhat.com>,
	 "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] Enable DT_RELR in glibc shared libraries and PIEs automatically
Date: Fri, 20 May 2022 18:51:15 -0700	[thread overview]
Message-ID: <CAMe9rOo1EDvVn4QE2POnBAskAPH8cnALiM8VGj2ApX3NQ1YB8w@mail.gmail.com> (raw)
In-Reply-To: <20220520225009.mfkzwang4spyznee@google.com>

On Fri, May 20, 2022 at 3:50 PM Fangrui Song via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> On 2022-05-16, Florian Weimer via Libc-alpha wrote:
> >* H. J. Lu via Libc-alpha:
> >
> >> Enable DT_RELR in glibc shared libraries and position independent
> >> executables (PIE) automatically if linker supports -z
> >> pack-relative-relocs.
> >
> >Thanks for updating the commit subject.
> >
> >Reviewed-by: Florian Weimer <fweimer@redhat.com>
> >
> >Florian
> >
>
> Thanks for the patch.
>
> Question: does gdb need DT_RELR support to debug such a shared object?
> `gdb elf/ld.so` will report
>
>    BFD: path/to/elf/ld.so: unknown type [0x13] section `.relr.dyn'
>
> but I do not know whether any functionality is affected in the absence
> of SHT_RELR support.

You need GDB 12 or 11.2 for  DT_RELR.

-- 
H.J.

      reply	other threads:[~2022-05-21  1:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-16 13:17 H.J. Lu
2022-05-16 13:44 ` Florian Weimer
2022-05-20 22:50   ` Fangrui Song
2022-05-21  1:51     ` H.J. Lu [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=CAMe9rOo1EDvVn4QE2POnBAskAPH8cnALiM8VGj2ApX3NQ1YB8w@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=maskray@google.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).