Debugging with GDB (September 2007)

140 Debugging with GDB
- For 32 bit IPF applications,
/opt/langtools/lib/hpux32/librtc.so
- For 64 bit IPF applications,
/opt/langtools/lib/hpux64/librtc.so
- For 32 bit PA applications,
opt/langtools/lib/librtc.sl
- For 64-bit PA applications,
/opt/langtools/lib/pa20_64/librtc.sl
To preload the librtc runtime library from a path that is different from the default
paths, you must use the LD_PRELOAD environment variable.
(Or)
• Instead of automatically preloading librtc and mapping the shared libraries, you
can explicitly preload the required librtc library after mapping the shared li-
braries private.
In the case of HP 9000 systems, you must explicitly map the share libraries as
private by using the +dbg enable option for the chatrcommand, as follows:
$ chatr +dbg enable ./<executable>
(This step is not required on Integrity systems.)
To explicitly preload the librtc runtime library and start the target application,
enter one of the following commands:
- For 32 bit IPF applications,
LD_PRELOAD=/opt/langtools/lib/hpux32/librtc.so <executable>
- For 64 bit IPF applications,
LD_PRELOAD=/opt/langtools/lib/hpux64/librtc.so <executable>
- For 32 bit PA applications,
LD_PRELOAD=/opt/langtools/lib/librtc.sl <executable>
- For 64-bit PA applications,
LD_PRELOAD=/opt/langtools/lib/pa20_64/librtc.sl <executable>
If LD_PRELOAD and chatr +mem_check are used to preload the librtc runtime
library , the librtc runtime library is loaded from the path specified by LD_
PRELOAD.
Note:
Batch Mode RTC displays one of the following errors and causes the pro-
gram 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"