- Fixed Issues
- Code Coverage C++ - v2002 Release 2/1964 Instrumentation of ternary expressions
- Code Coverage C++ And C - v2002 Release 2/1892 Unable to load fdc file
- Code Coverage C++ - v2002 Release 2/1875 Goto labels in switch cases produces compilation errors after instrumentation
- Memory Profiling C++ And C - v2002 Release 2/1989 SIGBUS of the instrumented application when memory optimization compilation option is used
- Memory Profiling C++ And C - v2002 Release 2/1958 Adding the atl_multi_threaded=1 option to the CC and CCP macros hangs BaseStation_C
- Memory Profiling C++ - v2002 Release 2/1889 The instrumentor attolccp terminates abnormally when the option -mempro is used
- Performance Profiling C - 2002.05.20/1855 Application under memory profiling analysis crashes when using -DUMPRETURNING option
- Memory Profiling C++ - 2002.05.20/1850 Bad generation of code by the instrumentor when Memory Profiling is engaged
- Runtime Analysis C++ - v2002 Release 2/1994 When opening the coverage report, only the report browser window can be seen
- Runtime Analysis C++ - v2002 Release 2/1972 With the -pedantic option gcc 2.96 errors on malloc and free not having the same prototype
- Runtime Analysis Java - v2002 Release 2/1914 When a very large classpath is used the error "Arg too large" occurs
- Runtime Analysis C++ And C - v2002 Release 2/1905 attolcc does not instrument the source code when the compiler option -MD is specified
- Runtime Analysis C++ - v2002 Release 2/1887 Instrumentor does not accept "friend T;" when T is a template
- Runtime Tracing C++ - v2002 Release 2/1977 Problem when instrumenting with implicit copy constructor
- Runtime Tracing C++ - v2002 Release 2/1973 With runtime tracing, copy constructors are created for unions which do not compile with GNU 2.96
- Studio C - v2002 Release 2/1999 Studio environment variable ($$NODENAME, $$NODEPATH, $$TARGETDIR, ...) in a external command does not work
- Studio All - 2002.05.20/1883 After "Stop" for a running build process, the message "Build completed" is shown.
- Studio All - v2002 Release 2/1865 Studio remains blocked a while after finishing the build process
- Target Deployment Port C++ And C - v2002 Release 2/1969 "__builtin_constant_p" is not recognized by the instrumentor
- Target Deployment Port C++ And C - v2002 Release 2/1970 Setting a long ENV_PATH in tp.ini or tpcpp.ini causes STATUS_ACCESS_VIOLATION
- Target Deployment Port C - v2002 Release 2/1910 Instrumentation errors when using variable arguments: __builtin_stdarg_start" is undefined
- Target Deployment
Port C++ - v2002 Release 2/1909 Instrumentation errors when using variable
arguments: __builtin_stdarg_start" is undefined
- Known Issues
- Documentation N/A - 2002.05.00/1018 (-) License Administration Guide refers to Rational Suite
- Runtime Analysis C++ - v2002 Release 2/2008 (-) When the options -g3 -Werror is used on the compiler, the instrumented code no longer compiles
- Studio Java - v2002 Release 2/1983 (-) Selective instrumentation does not set the package name of the class for exclusion
- Studio All - v2002 Release 2/1957 (-) Save icon greyed out after moving around project browser
- Studio Java - v2002 Release 2/1552 (-) Runtime tracing report for Java application references classes not located within the application
- Trace C++ - 2002.05.00/1165 (2002) The
by default sequence diagram printing functionality does not work correctly
Scope
What's New in This Release
Fixed Issues
This section describes the whole set of noteworthy fixed problems in the 2002.05.21 release.
Code Coverage
C++ - v2002 Release 2/1964 Instrumentation of ternary expressions
In some cases, instrumented code of ternary expressions does not compile.
Code Coverage
C++ And C - v2002 Release 2/1892 Unable to load fdc file
A gap between comment line in fdc file causes the problem. This error appears only on Windows. Error : While analyzing, syntax error near /BRANCH [.\AMMCSCRIPTPARSER_ACTOR.fdc:10784] While analyzing, syntax error near /BRANCH [.\AMMCSCRIPTPARSER_ACTOR.fdc:10791] While analyzing, syntax error near SHORTCUT [.\AMMCSCRIPTPARSER_ACTOR.fdc:11810] While analyzing, syntax error near /COMMENT [.\AMMCSCRIPTPARSER_ACTOR.fdc:11810] While analyzing, syntax error near SHORTCUT [.\AMMCSCRIPTPARSER_ACTOR.fdc:11811
Code Coverage C++
- v2002 Release 2/1875 Goto labels in switch cases produces compilation
errors after instrumentation
Goto labels inside switch blocks are placed inside another block by the
instrumentor. The compiler cannot compile this correctly and reports a syntax error.
Example:
int foo::goto_error(int x, char*s, char *s1) {
switch (x) {
case 1:
goto Where;
case 2:
x++;
goto Where;
case 3:
// int y; /*as a workaround uncomment this */
Where:
x+10;
if (strcmp(s, s1)!=0) {
cout << "we will, we will, fix this...";
}
}
return(x+10);
}
Memory Profiling
C++ And C - v2002 Release 2/1989 SIGBUS of the instrumented application
when memory
optimization compilation option is used
Memory optimization often implies use of non aligned data that can create a problem when trying to detect memory leaks.
Memory Profiling
C++ And C - v2002 Release 2/1958 Adding the atl_multi_threaded=1 option
to the CC and CCP macros
hangs BaseStation_C
When running the base station example on RedHat Linux 7.2 2.4.7-10smp after adding the
--atl_multi_threaded=1 to the instrumentor, the program that is generated does not run
to completion. Under the debugger it stops in __sigsuspend. This is due to a nested mutex lock that provokes a deadlock.
Memory Profiling
C++ - v2002 Release 2/1889 The instrumentor attolccp terminates abnormally
when the option -mempro is used
The instrumentor attolccp terminates abnormally when the option -mempro is used.
Performance Profiling
C - 2002.05.20/1855 Application under memory profiling analysis crashes
when using -DUMPRETURNING option
When running an application instrumented with the option DUMPRETURNING, the application crashes during the trace dump.
Memory Profiling C++ - 2002.05.20/1850
Bad generation of code by the instrumentor when Memory Profiling is engaged
With a C++ code the instrumentor generates bad C++ code which contains incorrect positioning of brackets. Error like : nrl.cpp nrl.cpp: Instrumenting... nrl.cpp: Compiling... nrl.aug.cpp C:\Clients\Elektrobit\PbCoverageCPP\nrl.cpp(24) : error C2226: syntax error : unexpected type 'std::complex' Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8168 for 80x86 Copyright (C) Microsoft Corp 1984-1998. All rights reserved.
Runtime Analysis
C++ - v2002 Release 2/1994 When opening the coverage report, only the
report browser window can be seen
When opening the coverage report, only the navigator window can be seen because it is too big.
Runtime
Analysis C++ - v2002 Release 2/1972 With the -pedantic option gcc 2.96
errors on malloc and free not having the same prototype
With the -pedantic option, gcc 2.96 errors on malloc and free not having the same prototype.
They should throw exceptions but the overloaded functions provided in the Target Deployment
Port do not throw exceptions.
Runtime
Analysis Java - v2002 Release 2/1914 When a very large classpath is
used the error "Arg too large" occurs
When a very large classpath is used, the error "Arg too large" occurs.
Runtime Analysis
C++ And C - v2002 Release 2/1905 attolcc does not instrument the source
code when the compiler option -MD is specified
attolcc does not instrument the source code when the compiler option -MD is specified. Example attolcc -- gcc -MD -c toto.c
Runtime Analysis
C++ - v2002 Release 2/1887 Instrumentor does not accept "friend T;"
when T is a template
Instrumentor does not accept "friend T;" when T is a template
Example:
template <class T>
class X : public Y
{
friend T;
};
Runtime Tracing
C++ - v2002 Release 2/1977 Problem when instrumenting with implicit
copy constructor
There is a problem in the runtime tracing feature with implicit copy constructors.
The following error message is given: ':: ' is not an immediate base class of ' :: '
Runtime Tracing
C++ - v2002 Release 2/1973 With runtime tracing, copy constructors
are created for unions
which do not compile with GNU 2.96
With runtime tracing, copy constructors are created for unions which do not compile with GNU 2.96
as all elements of the union were copied.
Studio C - v2002 Release
2/1999 Studio environment variable ($$NODENAME, $$NODEPATH, $$TARGETDIR,
...)
in a external command does not work
Creating a 'External Command' using the Studio environment variable like $$NODENAME, $$NODEPATH,
$$TARGETDIR, $$BINDIR, ... does not work. Example : External Command = "cmd /c dir $$NODEPATH"
Studio
All - 2002.05.20/1883 After "Stop" for a running build process, the
message "Build completed" is shown.
After "Stop" for a running build process, the message "Build completed" is shown.
Studio
All - v2002 Release 2/1865 Studio remains blocked a while after finishing
the build process
This only occurs with projects referencing a big number of files. Studio is checking for intermediate files (perl.exe continues to run in the background).
Target
Deployment Port C++ And C - v2002 Release 2/1969 "__builtin_constant_p"
is not recognized by the instrumentor
When instrumenting, the following error message occurs:
P+Linux attolccp: "/usr/include/asm/spinlock.h", line 168: error #20:
identifier "__builtin_constant_p" is undefined
"__builtin_constant_p()" is a function that is built into the compiler so it
does not have a prototype, hence the error message
Target
Deployment Port C++ And C - v2002 Release 2/1970 Setting a long ENV_PATH
in tp.ini or tpcpp.ini causes
STATUS_ACCESS_VIOLATION
STATUS_ACCESS_VIOLATION raised during Runtime Analysis activity creation if ENV_PATH variable
in TDP ini files set too long.
Target Deployment
Port C - v2002 Release 2/1910 Instrumentation errors when using variable
arguments:
__builtin_stdarg_start" is undefined
When instrumenting source code that uses variable argument macros va_arg() etc. The following errors occur: P+Linux attolcc1 - ERROR: syntax error near int [va_arg.c,12] P+Linux attolcc1: Cannot recover from earlier errors ... P+Linux attolcc - The following command-line caused an error: attolcc1 /tmp/_atc_51_22800.i /tmp/_atc_53_22800.c atct.def -bloc -proc=ret -mempro -perfpro -trace -COMMENT= Preprocessing command: gcc va_arg.c -g -O0 -Wall -pedantic -E>tmp-file P+Linux attolcc clinuxgnu - ERROR: Error during code instrumentation
Target Deployment
Port C++ - v2002 Release 2/1909 Instrumentation errors when using variable
arguments:
__builtin_stdarg_start" is undefined
When instrumenting source code that uses variable argument macros va_arg() etc. The following errors occur:
P+Linux attolccp: "va_arg.cpp", line 9: error #20: identifier
"__builtin_stdarg_start" is undefined
__builtin_stdarg_start((ap),numArgs);
^
P+Linux attolccp: "va_arg.cpp", line 11: error #254: type name is not allowed
Total += __builtin_va_arg (ap, int);
^
P+Linux attolccp: "va_arg.cpp", line 11: error #20: identifier
"__builtin_va_arg" is undefined
Total += __builtin_va_arg (ap, int);
^
P+Linux attolccp: "va_arg.cpp", line 13: error #20: identifier
"__builtin_va_end" is undefined
__builtin_va_end (ap);
^
P+Linux attolccp - FATAL ERROR: Syntax and/or semantic errors in source file, in
strumentation cancelled
Known Issues
Documentation
N/A - 2002.05.00/1018 (-) License Administration Guide refers to Rational
Suite
The License Administration Guide document provided with the product refers to Rational Suite, but in fact also applies to Rational Test RealTime as well as other Rational Software products.
Runtime Analysis
C++ - v2002 Release 2/2008 (-) When the options -g3 -Werror is used
on the compiler,
the instrumented code no longer compiles
The option -g3 results in the #defines remaining in the .i file. It also causes the predefined defines "__DATE__", "__TIME__" etc to be redefined at the beginning of the file. After instrumentation the compilation of the instrumented file results in some warning of the following type: file.c:0:warning: `__DATE__' redefined The option -Werror converts the warning to an error and the compilation stops.
Work-Around :
There are 2 workarounds but both require modification of the compilation flags: 1. Don't use -g3, use -g2 or even simpler -g 2. Don't use -Werror in this case the redefinition warning is no longer an error and the compilation will continue.
Studio Java - v2002 Release
2/1983 (-) Selective instrumentation does not set the package name
of the class for exclusion
When you exclude an unit from instrumentation in Java, it is necessary to add manually the package name. For example, you want to exclude from the instrumentation the UmtsServer Class: Setting / Runtime Analysis / General Runtime Analysis / Selective Instrumentation Selective Unit Instrumentation = UmtsServer is proposed automatically. You must add manually the package name. Selective Unit Instrumentation = package_name.UmtsServer So, in this case the correct setting to enter is: Selective Unit Instrumentation = baseStation.UmtsServer
Work-Around :
Set manually the package name before the class name for exclusion.
Studio All - v2002 Release
2/1957 (-) Save icon greyed out after moving around project browser
When editing a file the save icon becomes accessible. If another file is selected in the asset browser then the save icon becomes inaccessible. It is then difficult to save the modifications in the file.
Work-Around :
1. Click 'x' or right-click the file tab and select close. A dialog appears asking if the file should be saved. Obviously, the file must be re-opened to continue editing. 2. Create a second tab, either by opening another file or raising the Start page (ctrl+alt+r). Move between the tabs and the Save icon is reset.
Studio Java - v2002 Release
2/1552 (-) Runtime tracing report for Java application references classes
not located within the application
JVMPI classes are not filtered in the runtime tracing report. This affects all runtime tracing reports other than the one that is dynamically generated during application execution.
Work-Around :
JVMPI is only used by the memory profiling feature. When memory profiling is not performed, the JVMPI classes will not appear in a runtime tracing report.