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/29572] [gdb/symtab] read.h:298: internal-error: length: Assertion `m_length != 0' failed.
Date: Wed, 14 Sep 2022 09:53:01 +0000	[thread overview]
Message-ID: <bug-29572-4717-WiyQtXw4mZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29572-4717@http.sourceware.org/bugzilla/>

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

--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #2)
> Created attachment 14335 [details]
> Demonstrator patch
> 
> This is an alternative way of fixing PR29453.
> 
> Basically, we look into the CU header to find the length.

The more intrusive, but more maintainable version of this would be to just
always call create_all_comp_units, not just for readnow and cooked index, but
also for .debug_names and .gdb_index.

Tom, I think you suggested that already somewhere.

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

  parent reply	other threads:[~2022-09-14  9:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  8:28 [Bug symtab/29572] New: " vries at gcc dot gnu.org
2022-09-14  8:30 ` [Bug symtab/29572] " vries at gcc dot gnu.org
2022-09-14  8:31 ` vries at gcc dot gnu.org
2022-09-14  9:52 ` vries at gcc dot gnu.org
2022-09-14  9:53 ` vries at gcc dot gnu.org [this message]
2022-09-14 12:30 ` vries at gcc dot gnu.org
2022-09-14 13:02 ` vries at gcc dot gnu.org
2022-09-14 13:50 ` vries at gcc dot gnu.org
2022-09-14 15:49 ` vries at gcc dot gnu.org
2023-07-20 12:44 ` vries at gcc dot gnu.org
2023-08-10 13:46 ` cvs-commit at gcc dot gnu.org
2023-12-06  9:29 ` cvs-commit at gcc dot gnu.org
2023-12-06  9:35 ` 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-29572-4717-WiyQtXw4mZ@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).