[lldb] Clarify StructuredDataImpl ownershipStructuredDataImpl ownership semantics is unclear at best. Variousstructures were holding a non-owning pointer to it, with a comment thatthe object is o
[lldb] Clarify StructuredDataImpl ownershipStructuredDataImpl ownership semantics is unclear at best. Variousstructures were holding a non-owning pointer to it, with a comment thatthe object is owned somewhere else. From what I was able to gather that"somewhere else" was the SBStructuredData object, but I am not sure thatall created object eventually made its way there. (It wouldn't mattereven if they did, as we are leaking most of our SBStructuredDataobjects.)Since StructuredDataImpl is just a collection of two (shared) pointers,there's really no point in elaborate lifetime management, so this patchreplaces all StructuredDataImpl pointers with actual objects orunique_ptrs to it. This makes it much easier to resolve SBStructuredDataleaks in a follow-up patch.Differential Revision: https://reviews.llvm.org/D114791
show more ...
[lldb] Remove extern "C" from lldb-swig-lua interfaceThis is the lua equivalent of 9a14adeae0.
[lldb/lua] Add scripted watchpoints for LuaAdd support for Lua scripted watchpoints, with basic tests.Differential Revision: https://reviews.llvm.org/D105034
[lldb] Remove ScriptInterpreterLuaTest.Plugin unittestThis test is not useful as the functions it's testing are just returninga constant. It also fails in unoptimized builds as it's comparingchar
[lldb] Remove ScriptInterpreterLuaTest.Plugin unittestThis test is not useful as the functions it's testing are just returninga constant. It also fails in unoptimized builds as it's comparingcharacter strings by address.
[lldb/Lua] add support for Lua function breakpointAdds support for running a Lua function when a breakpoint is hit.Example: breakpoint command add -s lua -F abcThe above runs the Lua functio
[lldb/Lua] add support for Lua function breakpointAdds support for running a Lua function when a breakpoint is hit.Example: breakpoint command add -s lua -F abcThe above runs the Lua function 'abc' passing 2 arguments. 'frame', 'bp_loc' and 'extra_args'.A third parameter 'extra_args' is only present when there is structured datadeclared in the command line.Example: breakpoint command add -s lua -F abc -k foo -v barDifferential Revision: https://reviews.llvm.org/D93649
[LLDB/Lua] add support for one-liner breakpoint callbackThese callbacks are set using the following: breakpoint command add -s lua -o "print('hello world!')"The user supplied script is execute
[LLDB/Lua] add support for one-liner breakpoint callbackThese callbacks are set using the following: breakpoint command add -s lua -o "print('hello world!')"The user supplied script is executed as: function (frame, bp_loc, ...) <body> endSo the local variables 'frame', 'bp_loc' and vararg are all accessible.Any global variables declared will persist in the Lua interpreter.A user should never hold 'frame' and 'bp_loc' in a global variable asthese userdatas are context dependent.Differential Revision: https://reviews.llvm.org/D91508
[lldb] Get rid of helper CMake variables for PythonThis patch is a big sed to rename the following variables: s/PYTHON_LIBRARIES/Python3_LIBRARIES/g s/PYTHON_INCLUDE_DIRS/Python3_INCLUDE_DIRS/
[lldb] Get rid of helper CMake variables for PythonThis patch is a big sed to rename the following variables: s/PYTHON_LIBRARIES/Python3_LIBRARIES/g s/PYTHON_INCLUDE_DIRS/Python3_INCLUDE_DIRS/g s/PYTHON_EXECUTABLE/Python3_EXECUTABLE/g s/PYTHON_RPATH/Python3_RPATH/gI've also renamed the CMake module to better express its purpose and forconsistency with FindLuaAndSwig.Differential revision: https://reviews.llvm.org/D85976
[lldb/Interpreter] Support color in CommandReturnObjectColor the error: and warning: part of the CommandReturnObject output,similar to how an error is printed from the driver when colors areenabl
[lldb/Interpreter] Support color in CommandReturnObjectColor the error: and warning: part of the CommandReturnObject output,similar to how an error is printed from the driver when colors areenabled.Differential revision: https://reviews.llvm.org/D81058
[Lldb/Lua] Generate Lua BindingsThis patch uses SWIG to generate the Lua bindings for the SB API. Itcovers most of the API, but some methods require a type map similar toPython.Discussion on th
[Lldb/Lua] Generate Lua BindingsThis patch uses SWIG to generate the Lua bindings for the SB API. Itcovers most of the API, but some methods require a type map similar toPython.Discussion on the mailing list:http://lists.llvm.org/pipermail/lldb-dev/2019-December/015812.htmlDifferential revision: https://reviews.llvm.org/D71235
[lldb/Lua] Implement a Simple Lua Script Interpreter PrototypeThis implements a very elementary Lua script interpreter. It supportsrunning a single command as well as running interactively. It use
[lldb/Lua] Implement a Simple Lua Script Interpreter PrototypeThis implements a very elementary Lua script interpreter. It supportsrunning a single command as well as running interactively. It useseditline if available. It's still missing a bunch of stuff though. Somethings that I intentionally ingored for now are that I/O isn't properlyhooked up (so every print goes to stdout) and the non-editline supportwhich is not handling a bunch of corner cases. The latter is a matter ofreusing existing code in the Python interpreter.Discussion on the mailing list:http://lists.llvm.org/pipermail/lldb-dev/2019-December/015812.htmlDifferential revision: https://reviews.llvm.org/D71234