public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/30741] New: [gdb/symtab, cc-with-debug-names] gdb/dwarf2/index-write.c:1305: internal-error: write_debug_names: Assertion `counter == per_bfd->all_units.size ()' failed.
Date: Thu, 10 Aug 2023 10:01:33 +0000 [thread overview]
Message-ID: <bug-30741-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30741
Bug ID: 30741
Summary: [gdb/symtab, cc-with-debug-names]
gdb/dwarf2/index-write.c:1305: internal-error:
write_debug_names: Assertion `counter ==
per_bfd->all_units.size ()' failed.
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: symtab
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
When running test-case gdb.dwarf2/pr13961.exp with target-board
cc-with-debug-names, I run into:
...
Running /data/vries/gdb/src/gdb/testsuite/gdb.dwarf2/pr13961.exp ...
gdb compile failed, /data/vries/gdb/src/gdb/dwarf2/index-write.c:1305:
internal-error: write_debug_names: Assertion `counter ==
per_bfd->all_units.size ()' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
----- Backtrace -----
0x59f3a4 gdb_internal_backtrace_1
/data/vries/gdb/src/gdb/bt-utils.c:122
0x59f447 _Z22gdb_internal_backtracev
/data/vries/gdb/src/gdb/bt-utils.c:168
0xd06ae4 internal_vproblem
/data/vries/gdb/src/gdb/utils.c:396
0xd06eb3 _Z15internal_verrorPKciS0_P13__va_list_tag
/data/vries/gdb/src/gdb/utils.c:476
0x14a622a _Z18internal_error_locPKciS0_z
/data/vries/gdb/src/gdbsupport/errors.cc:58
0x6d9e62 write_debug_names
/data/vries/gdb/src/gdb/dwarf2/index-write.c:1305
0x6da547 _Z17write_dwarf_indexP14dwarf2_per_bfdPKcS2_S2_13dw_index_kind
/data/vries/gdb/src/gdb/dwarf2/index-write.c:1463
0x6da87b save_gdb_index_command
/data/vries/gdb/src/gdb/dwarf2/index-write.c:1524
0x5f7f5a do_simple_func
/data/vries/gdb/src/gdb/cli/cli-decode.c:95
0x5fcf6e _Z8cmd_funcP16cmd_list_elementPKci
/data/vries/gdb/src/gdb/cli/cli-decode.c:2735
0xc5fc93 _Z15execute_commandPKci
/data/vries/gdb/src/gdb/top.c:575
0x91ad4a catch_command_errors
/data/vries/gdb/src/gdb/main.c:518
0x91af56 execute_cmdargs
/data/vries/gdb/src/gdb/main.c:617
0x91c280 captured_main_1
/data/vries/gdb/src/gdb/main.c:1289
0x91c483 captured_main
/data/vries/gdb/src/gdb/main.c:1310
0x91c522 _Z8gdb_mainP18captured_main_args
/data/vries/gdb/src/gdb/main.c:1339
0x419602 main
/data/vries/gdb/src/gdb/gdb.c:39
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-08-10 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 10:01 vries at gcc dot gnu.org [this message]
2023-08-10 10:22 ` [Bug symtab/30741] " vries at gcc dot gnu.org
2023-08-10 13:46 ` cvs-commit at gcc dot gnu.org
2023-08-10 13:51 ` vries at gcc dot gnu.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-30741-4717@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).