public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/94474] Incorrect DWARF range information for inlined function Date: Mon, 06 Apr 2020 09:59:56 +0000 [thread overview] Message-ID: <bug-94474-4-BphFSQJUc8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94474-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94474 --- Comment #1 from Bernd Edlinger <bernd.edlinger at hotmail dot de> --- Hi, I use a newer binutils versions FWIW, and buit GCC-10 from a few days ago using those binutils. $ readelf -version GNU readelf (GNU Binutils) 2.32 Copyright (C) 2019 Free Software Foundation, Inc. This program is free software; you may redistribute it under the terms of the GNU General Public License version 3 or (at your option) any later version. This program has absolutely no warranty. instead of #+BEGIN_EXAMPLE <2><8db>: Abbrev Number: 38 (DW_TAG_inlined_subroutine) <8dc> DW_AT_abstract_origin: <0x9cc> <8e0> DW_AT_entry_pc : 0x400545 <8e8> Unknown AT value: 2138: 3 <8e9> DW_AT_ranges : 0x30 <8ed> DW_AT_call_file : 1 <8ee> DW_AT_call_line : 52 <8ef> DW_AT_call_column : 10 <8f0> DW_AT_sibling : <0x92f> #+END_EXAMPLE I see: <2><8b3>: Abbrev Number: 38 (DW_TAG_inlined_subroutine) <8b4> DW_AT_abstract_origin: <0x9a4> <8b8> DW_AT_entry_pc : 0x401165 <8c0> DW_AT_GNU_entry_view: 0 <8c1> DW_AT_ranges : 0x30 <8c5> DW_AT_call_file : 1 <8c6> DW_AT_call_line : 52 <8c7> DW_AT_call_column : 10 <8c8> DW_AT_sibling : <0x907> But as you can see there is a view number where the range begins, but there is no view number where the range ends. I am not sure if there are any view numbers when the inline has multiple ranges, (I dont remember) Therefore I try to chamge gdb to ignore is-stmt breakpoints which are at the end of the inline block. I am not sure if an entirely new DWARF version is necessary, or just a new AT value: like 2139 or so, to give us an idea if the is-stmt is per its view in the subroutine or in the calling program. Bernd.
next prev parent reply other threads:[~2020-04-06 9:59 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-03 16:13 [Bug debug/94474] New: " andrew.burgess at embecosm dot com 2020-04-06 9:59 ` bernd.edlinger at hotmail dot de [this message] 2020-04-06 10:54 ` [Bug debug/94474] " andrew.burgess at embecosm dot com 2020-04-06 11:04 ` bernd.edlinger at hotmail dot de 2020-04-06 11:17 ` bernd.edlinger at hotmail dot de 2020-04-06 12:55 ` andrew.burgess at embecosm dot com 2020-04-06 12:57 ` bernd.edlinger at hotmail dot de 2020-04-06 13:15 ` bernd.edlinger at hotmail dot de 2020-04-06 14:16 ` andrew.burgess at embecosm dot com 2020-04-28 2:17 ` bernd.edlinger at hotmail dot de 2020-04-28 9:56 ` andrew.burgess at embecosm dot com 2020-05-16 8:09 ` bernd.edlinger at hotmail dot de 2020-05-17 8:43 ` andrew.burgess at embecosm dot com 2020-05-17 9:05 ` bernd.edlinger at hotmail dot de 2021-12-28 13:16 ` bernd.edlinger at hotmail dot de 2021-12-28 20:57 ` bernd.edlinger at hotmail dot de
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-94474-4-BphFSQJUc8@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).