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: Sat, 08 Jul 2023 14:56:07 +0000 [thread overview]
Message-ID: <bug-30622-4717-baGNEek1gb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30622-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30622
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
(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.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-07-08 14:56 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 ` tromey at sourceware dot org [this message]
2023-07-18 15:51 ` [Bug gdb/30622] " 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
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-baGNEek1gb@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).