From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/3] Remove 'read' call from dwz_file::read_string
Date: Mon, 24 Mar 2025 16:30:56 -0400 [thread overview]
Message-ID: <b3b1fdf5-8ba5-4c9a-9ead-1779551a60db@simark.ca> (raw)
In-Reply-To: <20250323-dwz-dwarf-5-v2-v1-1-3c0775ca5514@tromey.com>
On 2025-03-23 15:20, Tom Tromey wrote:
> dwz_file::read_string calls 'read' on the section, but this isn't
> needed as the sections have all been pre-read.
In the long term, to remove unnecessary 'read' calls in a safe way, I
was thinking of introducing some kind of 'dwarf2_read_section_info' type
that would be a thin wrapper around a `dwarf2_section_info`, but one
that you could only obtain by calling `dwarf2_section_info::read`. That
would be a kind of "token" to make sure that the section is safe to read
from. A bit like when a function accepts an std::lock_guard object, it
is guaranteed that the lock is taken.
> @@ -261,7 +263,7 @@ dwarf2_read_dwz_file (dwarf2_per_objfile *per_objfile)
> error (_("could not find '.gnu_debugaltlink' file for %s"),
> per_bfd->filename ());
>
> - auto result = std::make_unique<dwz_file> (std::move (dwz_bfd));
> + dwz_file_up result (new dwz_file (std::move (dwz_bfd)));
Why this change?
Otherwise, LGTM.
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Simon
next prev parent reply other threads:[~2025-03-24 20:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-23 19:19 [PATCH 0/3] Support DWARF 5 .debug_sup section Tom Tromey
2025-03-23 19:20 ` [PATCH 1/3] Remove 'read' call from dwz_file::read_string Tom Tromey
2025-03-24 14:25 ` Alexandra Petlanova Hajkova
2025-03-24 20:30 ` Simon Marchi [this message]
2025-03-24 20:52 ` Tom Tromey
2025-03-23 19:20 ` [PATCH 2/3] Handle DWARF 5 separate debug sections Tom Tromey
2025-03-24 15:45 ` Alexandra Petlanova Hajkova
2025-03-24 17:16 ` Tom Tromey
2025-04-03 14:39 ` Tom Tromey
2025-04-22 14:55 ` Tom Tromey
2025-04-22 15:10 ` Simon Marchi
2025-04-28 11:35 ` Tom de Vries
2025-03-24 20:52 ` Simon Marchi
2025-03-25 13:37 ` Tom Tromey
2025-03-23 19:20 ` [PATCH 3/3] Add "-5" flag to cc-with-tweaks 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=b3b1fdf5-8ba5-4c9a-9ead-1779551a60db@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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