What's new in IDE 4.5?#

Platform#

• Eclipse platform 3.3.1.1 Release Notes What is new in 3.3
• CDT 4.0.2

C/C++ Development#

• The new QNX launch and debug shortcut adopt to the new CDT launch and debug framework. It is enhanced to have the ability to detect and associate binaries to remote targets architecture. It is more user friendly since it does most of the works to fill in enough information in the launch configuration, and only requires user attention to the launch configuration dialog while multiple choices are available.
• Added converter from QNX Projects to Managed Make Projects
• A managed build integration for the QNX tool chain
• QDE Debugger now has an option "Verbose console mode" that shows details of interaction with command line debugger in gdb process console. This option can be enabled from launch configuration or by right clicking on the process in debug view.
• GDB breakpoints actions page called "GDB Command Action" is added to the "breakpoint actions" property dialog box. This allows you to enter GDB commands - one command per line. Now you can define GDB command action and attach it to one or more breakpoints. When the breakpoint is hit, the defined GDB command(s) will run and the result will be shown in the GDB console. There is also a new global preference "GDB Command Action" page accessible from "Windows -> Preferences -> C/C++ -> Debug -> Breakpoint Actions". This preference page allows you to define one of more reusable GDB command actions that can be attached to a breakpoint later.
• Several major fixes connected to QNX container projects have been made:
  • speed of container project import was increased
  • resolved problem of workspace consistency after re-import of container project
  • fixed the workspace refresh problem after container project import (sometimes IDE did not refresh project view without restarting or even showed root container only (without components)) .
  • fixed the problem when the order of components in container project (and the build order) after import was wrongly changed.
  • fixed deadlock during the import operation for container project.

System Information#

• The QNX System Information enhancements with malloc information view that include various charts to help you observe changes in memory usage (allocations and deallocations). Because it is important for you to know when and where memory is being consumed within an application, the Memory Analysis Tooling feature includes several views that use the trace information from the Memory Analysis session to help extract and visually display this information (to determine memory usage; allocation and deallocation metrics). The IDE includes these new views to help you observe changes in memory over time: Outstanding allocations, Allocation deltas, Deallocation deltas, and Outstanding allocation deltas. To access these views, select "Window"-->"Show View"-->"Other" from the menu in the IDE, and then select "QNX System Information"-->"Malloc Information", and click "OK".
  • Note: For you to begin to view data on your graphs, you need to set logging for the target, and you need to select an initial process from the Target Navigator view.

Memory Analysis#

• The Memory Analysis Tool lets you import and export trace data from a Memory Analysis session view. With the Memory Analysis Tool, you can:
  • Export session information in CSV or XML format. In the IDE, you can export your trace data session information from a Memory Analysis session view. When exporting memory analysis information, the IDE lets you export results in .csv format or in .xml format. Later, you can import the event-specific results into a spreadsheet, or you can choose to import session data back into a Memory Analysis tool to review the results. To export, click "File"-->"Export" from the menu, and then select "QNX"-->"Memory Analysis Data".
  • Import memory analysis sessions from trace file or XML format. In the IDE, you can import memory events and memory errors from a Memory Analysis session view. When importing memory analysis session information, the IDE lets you import from libmalloc trace file (generated on the target), or from previously exported session data in XML format. To import, click "File"-->"Import" from the main menu, select "QNX"-->"Memory Analysis Data", and then follow the wizard instructions.nl

System Profiler#

• The Summary display will now show additional information about the dropped buffers if any are observed in the log file

• The Event Log will now use the DATE information in the log file and provide a 'real time' column to the log display. This can be adjusted or re-baselined in the project property ... also the icons have returned to the Event Log view after a long absence

• A new Event Log view has been created that allows users to see the entire log file contents without the "segmented" display of the older Log view. This is accessible via the Window > Show View > Other ... > QNX System Profiler > Ful Trace Eventl Log

Old Log View	Full Log View

• The export of log file data can be made into a CSV file. This is possible if you try and cut/paste a large selection from the Full Trace Event Log view or as a right click option on the *.kev file System Profiler > Export as CSV data

• User event labels are now visible at any zoom level (they are no longer affected by 'pixelization') and are also configurable at both a per-logfile and global basis. This is an initial cut of the interface for selecting the event data. Feedback is welcome