diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_before_you_begin.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_before_you_begin.htm index 8b21275f550..ceedc3ac684 100644 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_before_you_begin.htm +++ b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_before_you_begin.htm @@ -33,13 +33,13 @@ MinGW produces native Windows executables that do not require a separate runtime @@ -342,7 +342,7 @@ may contain other information.

DSF Integration

DSF (Eclipse Debugger Services Framework) integrated. See DSF features for more information. + href="https://www.eclipse.org/dsdp/dd/development/relnotes/dd_news-1.1.html">DSF features for more information. @@ -364,7 +364,7 @@ may contain other information.

Bugs fixed

Bugs fixed in this release: - + CDT 6.0 bug fixes @@ -393,7 +393,7 @@ may contain other information.

CDT 5.0 includes new features in Editor, Call Hierarchy, Refactoring, Indexer, Projects & Build, and Debug.

-See What's New in CDT 5.0 on the CDT Wiki for more information including screen shots. +See What's New in CDT 5.0 on the CDT Wiki for more information including screen shots.

Highlights include: @@ -460,7 +460,7 @@ See What's New in CDT 5.0

CDT 8.0 - New and Noteworthy

CDT 7.0 - New and Noteworthy

CDT 6.0 - New and Noteworthy

-

CDT 5.0 - New and Noteworthy

+

CDT 5.0 - New and Noteworthy

diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_70.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_70.htm index 8afa6c73da8..1c63d395f04 100644 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_70.htm +++ b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_70.htm @@ -16,7 +16,7 @@ tr {vertical-align: top;}

CDT 7.0 - New and Noteworthy

-

See What's new in CDT 7.0 on the CDT wiki +

See What's new in CDT 7.0 on the CDT wiki which may contain more recent information.

@@ -75,7 +75,7 @@ which may contain more recent information.

Code Analysis

@@ -274,19 +274,19 @@ which may contain more recent information.
  • DSF-GDB. The default debugger for the CDT is now using a different debugging framework and is called DSF-GDB. It provides better support for newer GDB versions, such as 6.7, 6.8 and 7.x, for older versions you would have to edit preferences to use the old framework (CDI) by default. See full list of DSF-GDB features - here. + here.
  • GDB Tracepoints are now supported. See the - wiki page. Available in DSF-GDB only. + wiki page. Available in DSF-GDB only.
  • Reverse Debugging which allows to undo execution. Requires GDB 7.0 or newer and only available on Linux. Available in DSF-GDB only. - A webinar on the topic is available here. + A webinar on the topic is available here.
  • Run To Line feature now allows to run to any line in the program, instead of only lines within the same method.
  • Pretty Printing feature of GDB is supported. Requires GDB 7.0 or newer as well as python, and GDB's python pretty-printers. - Some information available here. + Some information available here.
  • Interrupts on Windows platform while debugging application got improved support.
    • @@ -341,7 +341,7 @@ which may contain more recent information.

    CDT 8.0 - New and Noteworthy

    CDT 7.0 - New and Noteworthy

    CDT 6.0 - New and Noteworthy

    -

    CDT 5.0 - New and Noteworthy

    +

    CDT 5.0 - New and Noteworthy

    Back to Top diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_80.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_80.htm index 6da5fda9814..c766f4ac3db 100644 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_80.htm +++ b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_80.htm @@ -16,7 +16,7 @@ tr {vertical-align: top;}

    CDT 8.0 - New and Noteworthy

    -

    See What's new in CDT 8.0 on the CDT Wiki +

    See What's new in CDT 8.0 on the CDT Wiki which may contain more recent information.

    New code analysis framework is introduced, called Codan. See this - wiki for details. + wiki for details.

    Codan

     
    @@ -191,13 +191,13 @@ which may contain more recent information. @@ -266,7 +266,7 @@ which may contain more recent information.

    Furthermore, for an attach session (local or remote), there is even no need to specify the binary; for a local attach, GDB can find the binary automatically, while for a remote attach, CDT will prompt for it when it needs it.

    Image:Noprojectdebug.png

    -

    This feature was completed April 26th, 2011 as part of Bug 343861 +

    This feature was completed April 26th, 2011 as part of Bug 343861

    @@ -281,7 +281,7 @@ which may contain more recent information.


    With pretty-printing:

    Image:FullPrettyPrint.png

    -


    This feature has been contributed by Jens Elmenthaler to CDT 8.0 as of November 4th, 2010, as part of Bug 302121 +


    This feature has been contributed by Jens Elmenthaler to CDT 8.0 as of November 4th, 2010, as part of Bug 302121


    Configuring GDB for pretty-printing:

    @@ -322,7 +322,7 @@ end

    By using the enhancements of GDB 7.1, DSF-GDB now shows the core on which each thread runs as an extra part of the Debug View label. The list of all cores on which a process is located is also added as a label. The below image shows the new feature.

    Image:CoreLabels.png

    -

    This feature has been implemented for CDT 8.0 as of July 6th, 2010, as part of Bug 318230. The feature will be enabled automatically as long as GDB 7.1 or greater is used. +

    This feature has been implemented for CDT 8.0 as of July 6th, 2010, as part of Bug 318230. The feature will be enabled automatically as long as GDB 7.1 or greater is used.

    @@ -333,7 +333,7 @@ end @@ -345,7 +345,7 @@ end

    Variables, Expressions, Registers, Disassembly, and Memory Browser now supports opening multiple instances, and pin the view input to the selected debug context(s) in the Debug view. This can be used, for example, to easily compare the data of different threads.

    Image:PinCloneDebug.png

    -

    This feature has been implemented for CDT 8.0 as of Feb 15th, 2011, as part of Bug 327263, Bug 331781, and Bug 334566. +

    This feature has been implemented for CDT 8.0 as of Feb 15th, 2011, as part of Bug 327263, Bug 331781, and Bug 334566.

    @@ -410,7 +410,7 @@ end


    The values of most of these preferences will be used to populate the corresponding entries of the Debugger tab, whenever a new launch is created.

    Image:LaunchDefaultGdb.png

    -


    This feature has been implemented for CDT 8.0 as as part of Bug 120162, Bug 347245 and Bug 335895. +


    This feature has been implemented for CDT 8.0 as as part of Bug 120162, Bug 347245 and Bug 335895.

    @@ -460,37 +460,37 @@ end

    DSF-GDB

    @@ -548,7 +548,7 @@ end

    CDT 8.0 - New and Noteworthy

    CDT 7.0 - New and Noteworthy

    CDT 6.0 - New and Noteworthy

    -

    CDT 5.0 - New and Noteworthy

    +

    CDT 5.0 - New and Noteworthy

    Back to Top diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_81.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_81.htm index 25ceb216557..d925b09073e 100644 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_81.htm +++ b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_81.htm @@ -11,7 +11,7 @@

    CDT 8.1 - New and Noteworthy

    -

    See What's new in CDT 8.1 on the CDT Wiki +

    See What's new in CDT 8.1 on the CDT Wiki which may contain more recent information.

    @@ -70,7 +70,7 @@

    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.

    Image:Pin view call hierarchy.png -

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

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


    Filtering in Outline Views

    @@ -91,8 +91,8 @@


    Indexing

    -
    • The "C-Build console" is now named "CDT Build Console" -
    • It is now possible to open the CDT Build Console before performing a build. See bug 320765. Note that operations on the console will require the user to first select a project. The below screenshot shows the new access to the CDT Build Console. +
    • It is now possible to open the CDT Build Console before performing a build. See bug 320765. Note that operations on the console will require the user to first select a project. The below screenshot shows the new access to the CDT Build Console.

    Image:CDTConsoleStart.jpg

    -
    • "CDT Global Build Console" got introduced. This console combines output from all referenced projects being built in one view. See bug 309113. +
      • "CDT Global Build Console" got introduced. This console combines output from all referenced projects being built in one view. See bug 309113.

      Image:CDTGlobalBuildConsole.jpg

      -
      • Differentiate color highlighting in build output for error, warning and info problem markers. See bug 307211. +
        • Differentiate color highlighting in build output for error, warning and info problem markers. See bug 307211.

        Image:Bug 307211.png
    -

    When a breakpoint is set in a dynamically-linked library that was not loaded yet, the breakpoint will now work, once the library is loaded. See bug 248595. This feature is currently only supported when using GDB 6.8 or later. +

    When a breakpoint is set in a dynamically-linked library that was not loaded yet, the breakpoint will now work, once the library is loaded. See bug 248595. This feature is currently only supported when using GDB 6.8 or later.

    DSF-GDB now shows the owner of a process as an extra part of the process prompt for an attach session. The owner id will be shown starting with GDB 7.0. For a Remote attach session (using gdbserver --multi), the cores on which a process is located will also be shown. Showing the cores starts with GDB 7.1. The below image shows the new feature.

    Image:UserAndCores.jpg

    -

    This feature has been implemented for CDT 8.0 as of July 30th, 2010, as part of Bug 318230 comment 21. The feature will be enabled automatically as long as the proper version of GDB is used. +

    This feature has been implemented for CDT 8.0 as of July 30th, 2010, as part of Bug 318230 comment 21. The feature will be enabled automatically as long as the proper version of GDB is used.

    -
    1. The interface org.eclipse.cdt.dsf.mi.service.command.output.MIListThreadGroupsInfo.IThreadGroupInfo has four new methods. See bug 318230 comment 21 +
      1. The interface org.eclipse.cdt.dsf.mi.service.command.output.MIListThreadGroupsInfo.IThreadGroupInfo has four new methods. See bug 318230 comment 21
        • String getUser()
        • String getType()
        • String getCores()
        • String getExecutable()
        -
      2. The interface org.eclipse.cdt.dsf.gdb.service.command.IGDBControl has a new method: List<String> getFeatures(). See bug 322658 +
      3. The interface org.eclipse.cdt.dsf.gdb.service.command.IGDBControl has a new method: List<String> getFeatures(). See bug 322658
      4. The interface org.eclipse.cdt.dsf.gdb.service.command.IGDBControl no longer has the three methods: start(...), restart(...) and canRestart(...). Those methods are moved to org.eclipse.cdt.dsf.gdb.service.IGDBProcesses and have a new signature.
      5. org.eclipse.cdt.dsf.gdb.service.command.GDBControl and org.eclipse.cdt.dsf.gdb.service.command.GDBControl_7_0 no longer implement the five methods: start(...), restart(...), canRestart(...), startOrRestart(...), useContinueCommand(...) which are now implemented in org.eclipse.cdt.dsf.gdb.service.command.GDBProcesses and org.eclipse.cdt.dsf.gdb.service.command.GDBProcesses_7_0 -
      6. All the constructors of class org.eclipse.cdt.dsf.mi.service.command.commands.MIBreakInsert now take an extra parameter at the end of the parameter list: boolean allowPending. When this parameter is set to true, -break-insert will be used with the -f option, which asks GDB to make the breakpoint pending if the installation fails. This flag can only be enabled for GDB >= 6.8. See bug 248595 -
      7. The interface org.eclipse.cdt.dsf.debug.service.IProcesses.IMIProcesses has a new method: IMIContainerDMContext createContainerContextFromGroupId(...). See bug 317500 +
      8. All the constructors of class org.eclipse.cdt.dsf.mi.service.command.commands.MIBreakInsert now take an extra parameter at the end of the parameter list: boolean allowPending. When this parameter is set to true, -break-insert will be used with the -f option, which asks GDB to make the breakpoint pending if the installation fails. This flag can only be enabled for GDB >= 6.8. See bug 248595 +
      9. The interface org.eclipse.cdt.dsf.debug.service.IProcesses.IMIProcesses has a new method: IMIContainerDMContext createContainerContextFromGroupId(...). See bug 317500
      10. The file of constants org.eclipse.cdt.dsf.gdb.internal.ui.preferences.IGdbDebugPreferenceConstants has been removed. It was deprecated and had already been replaced by org.eclipse.cdt.dsf.gdb.IGdbDebugPreferenceConstants -
      11. The interface org.eclipse.cdt.dsf.mi.service.IMIRunControl has a new method: IRunMode getRunMode(). See bug 334463 +
      12. The interface org.eclipse.cdt.dsf.mi.service.IMIRunControl has a new method: IRunMode getRunMode(). See bug 334463
      13. FinalLaunchSequence has dramatically changed.
      14. GdbLaunch#addInferiorProcess() is removed.
      15. GDBControl.InferiorInputOutputInitStep is removed.
      16. GDBControl_7_0.InferiorInputOutputInitStep is removed. -
      17. The interface IMIRunControl has the new method isTargetAcceptingCommands() as part of Bug 339047 -
      18. IGDBControl, GDBControl and GDBControl_7_0, no longer have the three methods: initInferiorInputOutput(), createInferiorProcess() and getInferiorProcess() as part of Bug 237308 -
      19. MIInferiorProcess's constructors have changed, and many of its public methods are removed (getState(), getPid(), setPid(), etc) as part of Bug 237308 -
      20. CommandFactory#createMIInferiorTTYSet() has changed signature as part of Bug 237308 -
      21. The constructor to MIInferiorTTYSet has changed signature as part of Bug 237308 -
      22. IGDBProcesses gets the new method attachDebuggerToProcess() as part of Bug 237306 +
      23. The interface IMIRunControl has the new method isTargetAcceptingCommands() as part of Bug 339047 +
      24. IGDBControl, GDBControl and GDBControl_7_0, no longer have the three methods: initInferiorInputOutput(), createInferiorProcess() and getInferiorProcess() as part of Bug 237308 +
      25. MIInferiorProcess's constructors have changed, and many of its public methods are removed (getState(), getPid(), setPid(), etc) as part of Bug 237308 +
      26. CommandFactory#createMIInferiorTTYSet() has changed signature as part of Bug 237308 +
      27. The constructor to MIInferiorTTYSet has changed signature as part of Bug 237308 +
      28. IGDBProcesses gets the new method attachDebuggerToProcess() as part of Bug 237306
      29. GdbInferiorProcess no longer exists. Its base class, MIInferiorProcess should be used directly. -
      30. GDBBackend.doInitialize(), GDBControl.doInitialize() and GDBControl_7_0.doInitialize() are now private. Having them as public was a bug that would break versioning of the service. See Bug 341465 +
      31. GDBBackend.doInitialize(), GDBControl.doInitialize() and GDBControl_7_0.doInitialize() are now private. Having them as public was a bug that would break versioning of the service. See Bug 341465
      32. GDBControlDMContext no longer implements IBreakpointsTargetDMContext or IDisassemblyDMContext. Although not an API breaking change it has significant impacts. Mostly that code such as 
      (IBreakpointsTargetDMContext)fCommandControl.getContext() // Will fail with an Invalid Cast exception
 (IDisassemblyDMContext)fCommandControl.getContext() // Will fail with an Invalid Cast exception
      -

      will now fail because the command control context is no longer an IBreakpointsTargetDMContext/IDisassemblyDMContext. Instead, MIContainerDMC now implements IBreakpointsTargetDMContext/IDisassemblyDMContext. This change was necessary to fully support multi-process and was done in bug 335324 and bug 344298. +

      will now fail because the command control context is no longer an IBreakpointsTargetDMContext/IDisassemblyDMContext. Instead, MIContainerDMC now implements IBreakpointsTargetDMContext/IDisassemblyDMContext. This change was necessary to fully support multi-process and was done in bug 335324 and bug 344298.

    Contents

    • 1 Editor @@ -62,56 +62,56 @@

      Organize Includes Command

      The Organize Includes command is similar to Organize Imports in Java. It adds missing include statements, removes unnecessary ones, and reorders includes according to user preferences.

      Image:OrganizeIncludes.png -

      When determining which header files must be included the Organize Includes command follows the "Include What You Use" rule. See Why Include What You Use? and What Is a Use?. +

      When determining which header files must be included the Organize Includes command follows the "Include What You Use" rule. See Why Include What You Use? and What Is a Use?.

      Build

      Console

      -
      • Line wrap option on the console (Bug 199605). +

        Image:ConsoleWrapLine.png Image:ConsoleWrapLinePreference.png

        Improved toolchain detection

        -
        • Automatic detection of MinGW 64 bit (Bug 380598). -
        • Detection of Visual Studio under Windows 7 64 bit (Bug 385608). -
        • Recognize $PATH environment variable from workspace preferences for MinGW and Cygwin toolchains (Bug 384520). -
        • Introduction of environment variables $MINGW_HOME and $CYGWIN_HOME that are recognized in preferences and project properties (Bug 403257, Bug 357442). +
          • Automatic detection of MinGW 64 bit (Bug 380598). +
          • Detection of Visual Studio under Windows 7 64 bit (Bug 385608). +
          • Recognize $PATH environment variable from workspace preferences for MinGW and Cygwin toolchains (Bug 384520). +
          • Introduction of environment variables $MINGW_HOME and $CYGWIN_HOME that are recognized in preferences and project properties (Bug 403257, Bug 357442).

          Image:MINGW_HOME.png Image:CYGWIN_HOME.png

          Scanner Discovery / Language Settings Providers

          -
          • "Preprocessor Include Paths, Macros etc." property page now fully replaces older "Scanner Discovery" page. "Scanner Discovery" is now hidden by default (Bug 403405, Bug 407087). +
            • "Preprocessor Include Paths, Macros etc." property page now fully replaces older "Scanner Discovery" page. "Scanner Discovery" is now hidden by default (Bug 403405, Bug 407087).

            Image:PropertyPageSettingsScannerDiscovery.png

            -
            • Built-in Compiler Settings provider for MinGW is enabled by default now for MinGW toolchain (Bug 382422). -
            • Added Built-in Compiler Settings provider for Cygwin (Bug 382423). +
              • Built-in Compiler Settings provider for MinGW is enabled by default now for MinGW toolchain (Bug 382422). +
              • Added Built-in Compiler Settings provider for Cygwin (Bug 382423).

              Image:CygwinProvider.png

              -
              • Project-relative include paths representation was stabilized and now officially supported in UI (Bug 401734). -
              • Support for project-relative paths for Build Output Providers (Bug 402023). -
              • Changes in environment variables (preferences or project properties - as applicable) automatically trigger re-discovery (Bug 403406). -
              • Number of changes to support compatibility with older methods to provide include paths for indexer, namely pathEntryContainers, contributed ScannerInfo entries (Bug 401961, Bug 398056, Bug 392966). -
              • Fixed compatibility issues related to import older projects (Bug 393641). +
                • Project-relative include paths representation was stabilized and now officially supported in UI (Bug 401734). +
                • Support for project-relative paths for Build Output Providers (Bug 402023). +
                • Changes in environment variables (preferences or project properties - as applicable) automatically trigger re-discovery (Bug 403406). +
                • Number of changes to support compatibility with older methods to provide include paths for indexer, namely pathEntryContainers, contributed ScannerInfo entries (Bug 401961, Bug 398056, Bug 392966). +
                • Fixed compatibility issues related to import older projects (Bug 393641).

                Makefile Editor

                -
                • GNU Makefile functions highlighting fixed (Bug 406911). -
                • Bracket matching (Bug 405279). +

                  Image:MakeEditorBracketMatching.png

                  -
                  • Content assist for automatic variables (Bug 407169). +
                    • Content assist for automatic variables (Bug 407169).

                    Image:MakeEditorContentAssistAutoVars.png

                    -
                    • Highlight for conditional variable assignment (Bug 406596). -
                    • Proper colorization of escaped # (Bug 404599). +
                      • Highlight for conditional variable assignment (Bug 406596). +
                      • Proper colorization of escaped # (Bug 404599).

                      Misc

                      -
                      • Ability to specify local includes for indexer, as in [#include "header.h"] as opposed to system includes [#include <header.h>] (Bug 388368). -
                      • Fixed some bugs related to storing environment variables, such as silently ignoring removals or additions (Bug 348781, Bug 355488). -
                      • Improved performance in certain areas (Bug 405643, Bug 405638, Bug 405744, Bug 407483). -
                      • User documentation for Scanner Discovery updated including property page "Preprocessor Includes, Macros" (Bug 409392). +
                        • Ability to specify local includes for indexer, as in [#include "header.h"] as opposed to system includes [#include <header.h>] (Bug 388368). +
                        • Fixed some bugs related to storing environment variables, such as silently ignoring removals or additions (Bug 348781, Bug 355488). +
                        • Improved performance in certain areas (Bug 405643, Bug 405638, Bug 405744, Bug 407483). +
                        • User documentation for Scanner Discovery updated including property page "Preprocessor Includes, Macros" (Bug 409392).

                        Debug

                        Enhanced Expressions

                        @@ -144,7 +144,7 @@ var1; =$e* -- Will show a group containing variable var1 as well as all registe

                        This feature allows to quickly define multiple expressions that interest the user. Because groups are created from these special expressions, they can be collapsed when uninteresting and re-expanded later, without having to be re-entered by the user.

                        Image:CDT GroupExpr.png -

                        This feature was completed on July 10th, 2012 and updated for local variables on December 19th, 2012. For details see Bug 381754 and Bug 394408. +

                        This feature was completed on July 10th, 2012 and updated for local variables on December 19th, 2012. For details see Bug 381754 and Bug 394408.

                        Note that the comma (,) is not allowed as a group separator as it is used within valid expressions that use templates (e.g., ((((((class std::_Vector_base<int, std::allocator<int> >) v))._M_impl))._M_start)).

                        OS Resources View

                        @@ -206,7 +206,7 @@ Kernel modules - Listing of all loaded kernel modules

                        Floating Point renderer has been added to the memory package

                        A floating point render has been added to the memory package. So now there is the Traditional renderer and a Floating Point renderer available. This render allows display and editing of the floating point values. Since it originated from the Traditional render, it's workflow and style are similar. There is no ASCII data pane display, since this did not seem to make much sense with floating point data.

                        Image:CDT FloatingPointMemory.png -

                        This feature was completed on November 16th, 2012 as part of Bug 394509. +

                        This feature was completed on November 16th, 2012 as part of Bug 394509.

                        Debugging multiple processes within one debug session

                        Debugging a new executable in the same debug session has been improved for GDB versions starting from 7.2. "Debug New Executable" action has been added to the context menu of the Debug view. @@ -288,7 +288,7 @@ Building on the enhanced selection, it's now also possible to filter what is sho

                        See bugzilla report Bugs Fixed in CDT 8.2. Open this report in new browser window.

                        - +

                        What's new in other CDT releases

                        @@ -298,7 +298,7 @@ Open this report in new browser window.

                        CDT 8.0 - New and Noteworthy

                        CDT 7.0 - New and Noteworthy

                        CDT 6.0 - New and Noteworthy

                        -

                        CDT 5.0 - New and Noteworthy

                        +

                        CDT 5.0 - New and Noteworthy

                        Back to Top

                        diff --git a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_83.htm b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_83.htm index 165a0ac85a7..76997a20ba1 100755 --- a/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_83.htm +++ b/debug/org.eclipse.cdt.debug.application.doc/concepts/cdt_c_whatsnew_83.htm @@ -11,11 +11,11 @@

                        CDT 8.3 - New and Noteworthy

                        -

                        See What's new in CDT 8.3 on the CDT Wiki +

                        See What's new in CDT 8.3 on the CDT Wiki which may contain more recent information.

                        - +

                        Contents

                        Build

                        Toolchains

                        -
                        • Language dialect options in GNU toolchain definition (Bug 404913). +
                          • Language dialect options in GNU toolchain definition (Bug 404913).

                          DialectLanguageStandard.png

                          Scanner Discovery/Language Settings Providers

                          -
                          • Use applicable options (such as language dialect) from build settings during discovery of built-in settings (Bug 404913). But note that to use options changed by user the built-in settings provider needs to be set as non-shared.
                            +
                            • Use applicable options (such as language dialect) from build settings during discovery of built-in settings (Bug 404913). But note that to use options changed by user the built-in settings provider needs to be set as non-shared.

                            BuiltInDetectors-FLAGS.png

                            @@ -76,47 +76,47 @@

                            Debug

                            Threads displayed by creation order in the Debug view

                            -

                            For a multi-threaded program, the different threads are now shown in the order they were created during execution. Not only is that order more intuitive, it allows for the selection in the Debug view to be more stable. This enhancement was completed on January 13th, 2014. For details see Bug 412547. +

                            For a multi-threaded program, the different threads are now shown in the order they were created during execution. Not only is that order more intuitive, it allows for the selection in the Debug view to be more stable. This enhancement was completed on January 13th, 2014. For details see Bug 412547.

                            CDT ThreadOrder.png



                            Support for multi-process debugging in Memory views

                            -

                            The Memory view and Memory Browser view now support multi-process debugging. Beyond properly refreshing their content based on the currently selected process, the user can now define different memory addresses to look at for each process being debugged. This work was a contribution from Alvaro Sanchez-Leon on January 15th, 2014. For details see Bug 250323. +

                            The Memory view and Memory Browser view now support multi-process debugging. Beyond properly refreshing their content based on the currently selected process, the user can now define different memory addresses to look at for each process being debugged. This work was a contribution from Alvaro Sanchez-Leon on January 15th, 2014. For details see Bug 250323.

                            CDT MemMultiProcess.png



                            Enhanced support for multi-process debugging in Registers view

                            -

                            The Registers view now supports debugging processes with a different set of registers. For example, the registers of the selected process will properly be displayed when debugging both a 32-bit process and a 64-bit process. This work was a contribution from Alvaro Sanchez-Leon on September 29th, 2013. For details see Bug 418176. +

                            The Registers view now supports debugging processes with a different set of registers. For example, the registers of the selected process will properly be displayed when debugging both a 32-bit process and a 64-bit process. This work was a contribution from Alvaro Sanchez-Leon on September 29th, 2013. For details see Bug 418176.

                            CDT RegMultiProcess1.png CDT RegMultiProcess2.png



                            Register view is now stack-frame-specific

                            -

                            The Registers view will now update each time a different stack-frame is selected. The view will show the content of the registers as they were for the selected frame, when the method call was done which caused the creation of the next stack-frame. This work was a contribution from Alvaro Sanchez-Leon on September 27th, 2013. For details see Bug 323552. +

                            The Registers view will now update each time a different stack-frame is selected. The view will show the content of the registers as they were for the selected frame, when the method call was done which caused the creation of the next stack-frame. This work was a contribution from Alvaro Sanchez-Leon on September 27th, 2013. For details see Bug 323552.

                            CDT RegisterStack1.png CDT RegisterStack2.png



                            Basic support of Multicore Visualizer in all-stop mode

                            -

                            The Multicore Visualizer now displays properly in all-stop mode, with all its features available when the program is suspended, while still updating thread creation/termination when the program is running. This enhancement was completed on August 15th, 2013. For details see Bug 409965 +

                            The Multicore Visualizer now displays properly in all-stop mode, with all its features available when the program is suspended, while still updating thread creation/termination when the program is running. This enhancement was completed on August 15th, 2013. For details see Bug 409965


                            Variable substitution for GDB command file path

                            -

                            It is now possible to use eclipse variables within the specified path of the GDB command file. This allows to have project-specific GDB command files. For example ${project_loc}/project.gdbinit. This feature was completed July 23rd, 2013. For details see Bug 413373 +

                            It is now possible to use eclipse variables within the specified path of the GDB command file. This allows to have project-specific GDB command files. For example ${project_loc}/project.gdbinit. This feature was completed July 23rd, 2013. For details see Bug 413373

                            CDT GdbinitVarSubstitution.png



                            Project-less debugging is now supported on the Windows platform

                            -

                            Project-less debugging now works as expected on Windows. This enhancement was completed on August 10th, 2013. For details see Bug 344470 +

                            Project-less debugging now works as expected on Windows. This enhancement was completed on August 10th, 2013. For details see Bug 344470


                            Detection of target disconnection

                            -

                            When doing remote debugging, if the connection to the target is lost, the debug session will be cleanly terminated. Previously, some situations could lead to a debug session that lost its connection but remained active using the host machine instead; these cases have been fixed. This enhancement was completed on January 8th, 2014. For details see Bug 422586 +

                            When doing remote debugging, if the connection to the target is lost, the debug session will be cleanly terminated. Previously, some situations could lead to a debug session that lost its connection but remained active using the host machine instead; these cases have been fixed. This enhancement was completed on January 8th, 2014. For details see Bug 422586

                            Qt Support (preview)

                            Work continues on CDT's support for Qt. For CDT 8.3, this includes the following. Note that we still consider this a preview release until CDT 8.4 where we'll clean up usability issues around setting up CDT to work with Qt and hopefully some better qmake and QML support. @@ -139,7 +139,7 @@

                            Bugs Fixed in this Release

                            See bugzilla report Bugs Fixed in CDT 8.3

                            - +

                            What's new in other CDT releases

                            @@ -150,7 +150,7 @@

                            CDT 8.0 - New and Noteworthy

                            CDT 7.0 - New and Noteworthy

                            CDT 6.0 - New and Noteworthy

                            -

                            CDT 5.0 - New and Noteworthy

                            +

                            CDT 5.0 - New and Noteworthy

                            Back to Top