From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C306B3858D39; Sat, 8 Jul 2023 14:56:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C306B3858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1688828168; bh=TxoNSXV/d+t4E/EWp72e3463u0yWEnRUu2vsSPN7uU4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=CVm6IR48hnu+JfCPLWdqrb4kBMzLTNzHOh9XDXXFR0hVqZr8g35YOZonBrih6sVXF L7cvlYnApYcuKNT850bfNjGgeqkZ7b8cN0H505U01NDieE0NfKXbhxDlaRIH1MADEK ikwnM40qOrrRL1C7Wb0j8u10zAwdyaVOf12T3Ozw= From: "tromey at sourceware dot org" To: gdb-prs@sourceware.org Subject: [Bug gdb/30622] symbol file: create_range_type: Assertion `TYPE_LENGTH (index_type) > 0' failed Date: Sat, 08 Jul 2023 14:56:07 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: 12.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: tromey at sourceware dot org 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: cc 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=3D30622 Tom Tromey changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tromey at sourceware dot o= rg --- Comment #1 from Tom Tromey --- (In reply to Parker Dahn from comment #0) > However if I do not provide the file for symbols it does execute just fine Yeah, this is a crash related to the debug reader, in particular when making a type. Can you share your executable? > GNU gdb (Ubuntu 12.1-0ubuntu1~22.04) 12.1 ... or try a newer version. I don't recall any fixes in this area but it's hard to be sure. Without the executable, the only other option is probably to have you try to debug gdb, for that you'd have to build one with debug info. The main thing is tracking backward from the crash to find the "bad" debuginfo so we can make a reproducer. --=20 You are receiving this mail because: You are on the CC list for the bug.=