FWIW, I just out found that I can trivially work around this problem by
changing the order of object files passed to the linker.
It turns out that lldb will just pick up the first type named "Transform" in
the binary (regardless of namespace). Now, if I make sure that the object file
containing
Hi,
The list of Euro LLVM dev meeting technical talks, lightning talks, posters
and BoFs is now available on the LLVM website.
http://llvm.org/devmtg/2018-04/index.html#talks
Get your tickets from:
https://www.eventbrite.com/e/2018-european-llvm-developers-meeting-bristol-tickets-42283244322
If
Yes, the code was assuming that "exact_match" would be obeyed so it explicitly
specified returning only 1 match. When exact doesn't work, that means you get
the first one... You will only have a problem with the one whose name matches
both types, since the other way around the vtable name will
I've managed to unbreak the LLDB debugger as much as possible with the
current kernel and hit problems with ptrace(2) that are causing issues
with further work on proper NetBSD support. Meanwhile, I've upstreamed
all the planned NetBSD patches to sanitizers and helped other BSDs to
gain better or i
