public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/26151] Add ET_* markers for debug files, and enhance ldd (ld.so) to use them.
Date: Fri, 26 Jun 2020 16:18:04 +0000 [thread overview]
Message-ID: <bug-26151-131-rYCA2MsXYg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26151-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26151
--- Comment #12 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Carlos O'Donell from comment #11)
> >
> > Let's make a proposal for ET_DEBUG to gABI. If it is rejected, we send
> > ET_GNU_DEBUG to gnu-gABI.
>
> Sounds good to me.
>
Done.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-06-26 16:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 15:19 [Bug dynamic-link/26151] New: " carlos at redhat dot com
2020-06-22 15:30 ` [Bug dynamic-link/26151] " carlos at redhat dot com
2020-06-22 15:34 ` carlos at redhat dot com
2020-06-22 15:35 ` carlos at redhat dot com
2020-06-22 15:39 ` carlos at redhat dot com
2020-06-22 15:42 ` mark at klomp dot org
2020-06-22 20:29 ` hjl.tools at gmail dot com
2020-06-22 20:53 ` carlos at redhat dot com
2020-06-22 21:12 ` hjl.tools at gmail dot com
2020-06-23 12:44 ` carlos at redhat dot com
2020-06-23 12:46 ` carlos at redhat dot com
2020-06-23 12:54 ` hjl.tools at gmail dot com
2020-06-23 15:20 ` carlos at redhat dot com
2020-06-23 16:08 ` hjl.tools at gmail dot com
2020-06-26 16:08 ` carlos at redhat dot com
2020-06-26 16:18 ` hjl.tools at gmail dot com [this message]
2020-07-07 8:17 ` fweimer at redhat dot com
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=bug-26151-131-rYCA2MsXYg@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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).