From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, mail@simon-woerner.de
Cc: gdb@sourceware.org
Subject: Re: Assertion `idx >= 0 && idx < num_fields ()' failed.
Date: Fri, 24 Nov 2023 15:42:24 -0500 [thread overview]
Message-ID: <a691f0e0-b7c7-44e2-92bb-a3a5bba47d4b@simark.ca> (raw)
In-Reply-To: <87o7fjxgel.fsf@tromey.com>
On 11/24/23 11:30, Tom Tromey wrote:
>> I'm using the latest version:
>> ```
>> $ gdb --version
>> GNU gdb (GDB) 13.2
>> [...]
>> ```
>
> I suspect this is https://sourceware.org/bugzilla/show_bug.cgi?id=29735
> which I believe is fixed for gdb 14.
>
> Tom
You're right, I was able to reproduce and just finished bisecting it.
The other crash mentionned, when using tab-completion, is also fixed,
by this commit:
https://gitlab.com/gnutools/binutils-gdb/-/commit/6e7eef72164c00d6a5a7b0bce9fa01f5481f33cb
Simon
next prev parent reply other threads:[~2023-11-24 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87wmu9hhu5.fsf@tromey.com>
2023-11-21 15:09 ` sourceware.org
2023-11-23 12:11 ` mail
2023-11-23 12:11 ` mail
2023-11-24 16:30 ` Tom Tromey
2023-11-24 20:42 ` Simon Marchi [this message]
2023-11-23 12:11 ` mail
2023-11-23 16:01 ` Simon Marchi
2023-11-23 16:59 ` mail
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=a691f0e0-b7c7-44e2-92bb-a3a5bba47d4b@simark.ca \
--to=simark@simark.ca \
--cc=gdb@sourceware.org \
--cc=mail@simon-woerner.de \
--cc=tom@tromey.com \
/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).