Introduction to TETware source code patch releases. Source code patch releases may be made in between TETware GA releases. This enables customers who have signed up for TETware support to gain access to the most up-to-date TETware source code without needing to wait for the next GA release. Each patch release fixes one or more problems that have been reported since the last GA release. Once two or more patches have been issued, a cumulative patch archive is available in addition to the latest (or current) patch archive. The cumulative patch contains all the source files that have changed since the GA release, whereas the current patch archive contains only those files that have changed since the last patch release. If you are installing a patch release into a TET_ROOT directory hierarchy in which you have previously built TETware release 3.1, you don't have to re-run tetconfig or set up the defines.mk file again after you install the patch release. Instead you can rebuild TETware by resuming the build procedure at the "make install" stage. (A description of this procedure can be found in the appropriate TETware Installation Guide.) There follows a description of each of the problems fixed in each of the patch releases available to date. =========================================================================== Source code patch release 3 - 4th June 1997 =========================================================================== Port of TETware-Lite to Windows 95 --------------------------------------------------------------------------- Corrected a bug in the WIN32 signal blocking emulation =========================================================================== Source code patch release 2 - 10th April 1997 =========================================================================== When a child process is launched using tet_spawn() on Windows NT, the child process controller exits with the message: (null): (child.c, 132): argument count wrong; process must be \ executed by tet_spawn() =========================================================================== Source code patch release 1 - 1st April 1997 =========================================================================== Can't unlink temporary execution directory on NT when it contains read-only files. This is because on NT, write permission is required on a file in order to unlink it. --------------------------------------------------------------------------- When TET_EXEC_IN_PLACE is False, the copy to tet_tmp_dir is always done from the test case source directory. This is incorrect if there is an alternate execution directory - the copy should be done from there instead. --------------------------------------------------------------------------- White space is not tolerated at the start of lines in a scenario include file. This was permitted in TET 1.10, and is required in order to support X/Open's VSW5 and VSM test suites. --------------------------------------------------------------------------- tcc should generate a type 5 journal line containing uname information. This is for compatibility with ETET. (NOTE that in Distributed TETware, this line describes the system on which tcc is invoked which is not necessarily the same as the systems(s) running the tests.) --------------------------------------------------------------------------- In tcc/scen3.c function remove_unneeded_scenarios() the loop follows the forward pointer chain even after an unneeded scenario is removed. This causes a core dump on systems where the contents of free()'d memory should not be referenced. The comment describes what is required but the code doesn't do it! --------------------------------------------------------------------------- The file servlib/shared.mk is missing from TETware-Lite. The makefile should not include this file - instead it should be included when required by the transport-specific make include file. --------------------------------------------------------------------------- The compiler generates a number of warning messages when compiling the INET transport-specific code on HP-UX. This is because the code was originally developed on HP-UX v7 which did not have the file and so the corresponding #include line was #ifdef'd out on HP-UX platforms. Now that more recent versions of HP-UX have this file, the #ifdef __hpux can be removed and the warnings go away.