Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » C / C++ IDE (CDT) » Incorrect Cortex M3 code disassembly in eclipse(Problem in disassembler)
Incorrect Cortex M3 code disassembly in eclipse [message #946941] Tue, 16 October 2012 16:54
red baron is currently offline red baronFriend
Messages: 1
Registered: October 2012
Junior Member
Attached are two screenshots, one of arm-eabi-none-gdb disassembly output and one of eclipse showing the same area disassembled. The area disassembled is the printf function within the libc library of the yargato toolchain for the Cortex M3 ARM processor.

When using eclipse to step through the code at the instruction level you can click the step into button several times without the highlighted line in the disassembly pane moving sometimes... as if it was executing several lines of code in the background. this lead me to suspect the disassembly view was incorrect.

To check if it was the Yagarto toolchain or eclipse causing the fault I run up arm-none-eabi-gdb directly in a cmd line window and did a disassembly of the printf address to generate a screenshot of the mnemonics - ones I expected to see. The other screen shot is the exact same area disessembled via the eclipse disassembly view which shows a different set of mnemonics. The former I suspect are valid and correct, the latter in eclipse incorrect with some missing addresses listed.

My eclipse was basically configured as per Yagartos useful guide on their website for integrating their toolchain with the eclipse environment - so my Debug configuration settings are as per on their webpage.

My setup is using a SEGGER jlink JTAG debugger unit in conjunction with the Yagarto toolchain (latest version from their website).

I have been told the following ...
This is a bug with the Yagartos plug-in or the SEGGER jlink JTAG debugger unit.
The platform debugger does not provide any specific debuggers, but instead provides a framework for creating debuggers. The tooling you mentioned are providing a plug-in for Eclipse that is not working correctly - as you have shown. This is not a problem with the platform, but is instead a problem with the provider of the Yagartos plug-in (or the SEGGER jlink JTAG debugger unit)
Previous Topic:Help: CDT + MinGW no run configurations
Next Topic:Console Input under windows / use windows console
Goto Forum:

Current Time: Sat Jun 23 20:17:01 GMT 2018

Powered by FUDForum. Page generated in 0.01595 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top