From: Tom Tromey <tom@tromey.com>
To: Mihails Strasuns via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] gdb: move bfd_open_from_target_memory to gdb_bfd
Date: Wed, 09 Dec 2020 14:31:00 -0700 [thread overview]
Message-ID: <875z5ar7jf.fsf@tromey.com> (raw)
In-Reply-To: <20201208093447.15381-1-mihails.strasuns@intel.com> (Mihails Strasuns via Gdb-patches's message of "Tue, 8 Dec 2020 10:34:47 +0100")
>>>>> "Mihails" == Mihails Strasuns via Gdb-patches <gdb-patches@sourceware.org> writes:
Mihails> This function allows to create a BFD handle using an accessible memory
Mihails> range in a target memory. It is currently contained in a JIT module but
Mihails> this functionality may be of wider usefullness - for example, reading
Mihails> ELF binaries contained within a core dump.
Mihails> gdb/ChangeLog:
Mihails> 2020-12-07 Mihails Strasuns <miihails.strasuns@intel.com>
Mihails> * jit.c (mem_bfd*, bfd_open_from_target_memory): Removed.
Mihails> * gdb_bfd.h (gdb_bfd_open_from_target_memory): New function.
Mihails> * gdb_bfd.c (mem_bfd*, gdb_bfd_open_from_target_memory): New functions.
Hi. Thank you for the patch.
It looks good to me. I found a couple of minor nits, but the patch is
OK with these fixed.
Mihails> +/* Create and initialize a BFD handle from a target in-memory range. */
Mihails> +
Mihails> +gdb_bfd_ref_ptr
Mihails> +gdb_bfd_open_from_target_memory (CORE_ADDR addr, ULONGEST size,
Mihails> + const char *target,
Mihails> + const char *filename = nullptr);
In the style style, the return type isn't separated from the function
name in a declaration.
Mihails> + gdb_bfd_ref_ptr nbfd (gdb_bfd_open_from_target_memory (
Mihails> + code_entry->symfile_addr, code_entry->symfile_size, gnutarget));
The formatting here looks weird. Normally breaks would occur before "(".
Tom
next prev parent reply other threads:[~2020-12-09 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 9:34 Mihails Strasuns via Gdb-patches
2020-12-09 21:31 ` Tom Tromey [this message]
2020-12-10 10:17 ` Strasuns, Mihails via Gdb-patches
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=875z5ar7jf.fsf@tromey.com \
--to=tom@tromey.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