Changes made to IDE 4.7

Application Profiler:

The cheat sheet for the Application Profiler example was renamed from “QNX Example Application Profiling Project” to “Call Count and Sampling Profiling”, and a few other updates were made to the instructions to reflect changes made to the user interface.

The Time column was renamed to Deep Time and the Own Time column was renamed to Shallow Time (see Interpreting Tree mode column information by profiling type.

Code Coverage:

Information was added to describe how to instrument a static library with code coverage enabled; you either have to instrument your binary with code coverage, or link with the code coverage library using the -lgcov option (see How the coverage tool works).
Many Code Coverage topics were changed with updated feature information (see Using Code Coverage.
In the section “There are multiple ways to import a file” in the topic Importing gcc code coverage data from a project, references to .da were updated to .gcda to reflect the gcc files that the IDE currently supports.

Debugging:

By default, pdebug now sets LD_BIND_NOW to 1 to force the loading of all lazy-load dependencies. You can prevent pdebug from setting LD_BIND_NOW by specifying the new -l (“el”) option. For more information about lazy binding, see the Compiling and Debugging chapter in the Neutrino Programmer's Guide.
Updates were made to the JTAG Abatron architecture images and corresponding documentation for hardware and software configuration (see Using JTAG debugging, Connecting the Abatron BDI2000 Debugger to your host, Connecting the Abatron BDI2000 Debugger to your target, and Building a system image in the IDE User's Guide.

Memory Analysis:

For the mallopt() function, we've renamed MALLOC_FILLAREA to MALLOC_CKBOUNDS, and we've added more information about the MALLOC_CKALLOC, MALLOC_DUMP_LEAKS, MALLOC_EVENTBTDEPTH, MALLOC_FREE_CHECK, MALLOC_START_TRACING, MALLOC_STATS, MALLOC_TRACEBTDEPTH, MALLOC_TRACEMAX, MALLOC_TRACEMIN, MALLOC_TRACING, and MALLOC_VERIFY_ON options (see mallopt in the Neutrino Library Reference).
The Memory Events, Memory, Memory Backtrace, and Memory Problems views are now independent views that aren't included in the Sessions view.
The Trace Details and Statistics views have been removed. The functionality that these views provided is now available by using the filters on the Memory Events view (to obtain the same data).
Although you can continue to use libmalloc_g.so, use librcheck.so to obtain memory statistics.
More information was added to the documentation about timelines (see Timeline view in the IDE User's Guide).
The cheat sheet for Memory Analysis was renamed to “Memory Analysis Tooling”, and the cheat sheet instructions were updated to reflect the changes made to the user interface.
In the documentation for the IDE User's Guide, the Finding Memory Errors chapter was renamed to “Analyzing Memory Usage and Finding Memory Errors.” In addition, the topics in this chapter were reordered and modified for technical accuracy; many of the topic titles were renamed as well.
Now, the Memory Analysis Tooling views support grouping and search (see Memory Problems view and Memory Events view), column preferences (see Memory Problems Preferences and Memory Events Preferences), and filtering (see Memory Problems Filter and Memory Events Filter).
The instructions to import memory analysis data were improved (see Importing memory analysis data and Performing a postmortem memory analysis).
You can now configure memory analysis settings for a running program from the Settings tab (available from the Memory Analysis editor).
The documented steps to attach to a running process in order to analyze memory events and traces for a running process were updated (see Attaching to a running process.
We've added a warning in the documentation regarding the use of Mudflap together with Memory Analysis. If your binary is instrumented with Mudflap, you can't run Memory Analysis on it because there'll be a conflict (trying to overload the same functions), and it will cause the program to crash (see Using Mudflap).

Migration:

We've updated our platform support for this release. For a target OS, the IDE is compatible with targets that run QNX Neutrino. For a host OS, you can now use the IDE with any of the following development hosts (we don't include the IDE on self-hosted QNX Neutrino systems):
- Microsoft Windows 7 Professional 32- and 64-bit, Vista Business 32- and 64-bit, XP Professional SP3, or 2000 SP4
- Linux Red Hat Enterprise Linux 5.4 Desktop 32- and 64-bit, Red Hat Fedora 12, Ubuntu Workstation 9.10 32- and 64-bit, or openSUSE 11.2
You can also use the QNX Neutrino RTOS as a virtual machine on VMware Workstation 6.5 or 7.0, VMware Player 3.0, and Microsoft VirtualPC 2007. We provide a VMware image of a runtime installation of QNX Neutrino. If you intend to use the IDE on VMware, to ensure that VMware is supported for your host, search the compatibility guide located at http://www.vmware.com/resources/compatibility/search.php .
A new topic called Binary compatibility was created in the chapter Migrating from Earlier Releases to contain a summary of all binary compatibility issues.
Various important migration topics were updated in the IDE User's Guide. For the latest migration information for this release, see these updated migration topics:
The QNX Momentics Tool Suite lets you install and work with multiple versions of Neutrino (from 6.2.1 and later). Whether you're using the command line or the IDE, you can choose which version of the OS to build programs for. As a result, various migration topics in the documentation were also updated to help you with your migration tasks.
Note: Only versions of Momentics with different medial version numbers can coexist. For example, 6.3.2 can coexist with 6.2.1, but not with 6.3.0. However, 6.4.0 can coexist with 6.4.1 and 6.5.0. Coexistence with 6.2.1 is supported only on Windows hosts. For more information about migration and coexistence, see Migrating from Earlier Releases .
Previously, if you start the IDE, it uses your current qconfig choice as the default version of the OS. Now, the IDE uses the last installed version of the QNX software that appears in the Select Install list on the Global QNX Preferences page. For more information about coexistence and setting this option, see Coexistence.

By default, IDE 4.7 now stores its files in the following locations:

Type of file	Default location
Workspace folder	$HOME/ide-4.7-workspace
.metadata folder (for personal settings)	$HOME/ide-4.7-workspace/.metadata
Error log	$HOME/ide-4.7-workspace/.metadata/.log

System Builder:

The feature to build a System Builder EFS Project type was temporarily removed from the IDE. However, the documentation was updated to include instructions about how to create an EFS project. You'll need to follow the workaround instructions found in Creating a new QNX System Builder project for an OS image in the IDE User's Guide.

System Profiler:

A new Thread Call Stack view displays the current thread call stack at a given point in time for all instrumented threads. When you profile an application with function instrumentation, the profiler records function enter and function exit events, and uses events to determine the stack at any point in a program. For more information about this feature, see Thread Call Stack view.
The instructions for the System Profiler cheat sheet were updated to reflect the changes made to the user interface.

General:

In the chapter Launch Configurations Reference in the IDE User's Guide, documentation was added to Types of launch configurations to describe the new Group Launch configuration (see Launch Group type), as well as some clarification made to the other launch configuration types.
Documentation was added to describe how to disable the default editor setting that automatically performs syntax annotation highlighting in the editor (see Disabling automatic syntax annotation highlighting).
After installing, your desktop now includes an icon for the QNX Momentics IDE 4.7.
Many reference links in the IDE User's Guide were updated to go to more specific places in the guide.
Created a new troubleshooting topic to answer some common IDE questions you might have (see Troubleshooting in the IDE).
In the Developing C/C++ Programs chapter in the IDE User's Guide, the following changes were made:
- Many of the topics were reordered (see “ Developing C/C++ Programs ”.
- The Running projects was renamed to Running binaries for a project (see Running binaries for a project.
Added information about using the -configuration option (to re-direct the configuration to the shared install area from the command line) to the topic “ Updating the IDE using the Software Updates Manager ” in the IDE User's Guide.
For PhAB projects, the following variant types aren't supported: ARM v7, MIPS, and PPC SPE.
Documentation was added to describe the steps required to import a QNX BSP into the IDE (see “ Tutorial 4: Importing a QNX BSP into the IDE ”.
An important reference link was added to the topic QNX Momentics IDE User's Guide > Understanding and Analyzing Memory > Using memory analysis > Using a file to log the trace to the Heap Analysis chapter in the QNX Neutrino Programmer's Guide because it contains important information.
In the IDE User's Guide, the Using Mudflap documentation was moved from Debugging in the IDE > Using Mudflap to Analyzing Memory Usage and Finding Errors > Finding memory errors and leaks > Using Mudflap.
Documentation was created to describe how to import a BSP into the IDE (see Tutorial 4: Importing a QNX BSP into the IDE).
The steps in the Tutorial 1: Creating a C/C++ project were updated to reflect the changes made to the user interface.
In the Developing C/C++ Programs chapter, various changes were made to some their names and to their order in the chapter.
A new chapter called Project and Wizard Properties Reference was created. This chapter contains descriptions for the project and wizard reference pages.
A new chapter called IDE Administration was created. This chapter contains valuable information about how to administer some of the key aspects of the IDE.