Rational Test RealTime Release Notes

Updated : 25-Jul-2002 Version v2002 Release 2

Scope

What's New in This Release

Scope

A description of newly fixed problems,
A description of known problems.

Note: The title for Fixed Issues or Known Issues follows the following format:

Feature (Language)-(Version which contains the problem)/(defect number) (Title of Defect)

When contacting support for any issues, please specify the products full version number: 2002.05.20.468.004

What's New in This Release

General Updates

Rational Test RealTime now supports the Java language. You can use Test RealTime to perform runtime analysis and component testing of your Java code developed for the Java 2 Platform, Micro Edition, or the Java 2 Platform, Standard Edition.
The Target Deployment Technology has been enhanced. Target Deployment Port (.xdp files) from the previous release will be automatically updated when opened with the Target Deployment Port Editor. The new Target Deployment Port can still be used with the previous version of Test RealTime.
All Target Deployment Ports can now be edited by the Target Deployment Port Editor. They are all using the same .xdp file format.
The Rational Test RealTime add-in for Rational Rose RealTime has been enhanced to better support large and complex UML models. Please, note that this integration is only available for C++ language.
Test Template Generators are now called Code Parsers and generate metric information as well as test script templates.
C and C++ component testing now provides the ability to import data from external files for data-driven testing. Data files (.csv), associated with Test RealTime test nodes, are automatically converted by the build process into standard C/C++ header files and subsequently linked to the test driver. With this functionality, a developer can define test data outside of Test RealTime while continuing to benefit from the optimized performance that comes from compiling this data into the test harness. To get more information about this functionality, have a look at the User Guide, in the section Graphical User Interface>Working with Projects>Importing a Data Table.
Test RealTime feature names have been retired and replaced as follows:
- PurifyLT: memory profiling
- QuantifyLT: performance profiling
- Coverage: code coverage analysis
- Trace: runtime tracing
- Unit Testing for C/Ada: component testing for C/Ada
- Object Testing: component testing for C++
- System Testing: system testing for C

Rational Test RealTime now supports Java

Rational Test RealTime now provides the following features for the Java language:
- memory profiling
- performance profiling
- code coverage analysis
- runtime tracing
- component testing for Java

Rational Test RealTime supports J2ME (Java 2 Platform, Micro Edition) and J2SE (Java 2 Platform, Standard Edition).
The instrumentors for Java can be easily integrated with Apache Ant. You can find more information about this in the folder “/lib/java/ant”.

Rational Test RealTime User Interface Updates

Rational Test RealTime projects (.rtp files) have replaced the concept of a workspace (.rtw files) with the concept of a child project. Projects from the previous release (v2002) will be automatically updated when loaded by this new release.
Static metrics are now displayed in a separate report and are no longer part of the code coverage report. They are computed/updated when a file is added to the current project, when a file is saved after modification or when the project browser is refreshed.
If you have a very limited display resolution or colormap on your Unix workstation, you can use the “qtconfig” tool to modify the default display settings of the user interface.
You can easily import Test RealTime v2001A Unit Testing project, session and campaign files. This option is available in the File menu of the user interface. It will create a project with all the settings required to have a ready-to-run project.

C and C++ Instrumentor Updates

New advanced options are available to configure the instrumentation of your C or C++ source code. For more details, take a look at the reference manual or use the following command: « attolcc --help »
Microsoft Visual C Structured Exception Handling is now supported by the instrumentor for the C language.
The instrumentor options « -purifylt » and « -quantifylt » are deprecated, but still supported. If used, an information message is displayed. The options « -mempro » and «-perfpro » should be used instead.
The instrumentor options « -service » and « -exservice » are deprecated. The options « -unit » and « -exunit » should be used instead.
New static metrics are computed by the code parsers. The metrics previously computed the instrumentors are now deprecated. It is still possible to get those metrics from the instrumentors by using the « -metrics » option.
The option « -force_tdp_cc » forces the compilation of the Target Deployment Port source file « tdp.c » or « tdp.cpp » with the current target deployment port options. By default, the C++ version « tdp.cpp » is compiled. To force the compilation of the C version « tp.c », the environment variable ATL_FORCE_C_TDP has to be set to the value “on”. And therefore, the environment variable ATL_FORCE_CPP_TDP is no longer used.
The new option « -noinclude » for the C instrumentor lets you choose to not instrument any included header files (« .h »), thus only compiling source code files (« .c »).
The new option «-noinspect=extern» turns off the inspection of extern global variables by the memory profiling feature. Each global variable will be inspected in the source file where it is actually declared. This option can be used to prevent linker errors.
If the environment variable « ATL_NO_TDP_COMPILE » is set, the target deployment port source file « tdp.c » will not be compiled by the instrumentor. This option is useful when the Target Deployment Port needs to be a shared library. In that case, you should provide the library containing the Target Deployment Port on the link command-line or use the environment variable « ATL_SHARED_TDP » to give the file path to this shared library containing the precompiled Target Deployment Port.
The new option “-nostop” instructs the instrumentation launcher “attolcc” to continue the compilation process even if the instrumentation has not been achieved on the source file. If the instrumentation fails, the non-instrumented source file is compiled. When this option is used, the file “attolcc.log” contains the list of files that have not been instrumented and the reason why.
The new option ‘-ignore= instructs the instrumentation launcher “attolcc” not to instrument the files given in the comma separated list. When trying to match these file names and the one found on the compilation command-line after --, path is ignored: only base-name are compared; Note that this option, unlike the -exfile option of the instrumentors, does not launch the preprocessing and instrumentation stages.

Ada Instrumentor Updates

Static metrics are now computed by the code parser. The metrics previously computed by the instrumentors are now deprecated. It is still possible to get those metrics from the instrumentors by using the « -metrics » option.

Fixed Issues

This section describes the whole set of noteworthy fixed problems in the v2002 Release 2 release.

All Observation C - 2002.05.20/1544 Code generated by instrumentor produces warning/errors for GNU-QNX compiler

When a function returns a value that is the result of a call to another function and compares it to another value, 
the instrumentor does not calculate the return type of the expression correctly resulting in a compilation error 
when the instrumented code is compiled. Example:


extern void*getElement();
int elementExists()
{
  return (getElement()!=NULL);
}


In this case the instrumentor thinks that the type of the expression returned is of type void* instead of int.

All Observation C - 2002.05.20/1543 GNU-QNX analysis issues

1) An enum declared in a structure is not accepted.
2) Trouble with types which become local variables inside a function and which have to persist as types after 
   function's return.
3) A ; followed by another ; is not accepted in a struct/union

All Observation C - 2002.05.01/1428 The instrumentor does not handle open parenthesis correctly in extension function calls

When using the -O2 option on the gnu compiler the strchr() function is expanded
to an inline macro using the __extension__ GNU keyword. If character parameter
to strchr() is a parenthesis, '(' or ')', then the __extension__ keyword is not
analyzed correctly by the instrumentor resulting in the following error message:

gcc -E -O2 a.c > a.i
attolcc1 a.i a.aug.c atct.def -PROC -COUNT
TestRT attolcc1 - WARNING: Non terminated gnu __extension__ beginning at [a.c,7]
TestRT attolcc1 - ERROR: syntax error near  [a.c,12]
TestRT attolcc clinuxgnu - ERROR: Error during code instrumentation

Coverage C++ - 2002.05.20/1777 Invalid storage class for a mutable parameter

atostart supports now "mutable" keywords.

Coverage C++ - 2001A.04.01/1744 Covered code line shown in red in report

A line of code after a switch statement is shown in red, although covered.

Coverage C++ - 2001A.04.01/1710 A 'goto' used in code causes a problem to the instrumentation and the coverage report
is not correct

The 'goto' keyword used in code causes a bad analysis of source and the coverage report shows some bad 
results.

Coverage Ada - 2002.05.20/1704 With an important number of CASE/WHEN the instrumentor fails

A structure which contains a large number of CASE/WHEN causes a core dump to 
the instrumentor.

Coverage C++ - 2002.05.20/1598 Bad position of closing brace after asm() statement in if statement

Bad position of closing brace after asm() statement in if statement causes error in the instrumented 
code when compiled.

Coverage Ada - 2002.05.20/1573 The instrumentor (analyzer) loops

The Ada instrumentor loops during the file analysis.

Coverage C - 2002.05.20/1504 **Rename of void* causes syntax errors in instrumented code**

Usage of "-rename" command line option for void* functions causes illegal code generation.

Documentation N/A - 2002.05.20/1480 Trace: Example in pragma directives help (Ref Manual) uses incorrect syntax

In the reference manual under the topic of 'Pragma directives' there seems to be a mis-match between 
the example and the actual directives.

In the first example it has the following directive to illustrate how to do a dump:
  #pragma att_insert  if ( a == 0 ) _ATT_DUMP_STACK
however this would not work because it actually needs to be #pragma attol att_insert ... .

Likewise the following after the example would also need to be fixed up
This code will be replaced, after instrumentation, with the following line:
/*#pragma att_insert*/  if ( a == 0 ) _ATT_DUMP_STACK

Additionally I believe that the following syntax for use of the pragma directives should be changed 
from it's existing:
  #pragma  
to 
  #pragma attol  
as all of the pragma directives listed use #pragma attol ...

Documentation Ada - 2002.05.20/1438 Chapter on Testing tasks incorrect.

User Guide chapter Software Testing > Unit Testing > Unit Testing Scripts >
Advanced Ada > Testing Tasks states (in the PTU example) for version 2002.05.20:
TERMINATION
 #abort protected_array;
END TERMINATION
This can create a conflict when writing the SCI dump (especially if the task is calling 
stubbed procedures). Therefore, we suggest terminating any task (i. e. its state
is "terminated") before reaching the "END ELEMENT" statement in the PTU. For more details see 
the documentation for version 2002 Release 2.

Documentation C - 2002.05.00/1239 -SERVICE and -EXSERVICE are no longer supported by the instrumentor

The options to the instrumentor -SERVICE and -EXSERVICE are no longer supported by
the instrumentor. These options have been replaced by the options "-UNIT" and "-EXUNIT".

Documentation C - 2002.05.00/1213 Cannot connect to GUI

By default, the supervisor connects to user interface using the IP
address '127.0.0.1'.
On some client machines this does not seem to work.

Installation All - 2002.05.20/1464 testrtinit.sh or testrtinit.csh do not set up the LIBPATH for rs6000/aix

The Shared Library Path for Aix Operating system is not set by the testrtinit script

Object Testing C++ - 2002.05.20/1433 The ObjectTesting Wizard generates mangled names in return statements of STUBs

The ObjectTesting Wizard generates mangled names in return statements of STUBs. 
For example it generates

 #return Success__5cLift;

instead of


 #return cLift::Success;

PurifyLT C++ - 2002.05.20/1697 Instrumentor generates an inline function even though the size of the object is unknown

Instrumentor generates an inline function to test an object even though the
size of the object is unknown. This causes an error when the instrumented code
is compiled.

PurifyLT C++ - 2002.05.20/1525 Macro _ATP_USE_DEEP_GLOBAL

With the following type of code the instrumentor for PurifyLT does not generate
correct code to track the variables and compilation errors occur:


    struct TESTSTRUCT 
    { 
        float x,y; 
    }; 
    TESTSTRUCT dataArray[6];

PurifyLT C++ - 2002.05.00/1424 The instrumentor does not generate the "struct" keyword in certain circumstances

The instrumentor does not generate the "struct" keyword after the extern reference to a variable. Example:

struct sqlca
 {
 char sqlcaid[8];
 };
 extern struct sqlca sqlca;
 _ATP_START_PARSE_GLOBALS
   extern sqlca sqlca; // Should read extern struct sqlca sqlca;
 _ATP_PARSE_GLOBAL(sqlca)
_ATP_END_PARSE_GLOBALS

GUI C++ And C - 2002.05.20/1757 The path to the TDP object contains a slash instead of an antislash on Windows

The path to the TP.o object contains a slash character. Some compilers consider
this to be the start of a compiler option so the link step fails with
an "unknown compiler option" error message.

GUI C - 2002.05.20/1387 Dependencies (under "Files" view) do not contain the complete list of header files.

When creating a new activity with the Wizard, the PTU is generated correctly, but the referenced header files 
are not (all) listed in the Files view.

GUI N/A - 2002.05.01/1333 Absolute Paths in Settings -> General -> Directories incorrectly managed

Absolute paths in settings may cause paths duplication.

GUI All - 2002.05.01/1215 Build Options - Stages has no effect on the actual process of build

The Build -> Options -> Stages menu which allows you to choose which steps of the
build are to be performed is not operational.

System Testing C - 2002.05.20/1593 the atl_hexa_image function in ats.c does not convert correctly

In ats.c the function below does not convert any char into hexa.

void ATS_CLP atl_hexa_image (...)
{
  *hex1 = (value & 0xF0) + '0';
  if (*hex1 > '9') 
    *hex1 += ('A'-'0');
  *hex2= (value & 0x0F) + '0';
  if (*hex2 > '9') 
    *hex2 += ('A'-'0');
}

Target Deployment Port Ada - 2002.05.20/1459 TDP adaunxapex contains unnecessary files

Files attol_serv_dump.2.ada and attol.2.ada are not necessary.

Trace C++ - 2002.05.20/1487 Instrumenting nested templates classes produces code that does not compile

The following code

template 
class Test {
public:
     template 
     class Inner {
     public:
          int test_var;
     };

//     Inner theInner;
};

when instrumented with Trace produces code that does not compile.

Trace C++ - 2002.05.20/1481 Problem with macro _ATT_INIT_ARRAY_ATTR_2

Customer discovered problem in the code profiling generation before compilation that generates code 
that is not compileable - it generates the following code:
_ATT_INIT_ARRAY_ATTR_2(m_bgT,(BT *),2020)
Where m_bgT is defined as:
BT *m_bgT[20][20];

The macro for _ATT_INIT_ARRAY_ATTR_2 is defined as:
_ATT_INIT_ARRAY_ATTR_2(a,t,s1,s2)

and thus there appears to be a code generation error.  The code that generates the
_ATT_INIT_ARRAY_ATTR_2(m_bgT,(BT *),2020) 

should have created the line as:
_ATT_INIT_ARRAY_ATTR_2(m_bgT,(BT *),20,20)

Compiling the file generates the following error:

..\..\Bg.h(115) : warning C4003: not enough actual parameters for macro
'_ATT_INIT_ARRAY_ATTR_2'
..\..\Bg.h(115) : error C2059: syntax error : ';'
..\..\Bg.h(115) : error C2065: '_att_iterator_2_m_bgT' : undeclared
identifier
..\..\Bg.h(115) : error C2143: syntax error : missing ';' before ')'

Evaluation using Visual C++ 6.0.

Recreated based on sample code provided by customer (available in SR).

Unit Testing Ada - 2002.05.20/1737 For procedure taking <type>'access parameter, incorrect type declaration generated

If the procedure's parameter is an access type, the generated ptu will contain
a declaration only for the simple type.

Unit Testing Ada 95 - 2002.05.20/1730 Ada 95 stub discrepancy

The generated code uses a non-constraint type instead of (correctly) using
the constrained sub-type.

Unit Testing Ada - 2002.05.20/1699 The test script compiler generates a body for an abstract procedure in a stubbed package

The preprocessor generates a body for an abstract procedure in a stubbed
package. This results in a compilation error during the compilation of the code
generated from the test script.

Unit Testing Ada - 2002.05.20/1689 The postprocessor Ada loops, syntax error in tdc and rio

The postprocessor loops with the following message:
TestRT-W-STXERRTDC, Syntax error in the file . TDC desynchronization
beetwen tdc and rio
Error: problem during search of error messages INTERNERR

Unit Testing Ada - 2002.05.20/1608 Start generates #with lines for units passed by "-INTEGRATE=" option

The generated PTU template will contain:
#with PACK.INC; 
Inc being a separate procedure of Pack (and not a subpackage).

Unit Testing Ada - 2002.05.20/1540 The "Additional Report Generation options" are not passed to the report generator

The "Additional Report Generation options" are not passed to the report
generator. A modification to a file is necessary. Contact the technical support
to have the updated file.

Unit Testing Ada - 2002.05.20/1538 The option -ro on the Ada report generator is not supported but there is no warning

The option -ro on the Ada report generator is silently ignored. This option is
nolonger supported you should export the report in HTML from the Test RealTime
user interface.

Unit Testing Ada - 2002.05.20/1523 Parameterized Environments not supported

Currently, declaring a parameterized Environment does not modify the generated code.

Unit Testing Ada 83 - 2002.05.20/1518 Generated code truncates user code from within a stub procedure

Generated code truncates user code from within a stub procedure.

Unit Testing Ada 83 - 2002.05.20/1506 Generated code not Ada83 RM compliant

Generated code violates [RM_83 3.9(2)]: Type-declaration following a body.
This happens with type Attol_Uct_2 which is used for stub initializations.

Unit Testing C - 2002.05.20/1469 Test script generator generates STRUCTURE statements for typedefs

Test script generator generates STRUCTURE statements for typedefs and the
resulting test script fails when the preprocessor tries to analyze it.

Unit Testing Ada 95 - 2002.05.20/1460 Stub call to child package not recognized if fully qualified

If the stub call is fully qualified:
       <package>.<child_package>.procedure 1 => [etc...],
then an error is generated during preprocessing.

Unit Testing Ada 95 - 2002.05.20/1461 Error "CASE overflow in the module generate_tagged_edv_list_recursive : bad type"

When generating the code for a tagged type the following error message is
raised:

CASE overflow in the module generate_tagged_edv_list_recursive : bad type

Unit Testing Ada - 2002.05.20/1439 Generated PTU contains VAR lines over 80 characters long

Request for chopping generated VAR lines of PTU at around 80 characters in length

Unit Testing Ada 95 - 2002.05.01/1408 TDP Ada Aonix contains reference to RTRT_IMP95 in its analyzer files

The analyzer specification source file 
targets\adaaonix\ana\ada95\system-storage_elements.ads contains the following
line:
with RTRT_Imp95;
This causes the generated code to contain the same.

Unit Testing C - 2001A.04.01/859 Running start on preprocessed C file gives defined type as variable in VAR within
Environment block

Under certain circumstances, a type may show up as variable in an Environment block.

Known Issues

Code Coverage All - 2002.05.01/1338 (-) Coverage results (in CLI mode) are not appended anymore to 'attolcov.tio'

Coverage results are now ouput into the file "atlout.spt" and in create mode.
The file 'attolcov.tio' is created by calling the batch tool atlsplit on
the 'atlout.spt' file. The default filename 'attolcov.tio' can still be changed
using the "ATC_TRACES" environment variable. The test timestamp (line DT in the
tio file) is written by the atlsplit tool and not anymore by the TDP.

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.

Component Testing for C++ - 2002.05.20/1594 (-) Component Testing for C++ produces an unnecessary warning when
STUBing functions declared as extern "C"

When writing stubs of functions that have extern "C" linkage. Component Testing for C++ may
produce a warning message during the compilation of the test script. This warning message indicates:
TestRT attolccp: warning: math.stb:25: return type does not match the function prototype
> extern "C" int assertcsd(int i

Component Testing for C++ - 2002.05.01/1443 (-) Component Testing for C++: Unresolved symbol when linking

The Component Testing for C++ Wizard does not generate appropriate stubs for static fields.
If a stubbed class contains a static field, and this field is used by the test 
script and/or the tested source code, the linker will report an undefined 
reference to the static field. The workaround consists in adding manually the 
missing definition to the stub file (.stb), as shown in the example below:

##a_type stubbed_class::static_field;

Work-Around :

Add the line manually to the STB file.

Component Testing for C++ - 2002.05.00/1110 (-) Component Testing for C++ STUBs are not instrumented with OTC assertions (in some cases)

On non-Microsoft TDP:
If "Settings -> Runtime Analysis -> General -> Misc. Runtime Analysis
Options -> C++ Analysis -> Instantiate all templates even if not used" is not
checked (this is the default),
AND if some methods defined within a template class are stubbed,
AND if these methods are used in the code before the definition of the replacing
stub is seen
THEN these stubbed methods will not be instrumented by any of the Performance Profiling, 
Memory Profiling, Code Coverage or Runtime Tracing features, nor by the OTC assertions. 
This is usually not a problem with Performance Profiling, Memory Profiling, 
Code Coverage or Runtime Tracing, because most of the time stubs are excluded from 
these features' instrumentation. However it is a real defect regarding OTC assertions 
because the stubs should be OTC-tested, since they are methods of a tested class.

GUI Ada - v2002 Release 2/1797 (-) Wizard does not accept to generate a node for an Ada compilation unit
consisting only of a procedure

When using the wizard to generate a test node based on a procedure only, the unit is not 
shown in the dialogue to select the code under test.

Work-Around :

Press cancel within the wizard, go to the project window, select the 
Asset view > "By File," select the file containing the procedure to be tested, 
and click on the right mouse button. Select the "Test..." field. 
The wizard will reopen, and this time the Unit under test is correctly selected. 
Proceed as usual.

GUI N/A - 2002.05.20/1691 (-) In GUI "clear all" also deletes all files copied in directory for intermediate files

In the directory of intermediate files ( with TDP Name ), if you put a file which is needed for 
execution ( ex: a dll ) if you make a clear all, this file will be deleted.

Work-Around :

Put in read only the file.

GUI 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.

GUI All - 2002.05.20/1521 (-) Coverage Report Viewer no longer contains feature "Deselect all tests"

Missing feature in the GUI.

Work-Around :

Deselect all tests one by one.

GUI N/A - 2002.05.20/1455 (-) Launching GUI to an Exceed Server Windows will kill the X Server

Running the GUI from a Solaris session displaying to a Exceed version 5.00 server running on 
Windows 2000 causes the server to abort.

Work-Around :

Upgrade to Exceed 7.0 or later.

GUI N/A - 2002.05.00/1348 (-) GUI color on HP

Limited choice of colors available for the GUI on HP-UX workstations running
CDE on a 256 color display.

Work-Around :

Use the QtConfig tool to customize the color map.

Runtime Tracing C++ - 2002.05.00/1165 (-) The by default sequence diagram printing functionality does not work correctly

On Unix and Windows, the by default Runtime Tracing printing functionality does not work 
correctly (when all the pages are selected for printing, only the first page is 
printed). This printing defect occurs only for the Runtime Tracing diagram.

Work-Around :

Select a range to print for example page 1 to 6.

Component Testing for C - 2002.05.20/1702 (-) The template generator does not generate a stub if there is a space between the function name and the parameter and a prototype does not exist

Example :
int test(p1, p2)
int p1;
char p2[4];
{
	int result = p1;
	int value = 0;


	value = f1(p2);
	result += f2 (value);

	return result;
}

A stub will be generated for f1 but not for f2.
If the prototype exist, the stub will be generated.

Component Testing for C - 2001A.04.01/1640 (-) STUBing function that has a parameter of type cost pointer generates code that has
warnings or errors

Stubbing a function with the following prototype:

DEFINE STUB adc_close_c
    #adc_Result_t func(const void * _in Data_Ptr); 
END DEFINE

produces code that does not compile. NOTE: void can be replaced with any type
except char which is handled differently.

Work-Around :

In the test script, create a new type as follows:

#typedef const void * atl_void_const;

and then define the stub as follows:

DEFINE STUB adc_close_c
    #adc_Result_t adc_Qadc555Init(atl_void_const _in Data_Ptr); 
END DEFINE

Component Testing for C - 2002.05.20/1467 (-) Bad code generation when you have a macro calling itself

Bad code generation when you have a macro calling itself :

Example :

C-File:
DMTL_GLOB_STATE_1      dmtl_glob_state_1;

 
 H.-File:
typedef struct
  {
       struct
       {
               u32 lv_rough_leak_susp           :1;
       }bitfield;
  }DMTL_GLOB_STATE_1;
 
 
 PTU-File:
VAR lv_rough_leak_susp, int, INIT = 1, EV =INIT 

the preprocessor expands lv_rough_leak_susp twice if the macro is defined like that: 

#define  lv_rough_leak_susp           dmtl_glob_state_1.bitfield.lv_rough_leak_susp 

In generated code you obtain :

dmtl_glob_state_1.bitfield.dmtl_glob_state_1.bitfield.lv_rough_leak_susp = 1;

Work-Around :

In the test script, undefine the macro and use the normal C name of the field.

Component Testing for Ada - 2002.05.01/1313 (-) Preprocessor does not accept relative paths in .alk file

If .alk contains relative paths (with ".\"), the preprocessor does not accept the file.

Work-Around :

Generate the file with absolute paths, or without ".\", putting just the file name.

Component Testing for Ada - 2002.05.00/1217 (-) Attolpostproada does no longer generate ASCII reports

Report Generator does not accept the -RO command line option.

Component Testing for C - 2001A.04.00/837 (-) Line numbers in error messages upon Test Harness Compilation incorrect

When using the '&' for giving instructions spanning more than one line, the error
message gives the last line of this instruction as reference.