Conference turris::decladebug

952.0. "Assertion check loading image" by STEVEN::hobbs (Steven Hobbs) Mon May 12 1997 11:45

I am debugging a program with illegal floating values in registers and
I decided to switch from dbx to the new ladebug.  Here is what
happens:

steven-344> ladebug
Welcome to the Ladebug Debugger Version 4.0-37
(ladebug) load /usr/users/hobbs/tst/hydro2d/ladebug.out
Reading symbolic information ...Assertion failed: symlist->next() == NULL src/libsrc/ladebug/parsesymscoff.C 6844
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 ...
0x1246e084
0x12466700
0x12466274
0x124658a0
0x124645e8
0x1259c5f4
0x12580c48
0x123bde88
0x123be0bc
0x12394950
0x122475dc
0x1224b45c
0x12396000
0x1223651c
0x1225f00c
0x12232af4
0x122370e0
0x1222712c
0x1222426c
end of diagnostic stack trace.
Could not start process for /usr/users/hobbs/tst/hydro2d/ladebug.out
No image loaded ... Recovering ... 
(ladebug)

The dbx debugger debugs this file OK so I am back to dbx.  Let me know
when you have made a copy of ladebug.out so I can clean up this
directory.  The ladebug.out is the result of compiling the hydro2d
SPECmark benchmark with the latest BL36 GEM based f77 with -g3 and
-O4.  This version of f77 is about to go to field test.

This is a GEM problem.  Bob Monteleone is aware of it.

    
    
    This is only broken in GEM BL36, which has not shipped to customers
    yet. I have a fix, which I am now testing - I will post a final note
    after I complete the checkin of the fix.
    
    Bob
    
    

    
    
    Fixed in GEM...
    
    Bob