Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VAXDEBU07_070 VAX V7.0 DEBUG ECO Summary
Copyright (c) Digital Equipment Corporation 1997. All rights reserved.
PRODUCT: OpenVMS VAX
COMPONENT: DEBUG - DBG$HA_KERNEL.EXE
DBG$HA_MAIN.EXE
DEBUG.EXE
DEBUGSHR.EXE
DEBUGUISHR.EXE
VMSDEBUGCUSTUIL.UID
VMSDEBUGUIL.UID
SOURCE: Digital Equipment Corporation
ECO INFORMATION:
ECO Kit Name: VAXDEBU07_070
ECO Kits Superseded by This ECO Kit: VAXDEBU01_071 (V7.0 Only)
VAXDEBU06_070
VAXDEBU02_070
VAXDEBU01_070
ECO Kit Approximate Size: 4554 Blocks
Kit Applies To: OpenVMS VAX V7.0
System/Cluster Reboot Necessary: No
Installation Rating: 3 - To be installed on all systems running
the listed versions of OpenVMS which
are experiencing the problems described.
NOTE: In order to receive the full fixes listed in this kit,
the following remedial kits also need to be installed:
None
ECO KIT SUMMARY:
An ECO kit exists for DEBUG on OpenVMS V7.0. This kit addresses the
following problems:
Problems addressed in VAXDEBU07_070 kit
o There are no new problem fixes in this kit. The kit is being
re-issued as a single version kit. If you have installed the
VAXDEBU01_071 remedial kit, you do not need to install the
VAXDEBU07_070 kit.
Problems addressed in VAXDEBU01_071 kit for OpenVMS VAX V7.0
o Some VAX steps in PASCAL programs fail and cause severe errors,
for example, %SYSTEM-F-RADRMOD.
If there is a step range that includes a HALT instruction, then
the TBIT trap gets raised. That is, do not optimize stepping
performance for such ranges. Unfortunately, there are other
problems with this optimize algorithm that were fixed in later
releases. So to properly fix the essence of the problem, this
new optimization, for this stream, it must also be able to
recognize entry masks, and to adjust the low end, as well as
the high end, of the stepping range.
Problems addressed in VAXDEBU06_070 kit
o Missing files. The patch would not correct all the problems
mentioned in the release notes.
Problems addressed in VAXDEBU02_070 kit
o Debug main to kernel $WAKE uses the initial kernel thread PID.
This will not work if the some other kernel thread invoked the
debug kernel. That is, the debug kernel will operate in the
other kernel thread context including its $HIBERs. The $WAKE
from main needs to use the other kernel thread PID.
Problems addressed in VAXDEBU01_070 kit
o Japanese users report that the Debug GUI does not support
Kana-Kanji conversions.
o Source view line numbers are not visible on systems running CDE
and Motif V1.2.4.
o It is difficult to debug problems in the HA (Heap Analyzer)
kernel, especially problems during startup.
o HA main was failing to display error messages to SYS$OUTPUT
when appropriate. In particular, when DECW$DISPLAY was not set
properly, HA main failed to inform the user of its inability to
run.
o UIL files contained names greater than 31 characters long which
cause UIL compilation failures on V7.0.
o Applications linked with PTHREAD$RTL go into an infinite loop
when run with the Heap Analyzer (HA) and with kernel threads
enabled.
o Narrow the window between when DEBUG gains control and the call
to the threads facility to stop task scheduling.
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in the
OPENVMS database. To view these articles, open the appropriate product
database and perform a query using either of the following search
strings: 'VAXDEBU07_070' or 'VAXDEBU'.
ECO KIT ORDERING INSTRUCTIONS:
If after an evaluation you wish to obtain this kit, request it
electronically using the appropriate Advanced Electronic Services
(AES) Service Tool. If you are not familiar with how to request
kits electronically, open the DIA, WIS or DSNLINK database and
review the article entitled:
[AES] How To Electronically Request ECO Kits Using Service Tools
INSTALLATION NOTES:
The system does not need to be rebooted after this kit is installed.
However, if you have other nodes in your OpenVMS VMScluster, they should
be rebooted or you should install this kit on each system in order to
make use of the new image(s).
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| DBG$HA_KERNEL.EXE |%X11D63E62| V7.0-04R | 18-FEB-1997 |
| | | 23:56:21.30 |
+----------------------------+----------+-----------------+--------------+
| DBG$HA_MAIN.EXE |%XD43B11BF| V7.0-04R | 19-FEB-1997 |
| | | 00:31:29.53 |
+----------------------------+----------+-----------------+--------------+
| DEBUG.EXE |%X3A7BE31C| V7.0-04R | 19-FEB-1997 |
| | | 00:25:43.66 |
+----------------------------+----------+-----------------+--------------+
| DEBUGSHR.EXE |%X50CC1733| V7.0-04R | 19-FEB-1997 |
| | | 00:28:18.88 |
+----------------------------+----------+-----------------+--------------+
| DDEBUGUISHR.EXE |%XC1A52AB1| V7.0-04R | 19-DEC-1997 |
| | | 00:30:49.22 |
+----------------------------+----------+-----------------+--------------+
|
