HP-UX Programming Tools Release Notes

28 Chapter4
Problem Descriptions and Fixes
Problems and Limitations
HP DDE Problem With vfork()
You cannot single-step over a vfork() call. If you try to single-step, the
target program will fail. A workaround is to set a breakpoint after the
vfork() call. Then issue a go command instead of single-stepping to get
past the vfork() call.
HP DDE Problem with Pascal Uplevel References
HP DDE will always pick the most recent stack activation to display
uplevel references when direct or indirect recursion is used. This may
cause HP DDE to display uplevel variables with a value that is different
from the value seen by the function.
HP DDE Problem with Purify'd Code
During a debugging session on executables produced by Purify software
(a product of Pure Software Inc., now a division of Rational Software
Corp.), the application may receive a SIGCHLD signal and stop executing
before reaching the main entry point. Issue a go command to proceed to
the main entry point.
HP DDE Limitation with Implicitly Loaded Shared
Libraries
HP DDE currently does not allow you to intercept the loading of
implicitly loaded shared libraries (libraries that are linked with your
program).
Since some implicitly loaded shared libraries contain code that is
executed before the main program actually starts, you may be unable to
set breakpoints in that code. This problem typically arises when you try
to set a breakpoint on a C++ constructor function for a global object.
A workaround for this problem is to stop the debugger in start-up system
code and then to load debugging information for the implicitly loaded
shared library. The following example illustrates the details for this
workaround.