Files
clang-p2996/lldb/test/API/commands/expression/options/TestExprOptions.py
Michael Buch 38f8fcea34 [lldb][ClangExpressionParser] Don't by default enable Objecitve-C support when evaluating C++ expressions (#87767)
This patch attempts to decouple C++ expression evaluation from
Objective-C support. We've previously enabled it by default (if a
runtime existed), but that meant we're opting into extra work we only
need to do for Objective-C, which complicates/slows down C++ expression
evaluation. Of course there's a valid use-case for this, which is
calling Objective-C APIs when stopped in C++ frames (which Objective-C++
developers might want to do). In those cases we should really prompt the
user to add the `expr --language objc++` flag. To accomodate a likely
frequent use-case where a user breaks in a system C++ library (without
debug-symbols) but their application is actually an Objective-C app, we
allow Objective-C support in C++ expressions if the current frame
doesn't have debug-info.

This fixes https://github.com/llvm/llvm-project/issues/75443 and allows
us to add more `LangOpts.ObjC` guards around the expression evaluator in
the future (e.g., we could avoid looking into the Objective-C runtime
during C++ expression evaluation, which we currently do
unconditionally).

Depends on https://github.com/llvm/llvm-project/pull/87657
2024-04-11 20:30:48 +02:00

88 lines
2.9 KiB
Python

"""
Test expression command options.
Test cases:
o test_expr_options:
Test expression command options.
"""
import lldb
import lldbsuite.test.lldbutil as lldbutil
from lldbsuite.test.decorators import *
from lldbsuite.test.lldbtest import *
class ExprOptionsTestCase(TestBase):
def setUp(self):
# Call super's setUp().
TestBase.setUp(self)
self.main_source = "main.cpp"
self.main_source_spec = lldb.SBFileSpec(self.main_source)
self.line = line_number("main.cpp", "// breakpoint_in_main")
self.exe = self.getBuildArtifact("a.out")
def test_expr_options(self):
"""These expression command options should work as expected."""
self.build()
# Set debugger into synchronous mode
self.dbg.SetAsync(False)
(target, process, thread, bkpt) = lldbutil.run_to_source_breakpoint(
self, "// breakpoint_in_main", self.main_source_spec
)
frame = thread.GetFrameAtIndex(0)
options = lldb.SBExpressionOptions()
# test --language on C++ expression using the SB API's
# Make sure we can evaluate a C++11 expression.
val = frame.EvaluateExpression("foo != nullptr")
self.assertTrue(val.IsValid())
self.assertSuccess(val.GetError())
self.DebugSBValue(val)
# Make sure it still works if language is set to C++11:
options.SetLanguage(lldb.eLanguageTypeC_plus_plus_11)
val = frame.EvaluateExpression("foo != nullptr", options)
self.assertTrue(val.IsValid())
self.assertSuccess(val.GetError())
self.DebugSBValue(val)
# Make sure it fails if language is set to C:
options.SetLanguage(lldb.eLanguageTypeC)
val = frame.EvaluateExpression("foo != nullptr", options)
self.assertTrue(val.IsValid())
self.assertFalse(val.GetError().Success())
def test_expr_options_lang(self):
"""These expression language options should work as expected."""
self.build()
# Set debugger into synchronous mode
self.dbg.SetAsync(False)
(target, process, thread, bkpt) = lldbutil.run_to_source_breakpoint(
self, "// breakpoint_in_main", self.main_source_spec
)
frame = thread.GetFrameAtIndex(0)
options = lldb.SBExpressionOptions()
# Make sure we can retrieve `id` variable if language is set to C++11:
options.SetLanguage(lldb.eLanguageTypeC_plus_plus_11)
val = frame.EvaluateExpression("id == 0", options)
self.assertTrue(val.IsValid())
self.assertSuccess(val.GetError())
self.DebugSBValue(val)
# Make sure we can't retrieve `id` variable if language is set to ObjC:
options.SetLanguage(lldb.eLanguageTypeObjC)
val = frame.EvaluateExpression("id == 0", options)
self.assertTrue(val.IsValid())
self.assertFalse(val.GetError().Success())