HP WDB GUI 5.7 Reference Manual (September 2007)

Troubleshooting WDB GUI
Known Problems
Chapter 496
If you modify and save the source file in one window, the changes will not be visible in
the second window. If you then modify the source file in the second window, WDB GUI
will display this warning:
The file has been modified since opened or last saved. Save anyway? This happens
only for an NFS mounted filesystem that has a canonical reference and you do a cd to
that directory from within the debugger.
• Problem:Terminal Window Sometimes Fails to Start on 10.20
Workaround:The WDB GUI uses a terminal window to display the target programs
output and to allow user input to the target. The terminal program is started when the
View:Program Console menu pick is chosen or when the target program generates any
output. Some versions of dtterm on 10.20 cannot be started from the WDB GUI. If this
happens you will see the error:
Unable to start terminal
This is caused by a problem in dtterm, which is fixed in patch PHSS_17566.
If you donot have the patch available, you can work around the problem by setting the
environment variable TERM to hpterm and restarting the WDB GUI. You can also work
around the problem by starting the target program from a shell window and then
attaching to the program from the WDB GUI.
• Problem:Attaching to a Process May Generate Invalid Error
Workaround: If you attach to a program with a command line argument when you start
the WDB GUI, you may see an error that says:
No such file or directory.
This error may be displayed even when the WDB GUI was successful in attaching to the
process. If the WDB GUI comes up with the process loaded, you may ignore this message.
NOTE This problem does not occur if you start the WDB GUI and then attach to a
process from the WDB GUI menu.
• Problem:Viewing Large Call Stacks
Workaround:Runaway recursive functions can cause the call stack to become very large.
To prevent the long delays that would result when displaying a very large call stack, the
number of stack-frames displayed is limited to 200. To view a call stack with more than
200 frames, use the backtrace command from the Command view.
• Problem:Problems in invoking Program Console with .cshrc
Workaround: