| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[lldb/crashlog] Show help when the command is called without any argument This patch changes the crashlog command behavior to print the help message if no argument was provided with the command. rdar://94576026 Differential Revision: https://reviews.llvm.org/D127362 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com> | 4 年前 | |
[lldb] Support Python imports relative the to the current file being sourced Make it possible to use a relative path in command script import to the location of the file being sourced. This allows the user to put Python scripts next to LLDB command files and importing them without having to specify an absolute path. To enable this behavior pass -c to command script import. The argument can only be used when sourcing the command from a file. rdar://68310384 Differential revision: https://reviews.llvm.org/D89334 | 5 年前 | |
[lldb] Drop REQUIRES where redundant because of lit.local.cfg | 4 年前 | |
Revert a LIT typo fix in a RUN line Commit 573531f changes the behavior of the test, revert it back. | 4 年前 | |
[lldb/Python] Fix the infinitely looping Python prompt bug Executing commands below will get you bombarded by a wall of Python command prompts (>>> ). $ echo 'foo' | ./bin/lldb -o script $ cat /tmp/script script print("foo") $ lldb --source /tmp/script The issue is that our custom input reader doesn't handle EOF. According to the Python documentation, file.readline always includes a trailing newline character unless the file ends with an incomplete line. An empty string signals EOF. This patch raises an EOFError when that happens. [1] https://docs.python.org/2/library/stdtypes.html#file.readline Differential revision: https://reviews.llvm.org/D81898 | 5 年前 | |
[lldb] Skip ScriptInterpreter/Python/exit.test on Windows | 4 年前 | |
[lldb] Drop REQUIRES where redundant because of lit.local.cfg | 4 年前 | |
[lldb/Test] Use lit.local.cfg to mark whole directory as (un)supported. Mark the whole Python or Lua test directory as unsupported when the corresponding language is not available. | 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 | 4 年前 | |
[lldb] Drop REQUIRES where redundant because of lit.local.cfg | 4 年前 | |
[lldb] Drop REQUIRES where redundant because of lit.local.cfg | 4 年前 | |
[LLDB/Python] Fix segfault on Python scripted entrypoints The code that gets the ScriptInterpreter was not considering the case that it receives a Lua interpreter. Differential Revision: https://reviews.llvm.org/D92249 | 5 年前 | |
[lldb] Drop REQUIRES where redundant because of lit.local.cfg | 4 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 4 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 6 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 4 年前 |