A copy/paste error in GetClassInfoUtilityFunction resulted in the wrong
utility function being returned: copyRealizedClassList instead of
getRealizedClassList_trylock.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Oh boy, these are scary. Should LLDB fail harder when the utility expression fails, so we can detect these earlier?
Comment Actions
Fortunately we print an error, but we're also pretty resilient against some of this information missing. This bug was particularly tricky because it only causes a problem the second time that you execute the utility function, which only occurs when you have lazily instantiated classes (in Swift) which is why we didn't see this on llvm.org