RE: [Bastard-libdisasm] Data kept for invalid instructions

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

Hey Mike

> That behavior is by design, and not so simple to change; internally,
> size is
> the return value of the disassembly routines, with INVALID_INSN (-1)
> returned instead of size if the instruction is invalid.

I've been going through disasm_addr and noticed that. Will need an extra
argument in the function signature I suppose to hold that byte. (I'm still
talking 2005-02-27)

> A compromise would be to set the size of an invalid instruction to
> 1 byte, and copy that byte into the x86_insn_t -- would that be
> sufficient?

I wasn't sure -- it IS always just one byte, isn't it ? There will be subsequent
1 byte invalid opcodes when processing continues, right ?

I'm about to test an import of your latest libdisasm from CVS. Seems easier to
modify than the 2005-02-27 version I'm running. I just hope it works. Will let
you know.

THANKS