Conference turris::decladebug

955.0. "assertion failure with code compiled with 6.0 C++ compiler" by DECC::J_WARD () Fri May 16 1997 12:20

I'm getting a ladebug assertion error when trying to get a stack trace
with an executable that's been created with the EDG mainline
compiler.

I know that namespace TDI's are giving me some errors/warnings,
but Matt said that shouldn't mess things up enough to
cause a core dump.

The a.out is in ~j_ward/public on cosf.

I've also noticed that the file names/line numbers and function names
are usually not right.

(ladebug) run
Thread received signal SEGV
stopped at [locale::locale(const complex&):495 0x120022984]
(Cannot read source line 495 of ../cms_test/tests/test_rw_complex_complex.cxx)
(ladebug) where
>0  0x120022984 in ((locale*)0x11fffdca8)->locale(other=<bad reference>)
../cms_test/test
s/test_rw_complex_complex.cxx:495
#1  0x120022a5c in widen__Q13std36basic_ios__TcQ13std15char_traits__TcCXc(c=' ')
../cms_headers/ios:391
#2  0x120022b64 in init(sb=0x0Error: Unexpected symbol found in symbols for file
[../cms_headers/iosfwd, #982].
Error: symbol for 'std' of type [Module] will be ignored.
Warning: all future symbols of type [Module] will be silently ignored.
Assertion failed: ptrToScopeStackRecEntry src/libsrc/ladebug/parsesymscoff.C 5076
This is an unexpected condition and may indicate the presence of a defect.
If you wish to report this, please include the stack trace that follows.
Diagnostic stack trace ...
0x1246abe0
0x124667b0
0x12466274
0x124658a0
0x124645e8
0x1259c5f4
0x12580c48
0x1257fb68
0x123bde88
0x123bfef8
0x123f8678
0x123e9c94
0x123e9dc4
0x124cc3b4
0x1229a490
0x1229b798
0x1229b214
0x1229b88c
0x1229bef0
0x12232af4
0x122370e0
0x1222712c
0x1222426c
end of diagnostic stack trace.