Debugging with GDB (September 2007)

Chapter 14: HP-UX Configuration-Specific Information 189
Shift <Key>Prior: string(0x2) \n \
Shift <Key>Next: string(0x6) \n \
Shift <Key>Up: string(0x5) \n \
Shift <Key>Down: string(0x19) \n \
Shift <Key>Left: string(0x1b) string(i) \n \
Shift <Key>Right: string(0x1b) string(la)
For DtTerm use the following:
*DtTerm*Translations: #override\n \
Shift <Key>osfPageUp: string(0x2) \n \
Shift <Key>osfPageDown: string(0x6) \n \
Shift <Key>osfUp: string(0x5) \n \
Shift <Key>osfDown: string(0x19) \n \
Shift <Key>osfLeft: string(0x1b) string(i) \n \
Shift <Key>osfRight: string(0x1b) string(la)
Mouse operations are not supported in the -tui mode. Also the paging and shift keys
do not work well with VT100.
14.26.6 Changing the size of the source or debugger pane
1. Escape to vi command mode first.
2. Drag the status bar using the mouse.
If you are using -tui mode, use these commands to change the size of the current
window:
h
CTRL
i
-W +
to increase
h
CTRL
i
-W -
to decrease
In Visual Interface for WDB, the current window is usually the debugger window.
14.26.7 Using commands to browse through source files
Visual Interface for WDB is based on ‘vim’, so you can also use the ‘vi’ commands to
browse. For example,
h
CTRL
i
-B,
h
CTRL
i
-F,
h
CTRL
i
-D,
h
CTRL
i
-U are useful for browsing
the debugger window. These commands work whether or not you escape to ‘vi’ mode.
These ‘vim’ commands require you to escape to ‘vi’ mode.
For example:
‘/’ Search forward
‘?’ Search backward
‘n’
‘N’ Repeat search
‘%’ Match braces