Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDT/User/NewIn84"
(→Tooltip support in Multicore Visualizer) |
(→Debug) |
||
| Line 4: | Line 4: | ||
== Debug == | == Debug == | ||
| + | |||
| + | === Dynamic-printf === | ||
| + | |||
| + | CDT now supports the concept of dynamic-printf as provided by GDB. Using a dynamic-printf gives you the effect of inserting a printf call into your program on-the-fly, without having to recompile it or restart it. | ||
| + | |||
| + | '''Limitations to be aware of:''' | ||
| + | * Adding a dynamic-printf to a tight loop can cause major degradation of Eclipse's performance. This is because Eclipse will be receiving a message each time the dynamic-printf will be hit, which will happen extremely often in a tight loop. We are working at improving this. | ||
| + | * If GDB is not able to directly call 'printf' from within your program, the dynamic-printf output will not go the same location as normal printf output; instead it will be sent to the gdb console of Eclipse. We have seen this on some versions of Ubuntu 32bit. | ||
| + | |||
| + | Note that a Dynamic-printf can also be added from the Disassembly view. | ||
| + | |||
| + | This feature was completed May 1st, 2014 through [http://eclip.se/400628 Bug 400628]. | ||
=== Showing return value of method after a step-return === | === Showing return value of method after a step-return === | ||
Revision as of 15:20, 2 May 2014
Contents
Build
Indexing
Debug
Dynamic-printf
CDT now supports the concept of dynamic-printf as provided by GDB. Using a dynamic-printf gives you the effect of inserting a printf call into your program on-the-fly, without having to recompile it or restart it.
Limitations to be aware of:
- Adding a dynamic-printf to a tight loop can cause major degradation of Eclipse's performance. This is because Eclipse will be receiving a message each time the dynamic-printf will be hit, which will happen extremely often in a tight loop. We are working at improving this.
- If GDB is not able to directly call 'printf' from within your program, the dynamic-printf output will not go the same location as normal printf output; instead it will be sent to the gdb console of Eclipse. We have seen this on some versions of Ubuntu 32bit.
Note that a Dynamic-printf can also be added from the Disassembly view.
This feature was completed May 1st, 2014 through Bug 400628.
Showing return value of method after a step-return
CDT will now show the return value of a method call (if there is one) following a step-over operation. This value will be shown as the first element of the Variables view. This feature was completed February 13th, 2014 through Bug 341731.
Trace Control view enhancements
The Trace Control view has gotten a new look which is much more graphical. It aims at making the view easier to use, to understand, and to provide information quickly.
The below screenshot shows the new view while a trace experiment is running:
This screenshot shows the new view while examining the result of a tracing experiment:
For more details on tracing an application see this trace FAQ section. This work was a contribution from Dmitry Kozlov on February 5th, 2014. For details see Bug 390827.
Change breakpoint type
Breakpoint type is now an editable property. CDT will allow changing breakpoint type to Regular/Hardware/Temporary/Hardware Temporary from breakpoint property page. Breakpoint type can also be specified when adding a new breakpoint with "Add Breakpoint ..." action.
The feature has been completed on February 24th, through Bug 427898
Opcodes in Disassembly View
CDT will now show opcodes in the disassembly view when "Show Opcodes" is active.
This work was a contribution from William Riley on March 31st, 2014. For details see Bug 357270.
Tooltip support in Multicore Visualizer
The Multicore Visualizer now has tooltips available, when using the mouse to hover over a stopped thread. It will show available information about that thread, like source code file / line, function name, address.
This work was a contribution from Xavier Raynaud on April 11th, 2014. For details see Bug 431935.
General
CDT 8.4 requires JRE 1.7 or higher to run.