[lldb] Drop REQUIRES where redundant because of lit.local.cfg

2021-07-09T20:25:10+00:00

[lldb] Don't print script output twice in HandleCommand

2021-06-08T20:57:39+00:00

When executing a script command in HandleCommand(s) we currently print
its output twice
You can see this issue in action when adding a breakpoint command:

(lldb) b main
Breakpoint 1: where = main.out`main + 13 at main.cpp:2:3, address = 0x0000000100003fad
(lldb) break command add 1 -o "script print(\"Hey!\")"
(lldb) r
Process 76041 launched: '/tmp/main.out' (x86_64)
Hey!
(lldb)  script print("Hey!")
Hey!
Process 76041 stopped

The issue is caused by HandleCommands using a temporary
CommandReturnObject and one of the commands (`script` in this case)
setting an immediate output stream. This causes the result to be printed
twice: once directly to the immediate output stream and once when
printing the result of HandleCommands.

This patch fixes the issue by introducing a new option to suppress
immediate output for temporary CommandReturnObjects.

Differential revision: https://reviews.llvm.org/D103349

[lldb/Lua] Make lldb.debugger et al available to Lua

2020-01-09T16:15:41+00:00

The Python script interpreter makes the current debugger, target,
process, thread and frame available to interactive scripting sessions
through convenience variables. This patch does the same for Lua.

Differential revision: https://reviews.llvm.org/D71801

llvm-project.git/lldb/test/Shell/ScriptInterpreter/Lua/nested_sessions.test, branch main

[lldb] Drop REQUIRES where redundant because of lit.local.cfg

[lldb] Don't print script output twice in HandleCommand

[lldb/Lua] Make lldb.debugger et al available to Lua