Resolved Problems

This is the list of problems that have been completely resolved as of the current release of Kernel Trace.  It is provided as a mechanism to facilitate:
  1. the identification of defects and issues which are resolved but may not have been documented in previous releases;
  2. providing a history of all defects fixed to date, for regression testing purposes.
Number
Symptom
Root Cause
Status
1 Incorrect interpretation of the command line use of -i option by KTRACE.EXE. The problem with -i option processing is that it accepts mixed input so that decimal, octal and hex values may be entered like this: -i234abc or -i12FA etc. The problem is that KTRACE.EXE uses the function strtol  to convert the -i option value, but does not check for the termination character. For example, -i12FA may be visually interpreted as hex PID 0x12FA but strtol  truncates the alpha characters and assumes the decimal value of the PID is 12. This was a defect in KTRACE.EXE v1.1.7 and earlier. Fixed in the latest release of the Kernel Trace control program.
2 Starting tracing early in the boot process can cause a trap E or a system lockup with a black screen.  For example: 
  • when KTRACE.EXE is called from the beginning of STARTUP.CMD (this generated the trap E)
  • when KTRACE.EXE is called from the beginning of the first user exit in WSOD's restricted shell
This problem was caused by an invalid pointer begin passed from the kernel to the Execute Program tracepoint.  The pointer is supposed to allow the tracepoint to identify the name of the program being executed. This was a defect in KTRACE.SYS v1.1.12 and earlier.  Fixed in latest release of the Kernel Trace device driver.
3 QUERYFILEINFO tracepoint produces no data payload, only the pointer FFFF:FFFF This problem was caused by an invalid pointer being passed from the kernel to the Query File Information tracepoint.  It occurred when using OS/2 kernel revisions older than revision 14.080c. Fixed with OS/2 kernel 14.080c (first publicly released by IBM on a test basis October 15, 2001).
4 SETFILEINFO and SETPATHINFO tracepoints can generate a trap E when run in conjunction with IBM Communications Manager device driver CMVERIFY.SYS. This problem is caused by an invalid pointer being passed from the kernel to the SETFILEINFO and SETPATHINFO tracepoints when CMVERIFY.SYS is loaded. Fixed with OS/2 kernel APAR PJ28401.  In addition, a workaround for this problem was introduced with Kernel Trace 2002-02-22 release.

© 2001-2002 Golden Code Development Corporation.  ALL RIGHTS RESERVED.