From: Keith Seitz <keiths@redhat.com>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Use gdb_bfd_openr in corelow.c
Date: Mon, 2 Mar 2026 08:55:30 -0800 [thread overview]
Message-ID: <d1774199-e171-492b-90a7-e5dfe60714e2@redhat.com> (raw)
In-Reply-To: <20260302163129.610391-1-tromey@adacore.com>
On 3/2/26 8:31 AM, Tom Tromey wrote:
> corelow.c has a couple of calls to bfd_openr, each followed by a call
> to new_reference. It's cleaner to use the provided gdb_bfd_openr
> wrapper.
LGTM.
Reviewed-By: Keith Seitz <keiths@redhat.com>
Keith
prev parent reply other threads:[~2026-03-02 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 16:31 Tom Tromey
2026-03-02 16:55 ` Keith Seitz [this message]
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=d1774199-e171-492b-90a7-e5dfe60714e2@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@adacore.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