From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0571E3858412; Tue, 18 Jul 2023 20:44:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0571E3858412 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1689713091; bh=6stkOIGYT2D3bxvIoQAA92z8PhbV4DZc1rW8LJhKY3w=; h=From:To:Subject:Date:In-Reply-To:References:From; b=rpREIF0pzRM0k41waapobc299xBUpDhxqpcED9ma7aKuJI40j2o2CGj+qyRNnefwK XECdUsS7jaj/tvLHFTib+LGTjWXZVeY5cWFcZbwO4feunwbWXkduNy0XTAjx+uZ3AH nmwnqxpRUHnzG0C8HF6xzld9maY7gtxGmVaOHJXk= From: "parkerdahn at gmail dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/30622] symbol file: create_range_type: Assertion `TYPE_LENGTH (index_type) > 0' failed Date: Tue, 18 Jul 2023 20:44:50 +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: parkerdahn at gmail dot com 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 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D30622 --- Comment #5 from Parker Dahn --- (In reply to Tom Tromey from comment #4) > (In reply to Parker Dahn from comment #3) >=20 > > I apologize for the delay >=20 > No problem :) >=20 > > I built 13.2 and tried again, here is the print out of the backtrace. W= hat > > is the "bad" debug info you are looking for? >=20 > Normally what I'd want to see is the executable you are trying to debug. > However, in this case, the stack trace from gdb tells us something: >=20 > > 0x55a3d75d7d19 read_array_type > > ../../gdb-13.2/gdb/stabsread.c:3533 >=20 > ... this means you are using the "stabs" debug format. > stabs aren't really maintained in gdb at all. They've been > obsolete for decades now. >=20 > Are you forced to use stabs for some reason? If so, then probably the > bug can be fixed in gdb ... but most likely you'd be on your own. >=20 > Otherwise, if you don't have to use stabs, then most likely your problem > can be fixed by switching debug formats. That is, change "-gstabs" > to "-g" and rebuild from scratch. Unfortunately I am unable to recompile the target binary, but thank you for= the quick assistance. --=20 You are receiving this mail because: You are on the CC list for the bug.=