HP WDB GUI 5.7 Reference Manual (September 2007)

Troubleshooting WDB GUI
Known Problems
Chapter 4 97
1. If you have a read command in the .cshrc file and if you have not specified the
absolute path for the Program Console (ie) TERM=dtterm, and if you try to open the
Program Console, the GUI will hang or will dump core.
When there is no full path specified for the dtterm/ hpterm/xterm, WDB GUI will
use the which command to find the path for these terminals. which executes the .cshrc
file and the read in .cshrc waits for some input . But since WDB GUI has no associated
terminal for input, it will hang or dump core.
To solve this, remove/comment the ’read’ in the .cshrc file while invoking WDB GUI.
2. You might find the following warning appearing on the Status Line, when you invoke
the GUI’s program console :
Note: Trying other terms ( could not find $TERM dtterm )
The warning will appear if the PATH for the term is not set properly. To avoid getting
this warning, set the absolute path for hpterm /dtterm /xterm in TERM. For example:
$ export TERM=/usr/bin/X11/dtterm
3. WDB GUI will coredump if TERM variable is not initialised. For example:
$ export TERM=
4. To avoid the coredump, set TERM appropriately.
• Problem:Fonts problem in non-HP-UX machines
Workaround:WDB GUI might dump core when you set the DISPLAY environment variable
to a non-HP-UX machine say SUN or LINUX. The non-HP-UX machines do not recognise
HP fonts and so the application will dump core.
The solution is to copy the HP fonts on the non-HP-UX machine and to set that directory
in the fontpath. All neccesary HP fonts reside in the following directory in the HP-UX
machines:
Create a tar file, say fonts.tar of this directory and copy the tar file to the non-HP-UX
machine.
At the non-HP-UX machine, before invoking the WDB GUI,
1. Goto the directory where you have copied the tar file, say /tmp
2. Untar the tar file
3. xset +fp /tmp
4. xset fp rehash