From: sourceware.org@brn.li
To: gdb@sourceware.org
Subject: Assertion `idx >= 0 && idx < num_fields ()' failed.
Date: Tue, 21 Nov 2023 15:09:39 +0000 [thread overview]
Message-ID: <77df76a0525202bbbad9520a0467a5075efbd12c@brn.li> (raw)
When debugging QEMU with a breakpoint at `cpu_handle_exception` GDB crashes:
```
hit Breakpoint 1, cpu_handle_exception (cpu=0x5555573a2e00, ret=0x7fffffff99a4) at ../qemu-7.1.0/accel/tcg/cpu-exec.c:647
647 if (cpu->exception_index < 0) {
../../gdb/gdbtypes.h:985: internal-error: field: Assertion `idx >= 0 && idx < num_fields ()' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
0x564124985b0b ???
0x564124d6b4c4 ???
0x564124e55503 ???
0x5641248ffdf1 ???
0x564124d8fc49 ???
0x564124c9498c ???
0x564124d7b633 ???
0x564124c940e7 ???
0x564124c945df ???
0x564124d7b633 ???
0x564124c940e7 ???
0x564124c945df ???
0x564124d7b633 ???
0x564124c940e7 ???
0x564124c945df ???
0x564124d7b633 ???
0x564124c484ee ???
0x7f2db3c1abff ???
0x7f2db3c165fc ???
0x7f2db3c03890 ???
0x7f2db3bf1326 ???
0x7f2db3be3838 ???
0x7f2db3c0955f ???
0x7f2db3be722a ???
0x7f2db3c2b582 ???
0x7f2db3c2aa6d ???
0x7f2db3be722a ???
0x7f2db3c0955f ???
0x7f2db3bf9b55 ???
0x7f2db3c28b36 ???
0x564124c2b39a ???
0x5641249c04a4 ???
0x564124d32ed3 ???
0x5641249ce902 ???
0x5641249ceda1 ???
0x564124c4f7d7 ???
0x7f2db3bf9ea0 ???
0x7f2db3bd953b ???
0x7f2db3be3838 ???
0x7f2db3c0955f ???
0x7f2db3bf9b55 ???
0x7f2db3c9e680 ???
0x564124eb084a ???
0x564124c39162 ???
0x564124ea1b41 ???
0x564124b7fcbd ???
0x564124b690de ???
0x564124e55d7d ???
0x564124e98fee ???
0x564124bb5e24 ???
0x5641248e9694 ???
0x7f2db3445ccf ???
0x7f2db3445d89 ???
0x5641248f08e4 ???
0xffffffffffffffff ???
---------------------
This is a bug, please report it. For instructions, see:
<https://www.gnu.org/software/gdb/bugs/>.
```
Likely unrelated to #29950, as `-gstabs+` is not used.
If you like me to submit bugs using your issue tracker you should make it accessible and allow account registration.
Regards,
Simon Wörner
next reply other threads:[~2023-11-21 15:09 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 [this message]
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
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=77df76a0525202bbbad9520a0467a5075efbd12c@brn.li \
--to=sourceware.org@brn.li \
--cc=gdb@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).