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/29381] [gdb, debug-types, debug-names] read.h:309: internal-error: set_length: Assertion `m_length == length' failed.
Date: Tue, 19 Jul 2022 11:34:59 +0000	[thread overview]
Message-ID: <bug-29381-4717-zPCY7t8QQV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29381-4717@http.sourceware.org/bugzilla/>

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

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> When running test-case gdb.cp/cpexprs-debug-types/cpexprs-debug-types with
> target board cc-with-debug-names on a system with gcc 12.1.1 (defaulting to
> dwarf 5), I run into:
> ...
> (gdb) file
> /data/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.cp/cpexprs-
> debug-types/cpexprs-debug-types^M
> Reading symbols from
> /data/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.cp/cpexprs-
> debug-types/cpexprs-debug-types...^M
> warning: Section .debug_aranges in
> /data/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.cp/cpexprs-
> debug-types/cpexprs-debug-types has duplicate debug_info_offset 0x0,
> ignoring .debug_aranges.^M
> /data/vries/gdb_versions/devel/src/gdb/dwarf2/read.h:309: internal-error:
> set_length: Assertion `m_length == length' failed.^M
> A problem internal to GDB has been detected,^M
> further debugging may prove unreliable.^M
> ----- Backtrace -----^M
> ERROR: Couldn't load cpexprs-debug-types into GDB (GDB internal error).
> ... 
> 
> The problem is three-fold.
> 
> 1.
> The .debug_names index is rejected in dwarf2_read_debug_names because:
> ...
>   if (map->tu_count != 0)
>     {
>       /* We can only handle a single .debug_types when we have an
>          index.  */
>       if (per_bfd->types.size () != 1)
>         return false;
> ...
> there are TUs so the tu_count is > 0 but there's no .debug_types section
> (dwarf 5 puts the TUs in the .debug_info section) so the
> "per_bfd->types.size () != 1" test fails.
> 

Filed as PR29385.

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

  parent reply	other threads:[~2022-07-19 11:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-19  7:59 [Bug symtab/29381] New: " vries at gcc dot gnu.org
2022-07-19  8:36 ` [Bug symtab/29381] " vries at gcc dot gnu.org
2022-07-19 10:02 ` vries at gcc dot gnu.org
2022-07-19 10:24 ` vries at gcc dot gnu.org
2022-07-19 11:34 ` vries at gcc dot gnu.org [this message]
2022-07-19 13:14 ` vries at gcc dot gnu.org
2022-07-19 16:50 ` vries at gcc dot gnu.org
2022-07-19 17:36 ` vries at gcc dot gnu.org
2022-07-22 21:52 ` vries at gcc dot gnu.org
2022-08-01 12:04 ` 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-29381-4717-zPCY7t8QQV@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).