Novell ACCESS MANAGER 3.1 SP2 - ACCESS GATEWAY GUIDE 2010 Manual page 231

/etc/init.d/novell-vmc stop
3 To start the Novell Access Gateway in debugging mode, enter the following command:
/etc/init.d/novell-vmc gdb
4 To run the Access Gateway process, enter the following command at the GDB prompt:
run -m <memory> 2>/var/log/ics_dyn.log
Replace <memory> with the percentage of total memory to be used for the ics_dyn process.
You should set this value between 20 to 30 per cent.
5 Repeat the scenarios to reproduce the issue.
5a If you are trying to reproduce the proxy crash, you will enter the GDB prompt as soon as
the crash is reproduced.
5b If you are trying to reproduce a functionality issue, enter the following command to enter
the GDB prompt as soon as the issue is reproduced:
Crtl+C
For a list of commands that can be entered in the debugger, see
Commands" on page
6 To save all event logs to a file, enter the following command:
d ,save 1
This stores all the events in the
<pid>all_events.0.txt
7 Tar or zip this file and send it to Novell Support.
Useful Debugger Commands
GDB Commands
Table 7-5
Command Function
gcore Generate core file
k Kill process
Quit GDB prompt
q
Print the back trace
bt
Core Dump
Before you begin, make sure there is free space in
least equal to the RAM size
To collect a core dump:
1 Log in as the user.
root
2 To disconnect all instances of the Access Gateway, enter the following command:
/etc/init.d/novell-vmc stop
3 At the bash prompt, specify the following command:
touch /tmp/.dumpcore
231.
/chroot/lag-debug/opt/novell/debug/
file.
to hold the core file and that the space is at
root
"Useful Debugger
Troubleshooting the Access Gateway Appliance 231