Jump to: navigation, search

Difference between revisions of "CDT/User/NewIn81"

< CDT
m (Edit Breakpoint on Create)
m (Edit Breakpoint on Create)
Line 116: Line 116:
 
*# This brings up the function breakpoint properties dialog.   
 
*# This brings up the function breakpoint properties dialog.   
 
*# User must enter the function expression.
 
*# User must enter the function expression.
 +
  
 
[[Image:Cdt_n_and_n_8_1-add_breakpoint_dialog.png]]
 
[[Image:Cdt_n_and_n_8_1-add_breakpoint_dialog.png]]

Revision as of 12:00, 19 March 2012

Debug

Multicore Visualizer View

CDT now optionally includes a Multicore Visualizer View. This view displays a graphical representation of the state of the current application. It allows one to click- and drag-select groups of processes/threads, and apply debugging commands to them directly from the visualizer. Selections made in the Visualizer View are reflected automatically in the Debug View, and vice versa. The Multicore Visualizer View is designed to scale to large numbers of cpus and cores-per-cpu on both current and future multicore hardware.

The Multicore Visualizer View is meant to serve as a high-level visual overview of the current application, and can be used in tandem with the Debug View, which provides more in-depth detail.

The Multicore Visualizer View is just one example of a visualizer based on the underlying Visualizer Framework plugin. This provides a pluggable, extensible platform for developing visual development tools of this kind.

VisualizerSnapshot.png

Note that the Multicore Visualizer will only work using a Linux target; it will not work debugging on a Windows or Mac target. This is a current limitation of GDB which does not provide information about cores, for those targets (at writing, GDB is at version 7.4).

This feature was completed on February 10th, 2012. For details see Bug 335027

The Multicore Visualizer is an optional feature of the CDT and must be installed manually. The feature is called "C/C++ Multicore Visualizer". Installing it will install both the Multicore Visualizer and the Visualizer Framework. If you only want to install the Visualizer Framework (to build your own visualizer), you can install that feature by itself; it is called "CDT Visualizer Framework".

Advanced character encoding support

CDT now supports the handling of different character encodings for strings and wide character strings while debugging. This includes full support for Unicode encodings and many other popular encodings as well. You can select the character and wide character encoding within the Debug preferences.

DebugPreferences.png

CDT will then correctly display strings according to the selected encoding while debugging.

CharsetDebug.png

Note that this feature requires GDB version 7.0 or later. This feature was completed on March 7th, 2012 as part of Bug 307311, Bug 367456 and Bug 370462.

Partitioning of large arrays

CDT now displays large arrays as collections of partitions.

LargeArray.png

This feature was completed on January 26th, 2012 as part of Bug 365541

Multi-select attach dialog

CDT now allows selecting more than one process to attach to in a single user operation. The bottom pane is used to see which processes have been selected. If multi-process debugging is not supported with your debug session (needs GDB >= 7.2 and NonStop enabled), only the first process will be attached to.

Multiselect.png

This feature was completed June 30th, 2011 as part of Bug 293679

Default Postmortem file location

CDT now allows the user to specify a default directory for the location of core files for a postmortem launch when the prompt is triggered. Since a postmortem launch can easily be re-used for different core files of the same binary, this feature helps reduce the amount of navigation needed to select a core file. Note that specifying the actual core file is still supported, as well as leaving the entire field blank, which will also trigger the prompt, but use the default directory for its starting location.

Note that this 'core file' field supports the use of variables such as ${workspace_loc}.

This feature applies to both core files and trace files.

CorePath.png

This feature was completed on February 17th, 2012 as part of Bug 362039

Support for Fast Tracepoints

CDT now allows the user of fast tracepoints, as supported by GDB. Fast tracepoints use an instruction jump instead of a trap for efficiency. Fast tracepoint need a minimum of space to be inserted in the program and therefore, may fail to be set at certain locations. For fast tracepoints to work, a special library called the in-process agent (IPA), must be loaded in the inferior process. This library is built and distributed as an integral part of gdbserver. Please see the GDB documentation for more details.

The user can select between three tracepoint modes in the launch:

  1. Fast: Only use fast tracepoints. No tracepoint will be planted if a fast tracepoint cannot be used.
  2. Slow: Only use slow tracepoints.
  3. Automatic: Attempt to use fast tracepoints. If a fast tracepoint cannot be used, automatically use a slow tracepoint.

FastTracepointSelection.png

This feature was completed July 20th, 2011 as part of Bug 346320

Enhancements to Tracepoints

With the use of GDB 7.4, some new features are available within Eclipse.

  • Live enable/disable of C/C++ Tracepoints
    • Tracepoints can now be enabled and disabled at any time after a trace experiment has been started, and will immediately take effect within the ongoing experiment.
    • Note: Although GDB 7.4 seems to allow a tracepoint to be created during a trace experiment and will add it to the ongoing experiment, this behavior seems to have some issues. One of which is that deleting a tracepoint during an experiment will not remove that tracepoint from the ongoing experiment. Until this is fixed in GDB, it is recommended that the user stick to enable/disable operations during a tracing experiment.
  • Smaller Fast tracepoints
    • On 32-bit x86-architectures, fast tracepoints can now be placed at locations with 4-byte instructions, when they were previously limited to locations with instructions of 5 bytes or longer.
  • Tracepoint collecting of Strings
    • The tracepoint Collect action now takes an optional modifier "/s" to indicate that a string should be collected, when appropriate. It effectively dereferences pointer-to-character types and collects the bytes of memory up to a zero byte. An optional integer directly following the "/s" (no space in between) sets a bound on the number of bytes that will be collected. This "/s" modifier must be added manually by the user as in the screenshot below. However, we plan an incorporating this in Eclipse in a graphical way.

CollectString.png

Support for octal number format in CDI

CDI now also supports to use the octal number format to display the contents of variables, expressions and registers. You can select the octal number format within the Debug preferences. This feature was completed on March 7th, 2012 as part of Bug 370462.


Edit Breakpoint on Create

It is no longer necessary to first create a CDT breakpoint, then edit its properties. Properties such as enabled, ignore count, condition, temporary, can be set while creating the breakpoint.

There are several methods to open the properties dialog before creating the breakpoint:

  • Add Breakpoint... action.
    1. In the editor or the disassembly view, bring up the popup menu on the gutter.
    2. Select the "Add Breakpoint..." menu item.
    3. This brings up the breakpoint properties dialog for a line breakpoint pre-filled with the breakpoints location.
  • Control-Double Click
    1. Hold the Control key while double-clicking on the editor gutter.
    2. This brings up the breakpoint properties dialog for a line breakpoint pre-filled with the breakpoints location.
  • Control key with Toggle Method Breakpoint
    1. Open the editor's Outline view.
    2. Right-click on a method to bring up the popup menu.
    3. Hold the control key while selecting the Toggle Method Breakpoint action.
    4. This brings up the function breakpoint dialog pre-filled with the method name.
  • Add Watchpoint (C/C++)
    1. In the Breakpoints view, open the view menu.
    2. Select the "Add Watchpoint (C/C++)"... action.
    3. This brings up the watchpoint properties dialog.
    4. User must enter the watchpoint expression.
  • Add Function Breakpoint (C/C++)
    1. In the Breakpoints view, open the view menu.
    2. Select the "Add Function Breakpoint (C/C++)"... action.
    3. This brings up the function breakpoint properties dialog.
    4. User must enter the function expression.


Cdt n and n 8 1-add breakpoint dialog.png

Image: The breakpoint properties dialog for a line breakpoint about to be created.

Breakpoint Toggle Short-Cuts

The Toggle Breakpoint action in the editor and disassembly view menu now supports new behaviors when used with modifier keys:

  • Hold the *Shift* key while double-clicking on an existing breakpoint in order to enable or disable the breakpoint.
  • Hold the *Control* key while double-clicking on an existing breakpoint in order to bring up the breakpoint properties dialog to edit the existing breakpoint.
  • Hold the *Control* key while double-clicking on a location with no breakpoints, in order to bring up the breakpoint properties dialog to create a new breakpoint.

Cdt n and n 8 1-editor gutter menu.png

The editor gutter popup menu with the hints for the new accelerators.

Function Breakpoint Manual Entry

Editor

Pin the Call Hierarchy View

The Call Hierarchy View can now be pinned which enables the user to open multiple Call Hierarchy views at the same time.

Pin view call hierarchy.png

This feature was completed November 12th, 2011 as part of Bug 342498


Codan

External-tool-based Checkers

The main motivation for integrating Codan with external tools is to enjoy all the code checks from mature tools without leaving Eclipse. With the new infrastructure:

  1. External tools can be configured using Codan’s preference page
  2. External tools are invoked automatically when a C/C++ file is saved
  3. The output of these tools can be displayed as editor markers

The new infrastructure includes a checker that invokes Cppcheck. This checker is disabled by default but it can be easily enabled and configured in the Codan preference page.

Cppcheck-config-1.png

A more detailed configuration dialog can be found by pressing the “Customize Selected…” button:

Cppcheck-config-2.png

Users can specify the path of the Cppcheck executable, the arguments to pass and whether Cppcheck’s output should be displayed in the console.

A demo of this checker can be found here.

The new infrastructure makes it very easy to write your own external-tool-based checker. In the simplest case, you will need to:

  • Extend the abstract class AbstractCxxExternalToolBasedChecker.
  • Provide the name of your tool (e.g. "Cppcheck".)
  • Provide default values for the path of the executable, arguments to pass and whether the output of the tool should be displayed in the console.
  • Provide one or more implementations of AbstractOutputParser. They will parse the output of the external tool, line by line. It’s up to you to decide what to do with the output (e.g. create error markers.)

In the case of tools that are complex to set up, the new infrastructure is extremely flexible and configurable. It allows you to pretty much to configure every single aspect of the checker, from the files that the tool can check to the way to feed arguments to the tool.