From: Florian Weimer <fweimer@redhat.com>
To: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Cc: "Daniel Walker (danielwa)" <danielwa@cisco.com>,
Carlos O'Donell <carlos@redhat.com>,
Pedro Alves <palves@redhat.com>,
"Jeremy Stenglein (jstengle)" <jstengle@cisco.com>,
"xe-linux-external(mailer list)" <xe-linux-external@cisco.com>
Subject: Re: [RFC PATCH 0/3] implement dlmopen hooks for gdb
Date: Tue, 22 Sep 2020 19:06:25 +0200 [thread overview]
Message-ID: <87h7rpwxke.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <3ff42e45-b394-bf50-38c4-93baecc71497@redhat.com> (Carlos O'Donell via Libc-alpha's message of "Thu, 23 Jul 2020 17:20:23 -0400")
* Carlos O'Donell via Libc-alpha:
> Your next step would be to export the symbol via Versions at the current
> symbol node GLIBC_2.32 (soon to be GLIBC_2.33).
Can we create a new GLIBC_DEBUG symbol versions for symbols which are
not intended to be used for run-time linking?
The idea is that consumers will have deal with the absence of these
symbols anyway, so we just need one symbol version that does not depend
on the glibc version for this. Dependency management considerations
(that apply to symbols with run-time linking) do not come into play here.
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-09-22 17:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 19:32 Daniel Walker
2020-06-26 21:17 ` Carlos O'Donell
2020-07-23 18:40 ` Daniel Walker (danielwa)
2020-07-23 21:20 ` Carlos O'Donell
2020-09-16 16:18 ` Daniel Walker (danielwa)
2020-09-17 12:52 ` Carlos O'Donell
2020-09-17 12:59 ` Florian Weimer
2020-09-17 13:53 ` Carlos O'Donell
2020-09-18 15:35 ` Daniel Walker (danielwa)
2020-09-18 15:40 ` Florian Weimer
2020-09-21 20:02 ` Daniel Walker (danielwa)
2021-07-28 18:33 ` Daniel Walker
2021-07-28 18:48 ` H.J. Lu
2020-09-17 13:52 ` Carlos O'Donell
2020-09-22 17:06 ` Florian Weimer [this message]
2020-09-22 17:28 ` Carlos O'Donell
2020-09-22 17:37 ` Florian Weimer
2020-09-22 17:59 ` Carlos O'Donell
2020-09-22 18:04 ` Florian Weimer
2020-09-22 18:41 ` Carlos O'Donell
2020-09-22 18:44 ` Florian Weimer
2020-09-22 18:46 ` Carlos O'Donell
2020-09-22 18:17 ` Andreas Schwab
2020-09-22 19:13 ` Carlos O'Donell
2020-06-26 21:30 ` Florian Weimer
2020-06-27 1:10 ` Daniel Walker (danielwa)
2020-07-02 13:54 ` Conan Huang (conhuang)
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=87h7rpwxke.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=carlos@redhat.com \
--cc=danielwa@cisco.com \
--cc=jstengle@cisco.com \
--cc=libc-alpha@sourceware.org \
--cc=palves@redhat.com \
--cc=xe-linux-external@cisco.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).