From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug tools/22138] New: Support marking "debug" info files with special ET_GNU_DEBUG_* values.
Date: Thu, 14 Sep 2017 19:25:00 -0000 [thread overview]
Message-ID: <bug-22138-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=22138
Bug ID: 22138
Summary: Support marking "debug" info files with special
ET_GNU_DEBUG_* values.
Product: elfutils
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tools
Assignee: unassigned at sourceware dot org
Reporter: fweimer at redhat dot com
CC: carlos at redhat dot com, elfutils-devel at sourceware dot org,
fweimer at redhat dot com, unassigned at sourceware dot org
Blocks: 22101
Target Milestone: ---
+++ This bug was initially created as a clone of Bug #22136 +++
We need a way to identify "debug" info files, which appear like they are ELF
files but if inspected are actually missing a lot of information and can't be
properly parsed without the original DSO or executable.
To that end I suggest we adopt:
* ET_GNU_DEBUG_EXEC
* ET_GNU_DEBUG_DYN
* ET_GNU_DEBUG_REL
As ways to mark these files a debug information files. We can place them into
the OS-specific area, and audit that we don't overlap anything important from
other OSs.
We would need new binutils options to edit, adjust and set the "debug"-ness of
files.
Referenced Bugs:
https://sourceware.org/bugzilla/show_bug.cgi?id=22101
[Bug 22101] Dynamic loader must ignore "debug" shared objects e.g.
ET_GNU_DEBUG_*
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2017-09-14 19:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-22138-10460@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@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).