From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/12997] support dwarf4 .debug_types
Date: Thu, 14 Jul 2011 11:22:00 -0000 [thread overview]
Message-ID: <bug-12997-6586-N6c8NhXHg0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12997-6586@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=12997
Mark Wielaard <mjw at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mjw at redhat dot com
--- Comment #1 from Mark Wielaard <mjw at redhat dot com> 2011-07-14 11:21:25 UTC ---
In theory this is simple. elfutils 0.148+ libdw supports dwarf_next_unit(),
which is like dwarf_next_cu(), but returns either a CU or TU , and
dwarf_offdie_types(), which gives a Dwarf_Die inside a TU, like dwarf_offdie()
provides a Dwarf_Die inside a CU. A DIE can have a DW_AT_signature to indicate
that a type declaration has been placed in a type unit. This has
DW_FORM_ref_sig8 which can be resolved through dwarf_formref_die().
This should work fine for user space (ET_EXEC and ET_DYN). In the case of
ET_REL (like kernel modules) there is an issue that libdw will not handle the
comdat section groups (there will be multiple .debug_type sections in different
groups, while it expects only one). This will have to be fixed in elfutils (or
some pre/post-processing tool that gets run on the kernel modules to first
resolve the comdat groups and merge the .debug_type sections).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-07-14 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 15:24 [Bug translator/12997] New: " fche at redhat dot com
2011-07-14 11:22 ` mjw at redhat dot com [this message]
2017-10-11 10:44 ` [Bug translator/12997] " mark at klomp dot org
2017-10-11 10:48 ` mjw at fedoraproject dot org
2023-09-25 19:17 ` 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-12997-6586-N6c8NhXHg0@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).