| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[lldb] Fix Lua/watchpoint_callback.test on Apple Silicon As Pavel pointed out, on Apple Silicon "b main" stops at a point after the variable has already been initialized. This patch updates the test case to avoids that. I've also split the test into separate files so its easier to reproduce the individual scenarios without having to build any shared state. | 4 年前 | |
[lldb/ScriptInterpreter] Unify error message for command script import Rather than checking for Python explicitly, let the script interpreter handle things and print an error if the functionality is not supported. | 6 年前 | |
Fix script -lpython to handle control flow in one-line commands. The fix is to append a newline to the source being evaluated. Without this patch, the following commands **print no output, no errors**. (lldb) script if "foo" in lldb.frame.name: print(lldb.thread) (lldb) script for f in lldb.thread: print(f.name) The issue is with code.InteractiveConsole.runsource(). A trailing newline is needed for these expressions to be evaluated. I don't know why this is, the docs don't mention anything. From a python repl, the following samples show that a terminal newline allows statements containing flow control to fully execute. >>> import code >>> repl = code.InteractiveConsole() >>> repl.runsource("if True: print(1)") True >>> repl.runsource("if True: print(1)\n") 1 False Notes: From an interactive python repl, the output is not printed immediately. The user is required to enter a blank line following the first. >>> if True: print(1) ... 1 However, python -c 'if True: print(1)' works without needing a newline. Reviewed By: JDevlieghere Differential Revision: https://reviews.llvm.org/D127586 | 3 年前 |