I am using "xdb" to examine a core file as a result of an abort()
library call from a 'C' program executing on an HP730 running
HPUX 9.05. It seems that memory is being trashed resulting in a
sporadic but consistent error.
Using the "lg" sub-command results in the display of only those
globals which are not defined as static. If I invoke the
executable and single-step through the first instruction I can then
display the address of the static globals that are associated with
the problem captured in the core file. The static variables
themselves and the objects to which they point are exactly as
anticipated.
It seems evident from this that the symbol mapping information
maintained in the executable has been trashed. However, I can
find no reference in "man" pages or "FAQ's" which would help me
to determine the location of this information.
I am currently comparing the "nm" output of a debuggable and
non-debuggable version of the executable to try to piece this
together the slow way. I am sure this information is readily
available somewhere, but where? I would appreciate any hints on
how to speed up this process.
diw