Download Intel(R) C++ Software Development Tool Suite 2.0.1 Professional

Intel(R) C++ Software Development Tool Suite 2.0.1 Professional, Release Notes
If compiled with DEBUG flag set, the function myinit calls myinit_text which can be debugged in source
code.
Accessing the Kernel modules code
The Linux* 2.6 protects the access of the kernel modules if these are not used. So the code and the data of a
kernel module can not be viewed if these are not activated.
Impact, when the access to the modules is disallowed:
●
●
●
The “Module List” window can not be updated.
Setting software breakpoints in kernel modules is no more possible. In this case, it is necessary to use hardware
breakpoints and modify it to a software breakpoint when a hit occurs.
NOTE: The software breakpoints which were set into a kernel module remain valid.
The debug information of kernel modules can not be relocated. One solution to get the debug information of the
kernel modules relocated is to stop and continue the target just after the return of the function
sys_init_module and sys_delete_module. This can be performed using a special watchpoint on the
module list mutex:
SET WATCHPOINT /ACCESS=WRITE /LENGTH=4 AT &module_c$$1\\module_mutex.count
CONTINUE HARD 0
Starting debugging
The only changes between the Linux* 2.4 and 2.6 support for the usage is the additional watchpoint which needs to
be setup in the startup script (use the configuration file xdb\configurations\jtaglinux\jtaglinux26.xsf
which include this watchpoint)
The Linux plugin itself detects if the Linux 2.4 or 2.6 is debugged according the debug information file.
Symbian OS* v8.1b/v9 Build and Debug Support
A new command line option for the Intel® C++ Compiler and Intel® Linker, -platform=symbian, allows
creation of Symbian OS* DLLs and executables.
The Intel® XDB JTAG Debugger allows debugging of Symbian OS* v8.1b and v9 code generated by GNU or
ARM* RealView2.0/2.1 for Symbian OS* v8.1b/v9.
Access for Unloaded Modules in Palm OS*
Setting breakpoints in unloaded modules is now supported when debugging Palm OS*.
Debug Information Compatibility for GDB
A new compiler option -Qvariable_locations- can be used to improve compatibility of the debug information
when interpreted by GDB. This option is recommended only when GDB is used for debugging instead of the Intel®
XDB Debugger.
Example: ccxsc -Od -Qvariable_locations- -Zi test.c
FLEXlm* License Protection for Intel® XDB JTAG Debugger/Simulator
The installation process will check for the existence of a valid FLEXlm* license file, regardless of whether the
file:///C|/Documents and Settings/pdarling/Local Settings...Internet Files/OLK135/Product Release Notes_CS-023435.htm (17 of 47)11/8/2006 2:26:36 PM