Conference turris::decladebug

924.0. "Problem with untriggered base class" by CXXC::MJHANS (Matthew Hanselman, DEC C/C++) Fri Apr 11 1997 10:57

    DEC C++ T5.6-001 and ladebug 4.0-35:
    
    ladebug behaves differently for untriggered classes, depending on
    whether or not they are base classes.  A "whatis" on an untriggered
    base class gets a "Not in scope" error, while a "whatis" on an
    untriggered non-base class gives an "opaque" message.  The untriggered
    base class should also be opaque.
    
    ------------------------
    
    class NoBase {
      int trigger();  // Note not triggered
    } nobase_var;
    
    class Base {
      int trigger();  // Note not triggered
    } base_var;
    
    class Derived : Base {
      int data;
    } derived_var;
    
    main(){}
    
    -------------------------
    
    % ladebug a.out
    Welcome to the Ladebug Debugger Version 4.0-35
    ------------------ 
    object file name: a.out 
    Reading symbolic information ...done
    (ladebug) whatis NoBase
    class NoBase <opaque>
    (ladebug) whatis Base
    Symbol Base not visible in current scope.
    
    
    							- Matt

Thanks for the report.  Actually, this was a known problem and
I've been working on it for the past day or so.

- Steve

This is fixed in 4.0-36...


(ladebug) whatis Base
class Base <opaque>