Debugging with GDB Manual HP WDB v6.3 (5900-2180, August 2012)

strcmp()strcat()
printf()ctime()
pthread_self()dlclose()
putenv()memchr()
shmctl()strrchr()
strchr()dlgetname()
rand()dlget()
uwx_self_lookupip()clock_gettime()
shl_get()strlen()
shl_unload()dlhook()
shl_findsym ()dlmodinfo()
strtok_r()environ()
time()getenv()
uwx_get_reg()strlen()
shl_get_r()execl()
perror()exit()
uwx_init()fclose()
uwx_self_copyin()fork()
creat()strdup()
uwx_step()fopen()
write()fprintf()
uwx_self_init_context()fscanf()
pthread_getschedparam()sscanf()
uwx_self_init_info()strcasecmp()
uwx_register_alloc_cb()getcwd()
U_STACK_TRACE()getpagesize()
close()getpid()
strchr()srand()
The runtime checking (of dynamic memory, libraries, and pthreads) in the debugger relies on the
semantic and standard behavior of these library routines. Run Time Checking results in unexpected
and unpredictable behavior when used with applications that substitute or re-define these library
routines.
Before enabling the Run Time Checking feature in HP WDB, use the nm(1) command to determine
if the application or the dependent libraries in the application redefine or substitute these standard
library routines.
14.3 Supported Platforms and Modes
• Supported Platforms
HP WDB supports source-level debugging of programs written in HP C, HP aC++, and Fortran
90 on Integrity systems running on HP-UX 11i v2 or later and PA- RISC systems running HP-UX
11i v1 and later.
• Support for assembly-level debugging
HP WDB provides support for assembly-level debugging.
• Support for automatic loading of debug information
Debug information is automatically loaded from modules when an application is com- piled
with the +objdebug option.
• Support for debugging PA-RISC programs on Itanium-based systems
You can debug PA-RISC applications and core files on Itanium-based systems. When you start
HP WDB, if the debug target is a PA-RISC binary program, the debugger automatically loads
108 HP-UX Configuration-Specific Information