public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Fix over-eager CU expansion with new DWARF reader
Date: Mon,  7 Nov 2022 09:23:53 -0700	[thread overview]
Message-ID: <20221107162356.3175221-1-tromey@adacore.com> (raw)

PR symtab/29105 concerns an over-eager CU expansion bug with the new
DWARF reader.  This short series fixes the bug.

The first two patches are tiny refactorings to make the final patch
more understandable.

I don't know how to write a good test for this.  In order to try it,
what I had to do on my machine was to install the glibc debuginfo,
disable the use of the gdb index by hacking dwarf2_initialize_objfile
(Fedora uses .gdb_index in the system debuginfo), and finally run the
sizeof.exp test and try it out by hand, with "set debug symtab-create
1".

Regression tested on x86-64 Fedora 34.  Let me know what you think.

Tom



             reply	other threads:[~2022-11-07 16:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-07 16:23 Tom Tromey [this message]
2022-11-07 16:23 ` [PATCH 1/3] Remove language check from dwarf2_compute_name Tom Tromey
2022-12-01 15:16   ` Andrew Burgess
2022-11-07 16:23 ` [PATCH 2/3] Refactor cooked_index::do_finalize Tom Tromey
2022-12-01 15:34   ` Andrew Burgess
2022-11-07 16:23 ` [PATCH 3/3] Add name canonicalization for C Tom Tromey
2022-12-01 16:06   ` Simon Marchi
2022-12-01 16:29   ` Andrew Burgess
2022-12-01 17:56     ` Tom Tromey
2022-12-01 18:16       ` Tom Tromey
2022-12-01 23:23   ` Andrew Burgess
2022-12-02 14:39     ` Tom Tromey

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=20221107162356.3175221-1-tromey@adacore.com \
    --to=tromey@adacore.com \
    --cc=gdb-patches@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).