Filter
Top Products
The $kdebug_host variable is the name of the gateway system. By
default, $kdebug_host is set to localhost, assuming no gateway
system is being used.
The $kdebug_line variable selects the serial line definition to use in
the /etc/remote file of the build system (or the gateway system, if one
is being used). By default, $kdebug_line is set to kdebug.
The $kdebug_dbgtty variable sets the terminal on the gateway system
to display the communication between the build and test systems, which
is useful in debugging your setup. To determine the terminal name to
supply to the $kdebug_dbgtty variable, enter the tty command in the
correct window on the gateway system. By default, $kdebug_dbgtty
is null.
For example, the following $HOME/.dbxinit file sets the
$kdebug_host variable to a system named gatewy:
set $kdebug_host="gatewy"
4. Recompile kernel files, if necessary.
By default, the kernel is compiled with only partial debugging
information. Occasionally, this partial information causes kdebug to
display erroneous arguments or mismatched source lines. To correct
this, recompile selected source files on the test system specifying the
CDEBUGOPTS=
−g argument.
5. Make a backup copy of the kernel running on the test system so that
you can restore that kernel after testing:
# mv /vmunix /vmunix.save
6. Copy the kernel to be tested to /vmunix on the test system and reboot
the system:
# cp vmunix.test /vmunix
# shutdown -r now
7. If you are debugging on an SMP system, set the lockmode system
attribute to 4 on the test system, as follows:
a. Create a stanza-formatted file named, for example
generic.stanza, that appears as follows:
generic:
lockmode = 4
This file indicates that you are modifying the lockmode attribute
in the generic subsystem.
b. Use the sysconfigdb command to add the contents of the file to
the /etc/sysconfigtab database:
# sysconfigdb -a -f generic.stanza generic
c. Reboot your system.
2–40 Kernel Debugging Utilities