Specifications

Debugging a Device Driver
11.2 Using the OpenVMS AXP System-Code Debugger
The following commands access the user programs’ (or in this case the system-
code debugger) memory and registers. The DEPOSIT and EXAMINE commands
implement the following set of XDELTA commands: /, !, [, ", ’.
DEPOSIT
EXAMINE
SHOW STACK
SHOW CALLS
11.2.7 System-Code Debugger Network Information
The system-code debugger and the target kernel on the target system use a
private Ethernet protocol to communicate. For the two systems to see each other,
they have to be on the same Ethernet segment.
The network portion of the target system finds the first Ethernet device and
communicates through it. The network portion of the host system also finds
the first Ethernet device and communicates through it. However, if for some
reason, the system-code debugger picks the wrong device, you can override this
by defining the logical DBGHK$ADAPTOR to the template device name for the
appropriate adaptor.
11.3 Troubleshooting Checklist
If you have trouble starting a connection, perform the following tasks to correct
the problem:
• Check SCSNODE on the target system.
It must match the name you are using in the host CONNECT command.
• Make sure that both the Ethernet and boot device are on the boot command.
• Make sure that the host system is using the correct Ethernet device, and that
the host and target systems are connected to the same Ethernet segment.
• Check the version of the operating system and make sure that both the host
and target systems are running the same version (OpenVMS AXP Version
6.1).
11.4 Troubleshooting Network Failures
There are three possible network errors:
• NETRERTRY
Displayed if the system-code debugger connection is lost.
• SENDRETRY
Indicates a message send failure.
• NETFAIL
Caused by the two previous messages.
The netfail error message has a status code that can be one of the following
values:
11–11