disassembly options

[Daniel Jacobowitz]

On Mon, Sep 17, 2007 at 12:40:48PM +0100, Nick Clifton wrote:
> I think that even 80% might be a bit optimistic.  Maybe one approach would be 
> to not display this information when performing a static analysis (ie via 
> objdump -d) but instead to provide it when performing a disassembly for a third 
> party which can provide dynamic analysis.  ie I am thinking of GDB here, using 
> the opcodes library to provide a disassembly.  If the opcodes library provided 
> a new API function to map memory addresses to mmr register names, then GDB 
> could choose to display the mmr name as a comment when it is displaying a line 
> of disassembly.  Since GDB would have access to the actual register values, it 
> could be sure of getting the correct mmr name.

A lot of the time it doesn't; it's disassembling some other code
rather than the current code.  It would be able to sometimes, though.

Also GDB already has XML support.

-- 
Daniel Jacobowitz
CodeSourcery