From: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
To: Daniel Walker <danielwa@cisco.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>,
Pedro Alves <palves@redhat.com>,
Conan C Huang <conhuang@cisco.com>,
"Metzger, Markus T" <markus.t.metzger@intel.com>,
Florian Weimer <fw@deneb.enyo.de>,
Jeremy Stenglein <jstengle@cisco.com>,
"xe-linux-external\(mailer list\)" <xe-linux-external@cisco.com>
Subject: RFC: Add DT_GNU_DEBUG
Date: Sun, 1 Aug 2021 21:24:36 -0700 [thread overview]
Message-ID: <CAMe9rOpyFWJeX1db_6iNqQBAOzqywy4Nw2QhLjE=mWH_bZykTg@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOoVCWg+9c1nq9+HeA9uBkb8Hdu-kamczBHjaF+wciq5fw@mail.gmail.com>
On Wed, Jul 28, 2021 at 1:04 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> > Do you want to drive this, or should I ? It looks like you know the people
> > involved better than I do.
> >
>
> https://groups.google.com/g/generic-abi/c/1ngxmSwrafc
>
I don't think the gABI community is interested in a new debug dynamic
tag. I propose DT_GNU_DEBUG:
#define DT_GNU_DEBUG 0x6ffffff8
for the address of a pointer which will be filled by the dynamic
linker. Linker should
add the DT_GNU_DEBUG entry to executable's dynamic section.
BTW, we have a choice. DT_GNU_DEBUG can be readonly or readonly after
relocation, like DT_DEBUG.
--
H.J.
next prev parent reply other threads:[~2021-08-02 4:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 19:32 [RFC PATCH 3/3] add r_debug multiple namespaces support Daniel Walker via Libc-alpha
2020-06-26 21:05 ` Florian Weimer via Libc-alpha
2020-06-26 21:19 ` Carlos O'Donell via Libc-alpha
2020-06-26 21:24 ` Florian Weimer via Libc-alpha
2020-06-26 21:44 ` Carlos O'Donell via Libc-alpha
2020-06-27 9:34 ` Florian Weimer
2020-06-28 12:34 ` Carlos O'Donell via Libc-alpha
2020-06-29 8:51 ` Florian Weimer via Libc-alpha
2021-07-23 23:38 ` H.J. Lu via Libc-alpha
2021-07-27 17:39 ` Daniel Walker via Libc-alpha
2021-07-27 18:14 ` H.J. Lu via Libc-alpha
2021-07-28 15:15 ` H.J. Lu via Libc-alpha
2021-07-28 15:44 ` Daniel Walker via Libc-alpha
2021-07-28 17:14 ` H.J. Lu via Libc-alpha
2021-07-28 19:02 ` Daniel Walker via Libc-alpha
2021-07-28 20:04 ` H.J. Lu via Libc-alpha
2021-08-02 4:24 ` H.J. Lu via Libc-alpha [this message]
2021-08-02 5:22 ` RFC: Add DT_GNU_DEBUG Florian Weimer via Libc-alpha
2021-08-02 13:10 ` H.J. Lu via Libc-alpha
2021-08-03 16:39 ` Daniel Walker via Libc-alpha
2021-08-03 18:08 ` H.J. Lu via Libc-alpha
2021-08-03 20:04 ` Daniel Walker via Libc-alpha
2021-08-03 18:12 ` Florian Weimer via Libc-alpha
2021-08-03 18:23 ` H.J. Lu via Libc-alpha
2021-08-03 20:13 ` Florian Weimer via Libc-alpha
2021-08-03 20:21 ` H.J. Lu via Libc-alpha
2021-08-09 14:32 ` RFC: 2 choices of DT_XXX for dlmopen H.J. Lu via Libc-alpha
2021-08-09 17:16 ` Daniel Walker via Libc-alpha
2021-08-15 0:33 ` [PATCH] Extend struct r_debug to support multiple namespaces H.J. Lu via Libc-alpha
2021-08-16 16:20 ` Daniel Walker via Libc-alpha
2021-08-17 1:07 ` H.J. Lu via Libc-alpha
2020-06-27 1:21 ` [RFC PATCH 3/3] add r_debug multiple namespaces support Daniel Walker (danielwa) via Libc-alpha
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='CAMe9rOpyFWJeX1db_6iNqQBAOzqywy4Nw2QhLjE=mWH_bZykTg@mail.gmail.com' \
--to=libc-alpha@sourceware.org \
--cc=conhuang@cisco.com \
--cc=danielwa@cisco.com \
--cc=fw@deneb.enyo.de \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=jstengle@cisco.com \
--cc=markus.t.metzger@intel.com \
--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).