| Disassembly view - Show Opcodes [message #1220666] |
Thu, 12 December 2013 19:10  |
Eclipse User |
|
|
|
I'm having trouble getting opcodes to display in the Disassembly window whilst debugging.
If I right click the window and select "Show Opcodes" you can see the disassembly text move to the right a little but no opcode
The GDB console (in MI mode) shows the gdb commands being given
-data-disassemble -s 0x..... -e 0x.... --1
-data-disassemble -s 0x..... -e 0x.... --0
These output long lines of disassembly with the address, offset, asm etc...
done,asm_insns=[{address="0x08006964",func-name="Reset_Handler",offset="4",inst="ldr\tr1, [r0, #0]"}
According to the gdb manual it requires the option --2 to output raw hex opcode which the presumably gets parsed into the Disassembly display window
Am I missing something?
Using...
Eclipse IDE for C/C++ Developers
Version: Kepler Service Release 1
Build id: 20130919-0819
Eclipse CDT stuff
C/C++ Remote Debug Launcher 6.2.0.201309180223
CDT GCC Cross Compiler Support 1.2.0.201309180223
Eclipse C/C++ Development Tools 8.2.1.201309180223
Eclipse C/C++ Development Tools SDK 8.2.1.201309180223
Eclipse GDB Hardware Debugging Plug-in 7.2.0.201309180223
GDB Common 7.2.1.201309180223
|
|
|
|
| Re: Disassembly view - Show Opcodes [message #1237254 is a reply to message #1221119] |
Wed, 29 January 2014 03:46  |
| Eclipse User |
|
|
|
I ran into the same problem and, after some tedious plodding through the Eclipse git repository, found out that it's a feature that was 90% implemented more than 2 years ago, but then abandoned for some reason.
This is the feature request tracking the issue:
Bug 357270
The low-level part, querying the opcodes from GDB, has been implemented and was tracked here: Bug 357073
The high-level part, the opcode column in the view and related preferences, has also been implemented and was tracked here: Bug 357440
What's missing is some tiny middle part connecting the two ends:
IInstruction.java needs a small addition to store raw opcode bytes
MIInstruction.java needs a small addition to parse the opcode bytes in the GDB response
DisassemblyBackendDsf.java needs a small addition to retrieve the opcode bytes and put them in the disassembly
I'll that it in the bug report and see what happens...
|
|
|
Powered by
FUDForum. Page generated in 0.45878 seconds
Home