From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 613373858439; Fri, 14 Jul 2023 15:25:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 613373858439 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1689348321; bh=oV5ja0Au/nx/Dnqm3mFYLQmjH3/mwa94ZCkwddU7ZWQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=jBxTXCORB2RsTg1awXqG4JFVFue37aFUfr5jjHyyRrXcXfAVkKuA/Ldzd4Y9uhiRs GpzkmAm6Ix/clrFmZegGb9usGCUlAWJphpnkHMEh6gN3SmZ6h45MEAw34zPAm3cBbC IYX0qGNt87CihlTugvMhnqS8FqXrLn89PQ6xndcI= From: "mcermak at redhat dot com" 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 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: systemtap X-Bugzilla-Component: tapsets X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mcermak at redhat dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: systemtap at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30407 --- Comment #4 from Martin Cermak --- Created attachment 14964 --> https://sourceware.org/bugzilla/attachment.cgi?id=3D14964&action=3Ded= it A WIP patch showing line numbers, but no file names yet First time I see DWARF this closely. The attached WIP patch allows for sho= wing the line numbers already. The DWARF structure change roughly is as follows: DWARF-4 DWARF-5 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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 (ub= yte) maximum_operations_per_instruction (ubyte) maximum_operations_per_instruc= tion (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 (sequen= ce of ULEB128 pairs) --- directories_count (ULEB128) --- directories (sequence of direc= tory names) --- file_name_entry_format_count (ubyte) --- file_name_entry_format (sequen= ce of ULEB128 pairs) --- file_names_count (ULEB128) --- file_names (sequence of file n= ame 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 no= w... --=20 You are receiving this mail because: You are the assignee for the bug.=