Files
clang-p2996/lldb/test/API/functionalities/multidebugger_commands/TestMultipleDebuggersCommands.py
Jordan Rupprecht 9c2468821e [lldb][test] Modernize asserts (#82503)
This uses [teyit](https://pypi.org/project/teyit/) to modernize asserts,
as recommended by the [unittest release
notes](https://docs.python.org/3.12/whatsnew/3.12.html#id3).

For example, `assertTrue(a == b)` is replaced with `assertEqual(a, b)`.
This produces better error messages, e.g. `error: unexpectedly found 1
and 2 to be different` instead of `error: False`.
2024-02-21 13:02:30 -06:00

51 lines
1.6 KiB
Python

"""
Test that commands do not try and hold on to stale CommandInterpreters in a multiple debuggers scenario
"""
import lldb
from lldbsuite.test.decorators import *
from lldbsuite.test.lldbtest import *
from lldbsuite.test import lldbutil
class MultipleDebuggersCommandsTestCase(TestBase):
@no_debug_info_test
def test_multipledebuggers_commands(self):
"""Test that commands do not try and hold on to stale CommandInterpreters in a multiple debuggers scenario"""
source_init_files = False
magic_text = "The following commands may relate to 'env'"
debugger_1 = lldb.SBDebugger.Create(source_init_files)
interpreter_1 = debugger_1.GetCommandInterpreter()
retobj = lldb.SBCommandReturnObject()
interpreter_1.HandleCommand("apropos env", retobj)
self.assertIn(
magic_text,
str(retobj),
"[interpreter_1]: the output does not contain the correct words",
)
if self.TraceOn():
print(str(retobj))
lldb.SBDebugger.Destroy(debugger_1)
# now do this again with a different debugger - we shouldn't crash
debugger_2 = lldb.SBDebugger.Create(source_init_files)
interpreter_2 = debugger_2.GetCommandInterpreter()
retobj = lldb.SBCommandReturnObject()
interpreter_2.HandleCommand("apropos env", retobj)
self.assertIn(
magic_text,
str(retobj),
"[interpreter_2]: the output does not contain the correct words",
)
if self.TraceOn():
print(str(retobj))
lldb.SBDebugger.Destroy(debugger_2)