This is the mail archive of the
mailing list for the binutils project.
Re: [Patch, moxie] Print 'bad' instructions in disassembly instead of aborting
- From: Pedro Alves <palves at redhat dot com>
- To: Anthony Green <green at moxielogic dot com>
- Cc: binutils at sourceware dot org
- Date: Fri, 28 Sep 2012 16:38:59 +0100
- Subject: Re: [Patch, moxie] Print 'bad' instructions in disassembly instead of aborting
- References: <CACxje5_LP_+xoshUXDx-OtD9HDtwbuT+14MaRH6znaiUQUaF5w@mail.gmail.com>
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.