From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B2238385B831; Mon, 6 Apr 2020 11:04:51 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B2238385B831 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1586171091; bh=X4GMfB9hIrYKb2d+dC6m3RN7/uVHbw8xSf7wp3Kcl8g=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Hs7O/jRXj87iaj3VpVefOdfg0w1DtjQ8xFhOob2OQoxHbCmQpnnVJAFccj4u/vsW5 iqCxrbcoPMW4lcodYLMy1C/pI5jWHpjWV9PMhf8lUz/r5fn2WE3NPhWTKjb+FixzbN ZnIA+pDmKYGnlhdk6fe/EIC4e/bVRyKVTdqX5q+Y= From: "bernd.edlinger at hotmail dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/94474] Incorrect DWARF range information for inlined function Date: Mon, 06 Apr 2020 11:04:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: debug X-Bugzilla-Version: 9.2.0 X-Bugzilla-Keywords: wrong-debug X-Bugzilla-Severity: normal X-Bugzilla-Who: bernd.edlinger at hotmail dot de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Apr 2020 11:04:51 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94474 --- Comment #3 from Bernd Edlinger --- (In reply to Andrew Burgess from comment #2) > Sorry for including the wrong DWARF dump output in the bug report. I too > had seen the DW_AT_GNU_entry_view using a more recent binutils. >=20 NP. > When you pose the question: >=20 > I am not sure if there are any view numbers when the inline has multiple > ranges, (I dont remember) >=20 > I think you're asking do we get DW_AT_GNU_entry_view when we have multiple > ranges. And the answer is yes, this case already has multiple ranges (it > has a DW_AT_ranges, which contains multiple ranges), and this is super > confusing, because each range could, I guess, could have a different view > number for its start, right? >=20 I am talking about the end of the range each of the subranges They should have view numbers, gdb should note the view number when parsing the line program. I think we need an DW_AT_GNU_exit_view, you know, young jedi :-) Bernd.=