[Bastard-libdisasm] Data kept for invalid instructions

[<kri...@as...>]

Hi Michael,

It appears that when an invalid opcode is encountered by libdisasm, the insn
does not keep any information related to the opcode. It would be nice if the
exact bytes that were available as invalid opcodes were still in the data
structure, and that insn->size was still set to the size of the invalid code area. 

For example, if one was going over a list of disassembled instructions and
copying them somewhere else, missing the invalid opcodes (due to a 0 size, and
no by information) would cause offset problems for other branches inside a
function image!

This is against libdisasm2 extracted from cvs on 2005-02-27. Is this issue
addressed in a newer release ? What is the status of the new release 

Thanks,
Kristis