From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/25088] New: Support split-dwarf
Date: Wed, 09 Oct 2019 15:47:00 -0000 [thread overview]
Message-ID: <bug-25088-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=25088
Bug ID: 25088
Summary: Support split-dwarf
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: translator
Assignee: systemtap at sourceware dot org
Reporter: mark at klomp dot org
Target Milestone: ---
Since elfutils 0.171 libdw support split-dwarf (.dwo files). This is mostly,
but not totally, transparent for users like stap.
The easiest way to support split-dwarf is to use the new interface
dwarf_get_units where currently dwarf_next_unit or dwarf_nextcu is used.
/* Gets the next Dwarf_CU (unit), version, unit type and if available
the CU DIE and sub (type) DIE of the unit. Returns 0 on success,
-1 on error or 1 if there are no more units. To start iterating
provide NULL for CU. If version < 5 the unit type is set from the
CU DIE if available (DW_UT_compile for DW_TAG_compile_unit,
DW_UT_type for DW_TAG_type_unit or DW_UT_partial for
DW_TAG_partial_unit), otherwise it is set to zero. If unavailable
(the version or unit type is unknown) the CU DIE is cleared.
Likewise if the sub DIE isn't isn't available (the unit type is not
DW_UT_type or DW_UT_split_type) the sub DIE tag is cleared. */
extern int dwarf_get_units (Dwarf *dwarf, Dwarf_CU *cu, Dwarf_CU **next_cu,
Dwarf_Half *version, uint8_t *unit_type,
Dwarf_Die *cudie, Dwarf_Die *subdie)
__nonnull_attribute__ (3);
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-10-09 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 15:47 mark at klomp dot org [this message]
2019-10-09 15:49 ` [Bug translator/25088] " amerey at redhat dot com
2019-10-09 17:43 ` wcohen 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-25088-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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).