> On Feb 6, 2017, at 3:38 PM, Robinson, Paul <paul.robin...@sony.com> wrote: > > It's not practical for the DWARF to try to identify the actual address of the > vtable; that address might not be available. > it seems like we could hang onto the linkage_name of the vtable though, > somewhere, so you wouldn't be relying on the demangler you have available at > runtime to produce the same string that the compiler did at compile time. > The symbolic name of the vtable should be unambiguous (one hopes!) but not > depend on the existence of the vtable in any particular place. > Doesn't solve the problem for today's compilers, granted. > --paulr > > P.S. It would be helpful to have these things come up *before* the next rev > of the spec is frozen. Just sayin'. J > <> We had just identified this today and realized it was a problem so we had no idea there was a problem until today. Debuggers have been doing this pretty reliably for the past 15 years, so it was never anything we actually needed extra support for since it was so easy to do.
Greg
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
