aboutsummaryrefslogtreecommitdiff
path: root/llvm/unittests/ExecutionEngine/Orc/LibraryResolverTest.cpp
diff options
context:
space:
mode:
authorMichael Buch <michaelbuch12@gmail.com>2025-10-27 09:39:25 +0000
committerMichael Buch <michaelbuch12@gmail.com>2025-10-27 10:01:07 +0000
commit313b95f3a8d7efaf8970484c169f1a106bc12f68 (patch)
tree8210307648cc0530a4b077fe5a56a45fd4398765 /llvm/unittests/ExecutionEngine/Orc/LibraryResolverTest.cpp
parent538c8509efe8bcfcc0b1b6ad40dbc72b735e7fb5 (diff)
downloadllvm-313b95f3a8d7efaf8970484c169f1a106bc12f68.zip
llvm-313b95f3a8d7efaf8970484c169f1a106bc12f68.tar.gz
llvm-313b95f3a8d7efaf8970484c169f1a106bc12f68.tar.bz2
[lldb][test] Add test for parsing Objective-C synthesized properties
Prior to https://github.com/llvm/llvm-project/pull/164998, recent LLDB versions would fail to parse synthesized property setters correctly. The only way this failure would manifest is an error to the console: ``` error: main.o [0x00000000000000cd]: invalid Objective-C method DW_TAG_subprogram (DW_TAG_subprogram), please file a bug and attach the file at the start of this error message ``` There weren't any Objective-C tests that failed when the original regression (https://github.com/llvm/llvm-project/pull/100355) landed. This patch adds a test that explicitly checks that the type of the setter is sensible. This test fails without https://github.com/llvm/llvm-project/pull/164998 and passes with it. I decided not to check for the absence of the console error because that kind of test would be fragile to the removal of (or any changes to) the error message.
Diffstat (limited to 'llvm/unittests/ExecutionEngine/Orc/LibraryResolverTest.cpp')
0 files changed, 0 insertions, 0 deletions