From: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH v11 1/1] Extend struct r_debug to support multiple namespaces [BZ #15971]
Date: Thu, 16 Sep 2021 08:25:57 -0700 [thread overview]
Message-ID: <CAMe9rOo5ApPYTFbU20RSj7FMY1h_34mTGE3TyEvvufupZRhYig@mail.gmail.com> (raw)
In-Reply-To: <8735q4lfrl.fsf@oldenburg.str.redhat.com>
On Thu, Sep 16, 2021 at 8:08 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * H. J. Lu:
>
> > On Thu, Sep 16, 2021 at 1:34 AM Florian Weimer <fweimer@redhat.com> wrote:
> >> What about my question regarding access to _r_debug_extended for shared
> >> objects?
> >
> > As I mentioned in
> >
> > https://sourceware.org/pipermail/libc-alpha/2021-September/130888.html
> >
> > Linker generates DT_DEBUG only in the executable. dl_iterate_phdr can be
> > used to locate DT_DEBUG in the executable.
>
> I think some people want access _r_debug without any function calls, for
> example from signal handlers. But they can still do that. I guess we
> can reconsider what to do if there are similar requests for the
> extension structure.
We can certainly do that when there is a need in the future.
--
H.J.
prev parent reply other threads:[~2021-09-16 15:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 16:56 [PATCH v11 0/1] Extend struct r_debug to support multiple namespaces H.J. Lu via Libc-alpha
2021-09-14 16:56 ` [PATCH v11 1/1] Extend struct r_debug to support multiple namespaces [BZ #15971] H.J. Lu via Libc-alpha
2021-09-16 8:34 ` Florian Weimer via Libc-alpha
2021-09-16 14:17 ` H.J. Lu via Libc-alpha
2021-09-16 15:08 ` Florian Weimer via Libc-alpha
2021-09-16 15:25 ` H.J. Lu via Libc-alpha [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMe9rOo5ApPYTFbU20RSj7FMY1h_34mTGE3TyEvvufupZRhYig@mail.gmail.com \
--to=libc-alpha@sourceware.org \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.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).