Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[lldb/test] Add test for the scripting template list command #101726

Merged
merged 1 commit into from
Aug 2, 2024
Merged

[lldb/test] Add test for the scripting template list command #101726

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
42 changes: 42 additions & 0 deletions lldb/test/Shell/Commands/command-scripting-template-list.test
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
# REQUIRES: python
# RUN: %lldb -s %s -o exit | FileCheck %s

scripting template list
# CHECK:Available scripted extension templates:

# CHECK: Name: OperatingSystemPythonInterface
# CHECK-NEXT: Language: Python
# CHECK-NEXT: Description: Mock thread state
# CHECK-NEXT: API Usages: None
# CHECK-NEXT: Command Interpreter Usages:
# CHECK-NEXT: settings set target.process.python-os-plugin-path <script-path>
# CHECK-NEXT: settings set process.experimental.os-plugin-reports-all-threads [0/1]

# CHECK: Name: ScriptedPlatformPythonInterface
# CHECK-NEXT: Language: Python
# CHECK-NEXT: Description: Mock platform and interact with its processes.
# CHECK-NEXT: API Usages: None
# CHECK-NEXT: Command Interpreter Usages: None

# CHECK: Name: ScriptedProcessPythonInterface
# CHECK-NEXT: Language: Python
# CHECK-NEXT: Description: Mock process state
# CHECK-NEXT: API Usages:
# CHECK-NEXT: SBAttachInfo.SetScriptedProcessClassName
# CHECK-NEXT: SBAttachInfo.SetScriptedProcessDictionary
# CHECK-NEXT: SBTarget.Attach
# CHECK-NEXT: SBLaunchInfo.SetScriptedProcessClassName
# CHECK-NEXT: SBLaunchInfo.SetScriptedProcessDictionary
# CHECK-NEXT: SBTarget.Launch
# CHECK-NEXT: Command Interpreter Usages:
# CHECK-NEXT: process attach -C <script-name> [-k key -v value ...]
# CHECK-NEXT: process launch -C <script-name> [-k key -v value ...]

# CHECK: Name: ScriptedThreadPlanPythonInterface
# CHECK-NEXT: Language: Python
# CHECK-NEXT: Description: Alter thread stepping logic and stop reason
# CHECK-NEXT: API Usages: SBThread.StepUsingScriptedThreadPlan
# CHECK-NEXT: Command Interpreter Usages: thread step-scripted -C <script-name> [-k key -v value ...]

scripting template list -l lua
# CHECK: Available scripted extension templates: None
Comment on lines +41 to +42
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you get the same output regardless of whether you're building with or without lua support? If so then this is fine, otherwise this would have to go into a separate test that contains REQUIRES: lua.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I tested locally without Lua support.

Loading