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/29453] [gdb/symtab] read.h:309: internal-error: set_length: Assertion `m_length == length' failed
Date: Sun, 07 Aug 2022 08:01:25 +0000	[thread overview]
Message-ID: <bug-29453-4717-byb5mDODqT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29453-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> A simple fix is, don't calculate length based on the CU list:
> ...
> diff --git a/gdb/dwarf2/read.c b/gdb/dwarf2/read.c
> index c65a8831bcb..7253c7c0d3e 100644
> --- a/gdb/dwarf2/read.c
> +++ b/gdb/dwarf2/read.c
> @@ -4677,7 +4677,7 @@ create_cus_from_debug_names_list (dwarf2_per_bfd
> *per_bf
> d,
>                          " ignoring .debug_names."));
>               return false;
>             }
> -         const ULONGEST length = sect_off_next - sect_off_prev;
> +         const ULONGEST length = 0;
>           dwarf2_per_cu_data_up per_cu
>             = create_cu_from_index_list (per_bfd, &section, is_dwz,
>                                          sect_off_prev, length);
> ...

Tested this, no regressions.

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

  parent reply	other threads:[~2022-08-07  8:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-07  6:59 [Bug symtab/29453] New: " vries at gcc dot gnu.org
2022-08-07  7:02 ` [Bug symtab/29453] " vries at gcc dot gnu.org
2022-08-07  8:01 ` vries at gcc dot gnu.org [this message]
2022-08-09 12:36 ` vries at gcc dot gnu.org
2022-09-01  6:41 ` vries at gcc dot gnu.org
2022-09-14  8:46 ` 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-29453-4717-byb5mDODqT@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).