
and perform other debugging tasks, just as you would when debugging user
space programs.
The ability to debug a running kernel is provided through remote debugging.
The kernel code you are debugging runs on a test system. The dbx debugger
runs on a remote build system. The debugger communicates with the
kernel code you are debugging over a serial communication line or through
a gateway system. You use a gateway system when you cannot physically
connect the test and build systems. Figure 2–1 shows the connections
needed when you use a gateway system.
Figure 2–1: Using a Gateway System During Remote Debugging
ZK−0974U−R
Test SystemGateway System
Build System
Network
Serial Line
Kernel Code
dbx Debugger
As shown in Figure 2–1, when you use a gateway system, the build system is
connected to it using a network line. The gateway system is connected to
the test system using a serial communication line.
Prior to running the kdebug debugger, the test, build, and gateway systems
must meet the following requirements:
• The test system must be running Tru64 UNIX Version 2.0 or higher,
must have the Kernel Debugging Tools subset loaded, and must have the
Kernel Breakpoint Debugger kernel option configured.
• The build system must be running Tru64 UNIX Version 2.0 or higher and
must have the Kernel Debugging Tools subset loaded. Also, this system
must contain a copy of the kernel code you are testing and, preferably,
the source used to build that kernel code.
• The gateway system must be running Tru64 UNIX Version 2.0 or higher
and must have the Kernel Debugging Tools subset loaded.
2–38 Kernel Debugging Utilities