From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C0713385780F; Mon, 16 May 2022 16:47:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C0713385780F From: "simark at simark dot ca" To: gdb-prs@sourceware.org Subject: [Bug c++/29153] DW_FORM_rnglistx index pointing outside of .debug_rnglists offset array Date: Mon, 16 May 2022 16:47:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: c++ X-Bugzilla-Version: 12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: simark at simark dot ca X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot 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://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gdb-prs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-prs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 May 2022 16:47:04 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D29153 --- Comment #9 from Simon Marchi --- (In reply to Jean-Micha=C3=ABl Celerier from comment #8) > Ah okay, I thought that objfile refered to "object file" in the usual .o > sense and not shared object I understand the confusion. A .o file would be a "compilation unit" (or CU= ) in this context. > ; libossia.so is 170 megabytes so I was hoping > that there would be a way to narrow things a bit more. Well, by getting the DIE offset, that brings you to a specific CU. You can= see the offset of the beginning of the CU by printing "cu->per_cu->sect_off" in= the read_attribute_reprocess frame. With an objfile this large, it can take quite some time for readelf or llvm-dwarfdump to dump it all. So I usually dump it to a file: readelf --debug-dump obj > file llvm-dwarfdump obj > file and then search for offsets in that file using my text editor or less, which are pretty good for searching in very large files. > I'll try without > -gsplit-dwarf and report. Ok, that would be good to try. Although if the issue is really with -gsplit-dwarf, we'll want to find the root case, not just ignore it ;). --=20 You are receiving this mail because: You are on the CC list for the bug.=