bcm5719-llvm/lldb/packages/Python/lldbsuite/test/lang/objc, branch meklort-10.0.1

[lldb/Test] Move @skipIfAsan from test class to test methods.

2020-01-06T17:53:06+00:00

skipTestIfFn can only be used to decorate a test method.

[lldb/Test] Temporarily skip TestFoundationDisassembly on the ASan bot.

2020-01-06T17:06:09+00:00

This test is timing out on the sanitized bot on GreenDragon. Temporarily disable it to increase the signal-to-noise ration.

[lldb] Added test for objc_direct calls with categories

2019-12-20T10:07:30+00:00

As pointed out in D71694 this wasn't tested before in LLDB.

[lldb] Add support for calling objc_direct methods from LLDB's expression evaluator.

2019-12-17T09:28:40+00:00

Summary: D69991 introduced `__attribute__((objc_direct))` that allows directly calling methods without message passing. This patch adds support for calling methods with this attribute to LLDB's expression evaluator. The patch can be summarised in that LLDB just adds the same attribute to our module AST when we find a method with `__attribute__((objc_direct))` in our debug information. Reviewers: aprantl, shafik Reviewed By: shafik Subscribers: JDevlieghere, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D71196

LanguageRuntime: Simplify NSException::GetSummary() output

2019-12-13T20:33:31+00:00

Summary: Right now, NSException::GetSummary() has the following output: "name: $exception_name - reason: $exception_reason" It would be better to simplify the output by removing the name and only showing the exception's reason. This way, annotations would look nicer in the editor, and would be a shorter summary in the Variables Inspector. Accessing the exception's name can still be done by expanding the NSException object in the Variables Inspector. rdar://54770115 Signed-off-by: Med Ismail Bennani Subscribers: lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D71311 Signed-off-by: Med Ismail Bennani

[lldb][NFC] Remove all `setUp` overrides that only call the parent implementation

2019-12-13T11:34:49+00:00

Summary: A lot of our tests copied the setUp code from our TestSampleTest.py: ``` def setUp(self): # Call super's setUp(). TestBase.setUp(self) ``` This code does nothing unless we actually do any setUp work in there, so let's remove all these method definitions. Reviewers: labath, JDevlieghere Reviewed By: labath Subscribers: lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D71454

[lldb][NFC] Remove 'from future import print_function' from all tests that don't actually call 'print()'

2019-12-13T11:23:04+00:00

Summary: A lot of tests do this trick but the vast majority of them don't even call `print()`. Most of this patch was generated by a script that just looks at all the files and deletes the line if there is no `print (` or `print(` anywhere else in the file. I checked the remaining tests manually and deleted the import if we never call print (but instead do stuff like `expr print(...)` and similar false-positives). I also corrected the additional empty lines after the import in the files that I manually edited. Reviewers: JDevlieghere, labath, jfb Reviewed By: labath Subscribers: dexonsmith, wuzish, nemanjai, kbarton, christof, arphaman, abidh, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D71452

Complete complete types early when importing types from Clang module DWARF.

2019-11-22T17:58:16+00:00

This affects -gmodules only. Under normal operation pcm_type is a shallow forward declaration that gets completed later. This is necessary to support cyclic data structures. If, however, pcm_type is already complete (for example, because it was loaded for a different target before), the definition needs to be imported right away, too. Type::ResolveClangType() effectively ignores the ResolveState inside type_sp and only looks at IsDefined(), so it never calls ClangASTImporter::ASTImporterDelegate::ImportDefinitionTo(), which does extra work for Objective-C classes. This would result in only the forward declaration to be visible. An alternative implementation would be to sink this into Type::ResolveClangType ( https://github.com/llvm/llvm-project/blob/88235812a71d99c082e7aa2ef9356d43d1f83a80/lldb/source/Symbol/Type.cpp#L5809) though it isn't clear to me how to best do this from a layering perspective. rdar://problem/52134074 Differential Revision: https://reviews.llvm.org/D70415

Add a testcase for Clang modules being updated within one LLDB session.

2019-11-16T00:27:14+00:00

This actually works as expected, but wasn't explicitly tested before.

[-gmodules] Let LLDB log a warning if the Clang module hash mismatches.

2019-11-15T19:52:13+00:00

This feature is mostly there to aid debugging of Clang module issues, since the only useful actual the end-user can to is to recompile their program. Differential Revision: https://reviews.llvm.org/D70272