can't find class named `foo', as given by C++ RTTI

Benjamin Kosnik
Thu Jun 28 01:32:00 GMT 2001

> We already rely on being able to get mangled names from debug info too
> much.  This is why the clone constructors have the wrong name (they
> end up being fred() instead of fred::fred()).  Their
> specification has no DW_AT_MIPS_linkage_name, because it can't.  They
> have no DW_AT_MIPS_linkage_name beause they shouldn't need to.
> What really should be happening is that we should be generating
> qualified names on our own, and ignoring DW_AT_MIPS_linkage_name
> completely.

Ah. I get it now. So this namespace issue is probably the same problem that 
nested types are having...

I was wondering about the ctor issue.

> And we should be properly supporting namespaces, using directives,
> etc, anyway.  It would also let us be able to support java packages
> properly and whatnot.

These are all required features in gdb, not optional features, right?

> I can make gcc output this info in about a day.

Well then.

> i've got a collection of references for symbol table
> designs that can handle these things properly and efficiently, and
> close enough to the existing basic symbol table structure that you
> wouldn't have to start anywhere near from scratch, or come up with a
> design on your own.

Might as well post the links or citations if you've got them handy.


More information about the Gdb mailing list