HP-UX AAA Server A.07.01 Administrator's Guide

6. To ensure that the AATV is loaded correctly, check the logfile for an entry similar
to the following:
read_dyn_cfg: Loaded shared object: <aatvname>, <No. of aatvs>
Testing and Debugging a Plug-in
You must test the software module before you start using it in a production
environment. You can use several different methods to debug any modules that you
create. This section discusses testing the software module using the GNU Project
Debugger (gdb).
Using the GNU Project Debugger
HP recommends using gdb to debug software modules created using the HP-UX AAA
Server SDK.
NOTE: To debug a software module with gdb, your program must be compiled with
debug information enabled (using the -g option).
Using gdb to Debug Your Software Module
To debug your software module using gdb, complete the following steps:
1. Determine the RADIUS server’s process ID by entering the following command:
# ps -ef | grep radiusd
2. End the RADIUS server process by entering the following command:
# kill <radius pid>
3. Enter the following command:
# chatr +dbg enable /opt/aaa/bin/radiusd
4. Start radiusd by entering the following command:
# /opt/aaa/bin/radiusd
5. Start the debugger by entering the following command:
# gdb
This command starts a gdb session in UNIX and the gdb prompt appears. You can
access help by typing help at the gdb prompt. For more information about gdb,
enter man gdb at the command prompt.
If you start the gdb session from some other location, you must specify the directory
in which your plug-in module source code is located (for more information, see
gdb help).
6. At the gdb prompt, enter the dir command to include the path of your software
module, as shown in the following example:
# gdb> dir /opt/aaa/examples/sdk/csi
322 Customizing the HP-UX AAA Server Using the SDK