Debugging with GDB (September 2007)

Chapter 14: HP-UX Configuration-Specific Information 117
srand() unlink()
uwx_register_callbacks() lseek()
open() sprintf()
strcmp() printf()
pthread_self() putenv()
shmctl() strchr()
rand() uwx_self_lookupip()
shl_get() shl_unload()
shl_findsym () strtok_r()
time() uwx_get_reg()
shl_get_r() perror()
uwx_init() uwx_self_copyin()
creat() uwx_step()
write() uwx_self_init_context()
pthread_getschedparam() uwx_self_init_info()
uwx_register_alloc_cb() U_STACK_TRACE()
close() strchr()
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 WDB, use the nm(1) command
to determine if the application or the dependent libraries in the application re-define 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 supp ort 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 PA-RISC WDB. The PA-RISC version of HP WDB is provided as
part of the HP-UX operating system.