[PATCH 3/6] disas: add gdb_disassembly_vec

[Pedro Alves]

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