I will need to pass this to Sean Callanan to see if he can tell anything. It might be a few days before he can get to it.
I'll let you know when I know more. > On Nov 4, 2015, at 12:10 PM, Ramkumar Ramachandra <artag...@gmail.com> wrote: > > Greg Clayton <gclay...@apple.com> wrote: >> Follow my previous suggestions: enable lldb expr logging and also compare >> the output of the two "frame variable F" for frame 0 and frame 4 in your >> previous example. Since "frame variable" always uses the type _only_ from >> liba.so or libb.so, we might be able to see a difference in the output of >> "frame variable F" for the two frames. If we don't see any difference, we >> need to dump the type from "image lookup --all -t "foo<int>" and see if we >> see any differences there. If we don't see differences we need to then step >> through the code that is attempting to import "foo<int>" the second time and >> see where it thinks the types differ. > > Wow, it looks like lldb is doing an *enormous* amount of work to > evaluate an expression. I've attached the logging on f 0 and f 4, as > well as the image lookup output (doesn't seem to differ?). > > I'll try to work my way through the dumps in the meantime. Let me know > if anything immediately stands out. > <lldb-f0-getname.log><lldb-f4-getname.log><lldb-im-loo-function.log> _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
