[Patch, moxie] Print 'bad' instructions in disassembly instead of aborting

[Pedro Alves]

On 09/28/2012 04:53 AM, Anthony Green wrote:
> It used to make sense to have the disassembler abort() when it hit an
> unrecognized instruction. 

This _never_ made sense.  Consider that with e.g., gdb, which uses
libopcodes for disassembly, the user is free to do

 disassembled 0xsome_non_sense_data_address, 0xsome_nonsense_data_address+10

And who knows what random bits that would trip on.

If other ports are doing this, it's an accident waiting to happen.

Thanks for fixing.

-- 
Pedro Alves