🚀 go-pugleaf

I thought that I had grabbed and applied patches to fix
some of the bugs reported in gdb 4.6 running on a Sparc,
debugging g++ 2.2.2; however, I have noted that I still
have the following problems: 


1) Printing the value of class members takes a very long
time--often up to 20 seconds. 


2) When printing members, gdb often reports that there is
"no such member", even if the ptype command shows the
member to be present. 


3) Often gdb reports that it cannot locate a member
function, that it "may be inlined", when it is clearly not
so. 


4) Sometimes gdb seems to be at the wrong function level;
when asked "whatis this" while inside Foo::function(),
it will reply "class Bar *". 


5) The ptype command seems to choke on certain member
function names: 


(gdb) ptype Data
type = class Data : public ivSubject {
  protected:
    struct DataRep *rep;
    unsigned int noUpdate;
    unsigned int isModified;
  public:
    virtual ~Data(void);
    <badly mangled name __4Data__4Datai>;
    <badly mangled name __4Data__4Datai8DataTypeii>;
    <badly mangled name __4Data__4DataiP7DataRep>;
    <badly mangled name __4Data__4DataiPT0>;
    <badly mangled name __4Data__4DataiRT0>;
  protected:
    struct DataRep * new_rep(Data, DataFile *, Header *);
    struct DataRep * new_rep(Data, DataType, int, int);
  public:
...
[those names, from the header file, were as follows:
public:
        Data();
        Data(DataType type, int length, int chans=1);
        Data(DataRep *dr);
        Data(Data *d);  // special constructor for type conversion
        Data(Data &);
]

I know that these have all been reported at one time or
another...I am interested in knowing how many of these
have temporarily been fixed.  I am patiently awaiting
4.7, but would be glad for a bit more help with the current
version. 


Thanks!!

---
Douglas Scott                              (805)893-8352
Center for Computer Music Research and Composition
University of California, Santa Barbara
Internet: (NeXTMail ok)   <doug@foxtrot.ccmrc.ucsb.edu>