This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 3/6] disas: add gdb_disassembly_vec
- From: Pedro Alves <palves at redhat dot com>
- To: Markus Metzger <markus dot t dot metzger at intel dot com>, dje at google dot com
- Cc: gdb-patches at sourceware dot org
- Date: Fri, 09 Oct 2015 13:49:42 +0100
- Subject: Re: [PATCH 3/6] disas: add gdb_disassembly_vec
- Authentication-results: sourceware.org; auth=none
- References: <1442847283-10200-1-git-send-email-markus dot t dot metzger at intel dot com> <1442847283-10200-4-git-send-email-markus dot t dot metzger at intel dot com>
On 09/21/2015 03:54 PM, Markus Metzger wrote:
> Add a new function to disassemble a vector of instructions instead of a
> contiguous range of instructions. The instructions can be in any order
> and may originate from different functions.
>
> Change gdb_disassembly to create a vector of instructions from its low,
> high, and how_many arguments.
I wonder whether the representation could/should be based on a vector
of struct mem_range's instead of a vector of instructions. I'm assuming
the normal case is that we're disassembling ranges of more than
one instruction. Just seems wasteful for something like
(gdb) disassemble 0x3000000000,0x7000000000
to allocate so much memory. But maybe I simply misunderstood.
Thanks,
Pedro Alves