public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
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:41:49 +0000	[thread overview]
Message-ID: <bug-30622-4717-XnIfJPqJmX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30622-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30622

--- Comment #4 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Parker Dahn from comment #3)

> I apologize for the delay

No problem :)

> I built 13.2 and tried again, here is the print out of the backtrace. What
> is the "bad" debug info you are looking for?

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:

> 0x55a3d75d7d19 read_array_type
>         ../../gdb-13.2/gdb/stabsread.c:3533

... 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.

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.

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-07-18 20:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 18:22 [Bug gdb/30622] New: " parkerdahn at gmail dot com
2023-07-08 14:56 ` [Bug gdb/30622] " tromey at sourceware dot org
2023-07-18 15:51 ` parkerdahn at gmail dot com
2023-07-18 15:59 ` parkerdahn at gmail dot com
2023-07-18 20:41 ` tromey at sourceware dot org [this message]
2023-07-18 20:44 ` parkerdahn at gmail dot com
2023-07-19 13:36 ` tromey at sourceware dot org

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-30622-4717-XnIfJPqJmX@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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: link
Be 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).