One of our users reported that when he attempted to use DECladebug,
it bombed out on startup, emitting the following message (with the
"Assertion failed" line broken up here for improved readability):
walrus> decladebug scat
Welcome to the DECladebug Debugger Version 4.0-7
------------------
object file name: scat
Reading symbolic information ...Assertion failed:
alternateEntryPointStack->isEmpty()
src/libsrc/ladebug/parsesymscoff.C 5090
Abort - core dumped
The a.out was built with a command of the following sort:
f77 -g -o scat scat.f factor.f -lpg -lX11
The first library referenced (/local/lib/libpg.a) is a library of
graphics routines, compiled under an earlier version of OSF/1; the
X11 library is the standard one included with this version (v3.2c)
of Digital UNIX. If all the libpg.a routines which are referenced
by this program are commented out (or replaced by a bunch of dummy
stub routines), the DECladebug problem goes away.
So ... It appears that the problem is related to the use of this
library. But are there known incompatibilities between older and
current .o files which confuse DECladebug?
For the record, the "file" command tells me the following about .o
files from the library and those compiled under v3.2c: Both types
are identified as ...
COFF format alpha executable or object module not stripped
... but the ones created by the v3.2c compiler are "version 3.12-6"
whereas .o files in libpg.a are "version 3.11-0". Is the problem
related to this, or is it something more subtle? (And, if .o file
incompatibility is the cause of the problem, do we really have to
recompile all our old libraries in order to use DECladebug on any
program which uses them?)
Mark Bartelt 416/978-5619
Canadian Institute for mark_at_cita.toronto.edu
Theoretical Astrophysics mark_at_cita.utoronto.ca
"Nur eine Waffel taugt!" -- Parsifal, in an Eggo commercial
Received on Thu Nov 30 1995 - 15:22:21 NZDT