HP WDB 5.9 Release Notes

Table 1 Dependent Library Routines for Run Time Checking using WDB (continued)
uwx_register_alloc_cbuwx_self_init_infopthread_getschedparamuwx_self_init_context
uwx_self_lookupipuwx_register_callbacksstrstr
The Run Time Checking (dynamic memory, libraries, and pthreads checking) in
WDB is dependent on the semantics and the standard behavior of these library
routines. Run Time Checking in WDB results in unexpected and unpredictable
behavior when used with applications that substitute or redefine these library
routines.
Before enabling the Run Time Checking feature in WDB, use the nm command to
determine if your application or the dependent libraries in your application redefine
or substitute these library routines.
• Batch Mode RTC displays one of the following errors and causes the program to
temporarily hang if the version of WDB and librtc.[sl|so] do not match, or
if WDB is not available on the system:
/opt/langtools/bin/gdb: unrecognized option `-brtc'
Use `/opt/langtools/bin/gdb --help' for a complete list of options.
Or
execl failed. Cannot print RTC info: No such file or directory
This error does not occur under normal usage where WDB or librtc.[sl|so]
is used from the default location at /opt/langtools/...
However, this error occurs if GDB_SERVER and/or LIBRTC_SERVER are set to a
mismatched version of WDB or librtc.[sl|so] respectively.
• If the application does not link in the libpthread library
(lipbpthread.so|libpthread.s1) or the libpthread tracer library
(libpthread_tr_so.l|libpthread_tr.l ), the following error message
appears:
Tracing version of libpthread is not loaded: set thread_check before starting the program, link
your program with libpthread_tr or set LD_LIBRARY_PATH to contain /opt/langtools/wdb/lib/hpux32
HP-WDB Debugger does not display backtrace under Backtrace at the
point of event occurrence for thread conditions detected at thread-exit, if
there is an implicit call to pthread_exit().
14