The filename argument to gdb_bfd_open_from_target_memory was never
used; this argument had a default value of nullptr, and the only call
to this function, in jit.c, relied on the default value.
In the next commit I'm going to make some changes to the
gdb_bfd_open_from_target_memory function, and, though I could take
account of a filename parameter, it seems pointless to maintain an
unused argument.
This commit removes the filename argument.
There should be no user visible changes after this commit.
gdb_bfd_ref_ptr
gdb_bfd_open_from_target_memory (CORE_ADDR addr, ULONGEST size,
- const char *target,
- const char *filename)
+ const char *target)
{
struct target_buffer *buffer = XNEW (struct target_buffer);
buffer->base = addr;
buffer->size = size;
- return gdb_bfd_openr_iovec (filename ? filename : "<in-memory>", target,
+ return gdb_bfd_openr_iovec ("<in-memory>", target,
mem_bfd_iovec_open,
buffer,
mem_bfd_iovec_pread,
bool gdb_bfd_get_full_section_contents (bfd *abfd, asection *section,
gdb::byte_vector *contents);
-/* Create and initialize a BFD handle from a target in-memory range. */
+/* Create and initialize a BFD handle from a target in-memory range. The
+ BFD starts at ADDR and is SIZE bytes long. TARGET is the BFD target
+ name as used in bfd_find_target. */
gdb_bfd_ref_ptr gdb_bfd_open_from_target_memory (CORE_ADDR addr, ULONGEST size,
- const char *target,
- const char *filename = nullptr);
+ const char *target);
/* Range adapter for a BFD's sections.