| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
Revert "[lldb/crashlog] Make interactive mode the new default" (#96263) Reverts llvm/llvm-project#94575 since introduces test failure: https://green.lab.llvm.org/job/llvm.org/view/LLDB/job/as-lldb-cmake/6166/ | 2 年前 | |
[NFC][Py Reformat] Reformat python files in lldb This is an ongoing series of commits that are reformatting our Python code. Reformatting is done with black (23.1.0). If you end up having problems merging this commit because you have made changes to a python file, the best way to handle that is to run git checkout --ours <yourfile> and then reformat it with black. RFC: https://discourse.llvm.org/t/rfc-document-and-standardize-python-code-style Differential revision: https://reviews.llvm.org/D151460 | 3 年前 | |
[lldb] Drop REQUIRES where redundant because of lit.local.cfg | 5 年前 | |
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 | 6 年前 | |
[lldb] Skip ScriptInterpreter/Python/exit.test on Windows | 4 年前 | |
[lldb] Drop REQUIRES where redundant because of lit.local.cfg | 5 年前 | |
[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 | 5 年前 | |
[lldb] Drop REQUIRES where redundant because of lit.local.cfg | 5 年前 | |
[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 | 5 年前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 2 年前 | ||
| 3 年前 | ||
| 5 年前 | ||
| 4 年前 | ||
| 6 年前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 6 年前 | ||
| 4 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 | ||
| 5 年前 |