HPlogo HP C/HP-UX Version A.10.32.30 Release Notes: For HP-UX 10.20 Systems > Chapter 4 Problem Descriptions and Fixes

HP WDB Problems and Limitations

» 

Technical documentation

Complete book in PDF

 » Table of Contents

 » Index

HP WDB Limitation on Window Resizing with TUI

We recommend that you not resize an hpterm or xterm terminal window while using the Terminal User Interface (TUI). If you do, the following problems occur:

  • The command window contents and (gdb) prompt are erased. Issue a refresh (ref) command and then press the Return key to recover the prompt.

  • It is no longer possible to scroll in windows by using the Page Up, Page Down, and arrow keys. You must use the +, -, >, and < commands instead.

HP WDB Limitation with Processes Started across NFS Mounts

When HP WDB attaches to a running program you might get this message:

(gdb) attach 12852
Attaching to process 12852
 
Attaching to process 12852 failed.  Check whether
program is on an NFS-mounted file-system.  If so,
you will need to mount the file system with the
"nointr" option with mount(1) or make a local copy
of the program to resolve this problem.

The most likely cause for this message is that you have attached to a process that was started across an NFS mount.

The HP-UX kernel has a restriction that prevents a debugger from attaching to a process started from an NFS mount, unless the mount was made non-interruptible with the -nointr flag, see mount(1).

Terminal Window Sometimes Fails to Start from WDB GUI on 10.20

The WDB GUI uses a terminal window to display the target program's output and to allow user input to the target. The terminal program starts when you choose the View:Program Console menu command or when the target program generates 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 don't 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.

© 1999 - Hewlett-Packard Development Company, L.P.