public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/12997] support dwarf4 .debug_types
Date: Mon, 25 Sep 2023 19:17:52 +0000	[thread overview]
Message-ID: <bug-12997-6586-mPknYqvrVE@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12997-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=12997

William Cohen <wcohen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |wcohen at redhat dot com

--- Comment #2 from William Cohen <wcohen at redhat dot com> ---
This is partially addressed by git commit
337b7c44b1cd672f76e58166a562c12a300ddb20:

Author: Tom Tromey <tromey@redhat.com>  2012-03-16 12:44:14
Committer: Mark Wielaard <mjw@redhat.com>  2012-03-21 11:36:31
Parent: 1485ded3f2d709c9011bd9f340ce39b1930f7e32 (PR13876: same another test
case)
Child:  2a885a4a9ca1826187c97c7eb128b06b4a5222f2 (Depend on elfutils 0.148+,
document debug_types support requires 0.154+.)
Branches: master, remotes/origin/master and many more (54)
Follows: release-1.7
Precedes: release-1.8

    Partial fix for PR12997 - support dwarf4 .debug_types

    This fix does not solve the ET_REL case pointed out in the PR.
    However, it does work ok for ordinary code.

        * dwflpp.cxx (dwflpp::iterate_over_cus): Add 'want_types' argument.
        Iterate over type units.
        (dwflpp::declaration_resolve_other_cus): Update.
        (dwflpp::iterate_single_function): Update.
        (dwflpp::iterate_over_globals): Also allow DW_TAG_type_unit.
        * dwflpp.h (module_tus_read_t): New typedef.
        (dwflpp::iterate_over_cus): Update.
        (dwflpp::module_tus_read): New member.
        * tapsets.cxx (dwarf_query::query_module_dwarf): Update.
        (tracepoint_query::handle_query_module): Update.
        * testsuite/systemtap.pass1-4/debugtypes.cxx: New file.
        * testsuite/systemtap.pass1-4/debugtypes.exp: New file.
        * testsuite/systemtap.pass1-4/debugtypes.stp: New file.

    I built gdb with '-gdwarf-4 -fdebug-types-section'.
    Then I tried this stap script:

    probe
process("/home/tromey/gnu/archer/build/gdb/gdb").function("dwarf2_attr") {
          println(@cast($dwarf2_per_objfile, "struct
dwarf2_per_objfile")->objfile)
    }

    With Fedora 16 stap:

    barimba. stap -p2 /tmp/q.stp
    semantic error: type definition 'struct dwarf2_per_objfile' not found:
identifier '@cast' at /tmp/q.stp:2:15
            source:       println(@cast($dwarf2_per_objfile, "struct
dwarf2_per_objfile")->objfile)
                                      ^
    Pass 2: analysis failed.  Try again with another '--vp 01' option.

    After the patch, this works.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2023-09-25 19:17 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 ` [Bug translator/12997] " mjw at redhat dot com
2017-10-11 10:44 ` 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 [this message]

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-mPknYqvrVE@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).