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 tapsets/30407] Tapset function print_ubacktrace_fileline() no longer works with DWARF5
Date: Wed, 12 Jul 2023 14:47:28 +0000	[thread overview]
Message-ID: <bug-30407-6586-aC6KysvDcN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30407-6586@http.sourceware.org/bugzilla/>

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

William Cohen <wcohen at redhat dot com> changed:

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

--- Comment #3 from William Cohen <wcohen at redhat dot com> ---
Had some additional discussion with Martin on email on how to fix this. For
this PR (and 29984) there are two parts that need to be addressed:

1) recognize the dwarf 5 format line info in translate.cxx.  It looks like
https://sourceware.org/bugzilla/show_bug.cgi?id=29984 mentions an area that
needs to be changed to so systemtap copies the line information.

2) have the runtime _stp_linenumber_lookup in runtime/sym.c be able to handle
the dwarf 5 line number headers.

Need to refer to the dwarf debuginfo manuals for dwarf4 and dwarf5 from
https://dwarfstd.org/, section 6.2.4 "The Line Number Program Header" for
details on the differences.  There are differences in the dwarf5 line number
header: address_size, segment_selector_size, directories_count, directories,
etc. in dwarf5 .

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

  parent reply	other threads:[~2023-07-12 14:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-30  6:08 [Bug tapsets/30407] New: Tapset function print_ubacktrace_fileline() no longer works on kernel 6.2 agentzh at gmail dot com
2023-05-02 22:29 ` [Bug tapsets/30407] " agentzh at gmail dot com
2023-05-02 22:32 ` [Bug tapsets/30407] Tapset function print_ubacktrace_fileline() no longer works on kernel 6.2/6.1 agentzh at gmail dot com
2023-06-08 14:27 ` mcermak at redhat dot com
2023-06-08 14:39 ` [Bug tapsets/30407] Tapset function print_ubacktrace_fileline() no longer works with DWARF5 mcermak at redhat dot com
2023-07-12 14:47 ` wcohen at redhat dot com [this message]
2023-07-14 15:25 ` mcermak at redhat dot com
2023-07-26 14:40 ` mark at klomp dot org
2023-10-10  9:14 ` mcermak at redhat dot com
2023-10-10  9:14 ` mcermak 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-30407-6586-aC6KysvDcN@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).