This is an archive of the discontinued LLVM Phabricator instance.

[lldb] Add a test for potentially conflicting names for the Objective-C class update utility expression
ClosedPublic

Authored by teemperor on Aug 9 2021, 11:47 AM.

Details

Summary

We recently had an issue where a user declared a Class::free function which then got picked up by accident
by the expression evaluator when calling ::free. This was due to a too lax filter in the
DWARFIndex (which was fixed by https://reviews.llvm.org/D73191 ). This broke the Objective-C utility
expression that is trying to update the Objective-C class list (which is calling :;free).

This adds a regression test for situations where we have a bunch of functions defined that share
the name of the global functions that this utility function calls. None of them are actually conflicting
with the global functions we are trying to call (they are all in namespaces, objects or classes).

Diff Detail

Event Timeline

teemperor requested review of this revision.Aug 9 2021, 11:47 AM
teemperor created this revision.
JDevlieghere accepted this revision.Aug 9 2021, 11:52 AM

Thank you, LGTM

This revision is now accepted and ready to land.Aug 9 2021, 11:52 AM
This revision was landed with ongoing or failed builds.Aug 10 2021, 5:46 AM
This revision was automatically updated to reflect the committed changes.
Herald added a project: Restricted Project. · View Herald TranscriptAug 10 2021, 5:46 AM