From: "mcermak 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: Fri, 14 Jul 2023 15:25:20 +0000 [thread overview]
Message-ID: <bug-30407-6586-Z90pEsFCuY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30407-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30407
--- Comment #4 from Martin Cermak <mcermak at redhat dot com> ---
Created attachment 14964
--> https://sourceware.org/bugzilla/attachment.cgi?id=14964&action=edit
A WIP patch showing line numbers, but no file names yet
First time I see DWARF this closely. The attached WIP patch allows for showing
the line numbers already. The DWARF structure change roughly is as follows:
DWARF-4 DWARF-5
==================================================================
unit_length unit_length
version (uhalf) version (uhalf)
--- address_size (ubyte)
--- segment_selector_size (ubyte)
header_length header_length
minimum_instruction_length (ubyte) minimum_instruction_length (ubyte)
maximum_operations_per_instruction (ubyte) maximum_operations_per_instruction
(ubyte)
default_is_stmt (ubyte) default_is_stmt (ubyte)
line_base (sbyte) line_base (sbyte)
line_range (ubyte) line_range (ubyte)
opcode_base (ubyte) opcode_base (ubyte)
standard_opcode_lengths (array of ubyte) standard_opcode_lengths (array of
ubyte)
include_directories (sequence of path names) ---
file_names (sequence of file entries) ---
--- directory_entry_format_count
(ubyte)
--- directory_entry_format (sequence
of ULEB128 pairs)
--- directories_count (ULEB128)
--- directories (sequence of directory
names)
--- file_name_entry_format_count
(ubyte)
--- file_name_entry_format (sequence
of ULEB128 pairs)
--- file_names_count (ULEB128)
--- file_names (sequence of file name
entries)
So, the attached WIP patch merely jumps over address_size and
segment_selector_size for now. Looking into how to display the file name now...
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-07-14 15:25 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
2023-07-14 15:25 ` mcermak at redhat dot com [this message]
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-Z90pEsFCuY@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).