MMed Ismail Bennani[lldb/crashlog] Show help when the command is called without any argument
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[lldb/crashlog] Fix line entries resolution in interactive mode This patch subtracts 1 to the pc of any frame above frame 0 to get the previous line entry and display the right line in the debugger. This also rephrase some old comment from 48d157dd4. rdar://92686666 Differential Revision: https://reviews.llvm.org/D125928 Signed-off-by: Med Ismail Bennani <medismail.bennani@gmail.com> | 4 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
[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> | 3 年前 | |
[lldb] Use __lldb_init_module instead of "if lldb.debugger" idiom Update examples and docs to demonstrate using __lldb_init_module instead of the idiom that checks for lldb.debugger at the top-level. if __name__ == '__main__': ... elif lldb.debugger: ... Is replaced with: if __name__ == '__main__': ... def __lldb_init_module(debugger, internal_dict): ... This change is for two reasons. First, it's generally encouraged not to only use the convenience singletons (lldb.{debugger,process,target,etc}) interactively from the script command. Second, there's a bug where registering a python class as a command (using command script add -c ...), result in the command not being runnable. Note that registering function-backed commands does not have this bug. Differential Revision: https://reviews.llvm.org/D117237 | 4 年前 | |
Python 2/3 compatibility: from __future__ import print_function Differential Revision: https://reviews.llvm.org/D59580 llvm-svn: 356695 | 7 年前 | |
[lldb] Use __lldb_init_module instead of "if lldb.debugger" idiom Update examples and docs to demonstrate using __lldb_init_module instead of the idiom that checks for lldb.debugger at the top-level. if __name__ == '__main__': ... elif lldb.debugger: ... Is replaced with: if __name__ == '__main__': ... def __lldb_init_module(debugger, internal_dict): ... This change is for two reasons. First, it's generally encouraged not to only use the convenience singletons (lldb.{debugger,process,target,etc}) interactively from the script command. Second, there's a bug where registering a python class as a command (using command script add -c ...), result in the command not being runnable. Note that registering function-backed commands does not have this bug. Differential Revision: https://reviews.llvm.org/D117237 | 4 年前 | |
*** This commit represents a complete reformatting of the LLDB source code *** to conform to clang-format’s LLVM style. This kind of mass change has *** two obvious implications: Firstly, merging this particular commit into a downstream fork may be a huge effort. Alternatively, it may be worth merging all changes up to this commit, performing the same reformatting operation locally, and then discarding the merge for this particular commit. The commands used to accomplish this reformatting were as follows (with current working directory as the root of the repository): find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} + find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ; The version of clang-format used was 3.9.0, and autopep8 was 1.2.4. Secondly, “blame” style tools will generally point to this commit instead of a meaningful prior commit. There are alternatives available that will attempt to look through this change and find the appropriate prior commit. YMMV. llvm-svn: 280751 | 9 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
Add an example command to toggle between disassembly-only and source mode. Sometimes you are debugging in source, but you really only want to see the disassembly. That's easy to do but you have to set a few variables. This command toggles between your old values, and a disassembly only mode. llvm-svn: 300902 | 9 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
[lldb] Use __lldb_init_module instead of "if lldb.debugger" idiom Update examples and docs to demonstrate using __lldb_init_module instead of the idiom that checks for lldb.debugger at the top-level. if __name__ == '__main__': ... elif lldb.debugger: ... Is replaced with: if __name__ == '__main__': ... def __lldb_init_module(debugger, internal_dict): ... This change is for two reasons. First, it's generally encouraged not to only use the convenience singletons (lldb.{debugger,process,target,etc}) interactively from the script command. Second, there's a bug where registering a python class as a command (using command script add -c ...), result in the command not being runnable. Note that registering function-backed commands does not have this bug. Differential Revision: https://reviews.llvm.org/D117237 | 4 年前 | |
[lldb] Fix python errors in gdbremote.py Fix exceptions encountered while debugging gdb protocol Differential Revision: https://reviews.llvm.org/D120792 | 4 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
[Examples] Move structured-data unpacking out of the loop. (NFC) There's no need to repeat this work in the loop. | 6 年前 | |
[lldb] Use __lldb_init_module instead of "if lldb.debugger" idiom Update examples and docs to demonstrate using __lldb_init_module instead of the idiom that checks for lldb.debugger at the top-level. if __name__ == '__main__': ... elif lldb.debugger: ... Is replaced with: if __name__ == '__main__': ... def __lldb_init_module(debugger, internal_dict): ... This change is for two reasons. First, it's generally encouraged not to only use the convenience singletons (lldb.{debugger,process,target,etc}) interactively from the script command. Second, there's a bug where registering a python class as a command (using command script add -c ...), result in the command not being runnable. Note that registering function-backed commands does not have this bug. Differential Revision: https://reviews.llvm.org/D117237 | 4 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
[lldb] Use __lldb_init_module instead of "if lldb.debugger" idiom Update examples and docs to demonstrate using __lldb_init_module instead of the idiom that checks for lldb.debugger at the top-level. if __name__ == '__main__': ... elif lldb.debugger: ... Is replaced with: if __name__ == '__main__': ... def __lldb_init_module(debugger, internal_dict): ... This change is for two reasons. First, it's generally encouraged not to only use the convenience singletons (lldb.{debugger,process,target,etc}) interactively from the script command. Second, there's a bug where registering a python class as a command (using command script add -c ...), result in the command not being runnable. Note that registering function-backed commands does not have this bug. Differential Revision: https://reviews.llvm.org/D117237 | 4 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
[lldb] [gdb-remote server] Introduce new stop reasons for fork and vfork Introduce three new stop reasons for fork, vfork and vforkdone events. This includes server support for serializing fork/vfork events into gdb-remote protocol. The stop infos for the two base events take a pair of PID and TID for the newly forked process. Differential Revision: https://reviews.llvm.org/D100196 | 5 年前 | |
[lldb] Fix typos. NFC. Differential Revision: https://reviews.llvm.org/D103381 | 5 年前 | |
Python 2/3 compatibility: from __future__ import print_function Differential Revision: https://reviews.llvm.org/D59580 llvm-svn: 356695 | 7 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
Python 2/3 compatibility: from __future__ import print_function Differential Revision: https://reviews.llvm.org/D59580 llvm-svn: 356695 | 7 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
[lldb] Use __lldb_init_module instead of "if lldb.debugger" idiom Update examples and docs to demonstrate using __lldb_init_module instead of the idiom that checks for lldb.debugger at the top-level. if __name__ == '__main__': ... elif lldb.debugger: ... Is replaced with: if __name__ == '__main__': ... def __lldb_init_module(debugger, internal_dict): ... This change is for two reasons. First, it's generally encouraged not to only use the convenience singletons (lldb.{debugger,process,target,etc}) interactively from the script command. Second, there's a bug where registering a python class as a command (using command script add -c ...), result in the command not being runnable. Note that registering function-backed commands does not have this bug. Differential Revision: https://reviews.llvm.org/D117237 | 4 年前 | |
Another silly little thing you can do with Python commands. Sometimes you want to step along and print a local each time as you go. You can do that with stop hooks, but that's a little heavy-weight. This is a sketch of a command that steps and then does "frame variable" on all its arguments. llvm-svn: 314958 | 8 年前 | |
[lldb][crashlog] Avoid specifying arch for image when a UUID is present When adding an image to a target for crashlog purposes, avoid specifying the architecture of the image. This has the effect of making SBTarget::AddModule infer the ArchSpec for the image based on the SBTarget's architecture, which LLDB puts serious effort into calculating correctly (in TargetList::CreateTargetInternal). The status quo is that LLDB randomly guesses the ArchSpec for a module if its architecture is specified, via: SBTarget::AddModule -> Platform::GetAugmentedArchSpec -> Platform::IsCompatibleArchitecture -> GetSupportedArchitectureAtIndex -> {ARM,x86}GetSupportedArchitectureAtIndex ... which means that the same crashlog can fail to load on an Apple Silicon Mac (due to the random guess of arm64e-apple-macosx for the module's ArchSpec not being compatible with the SBTarget's (correct) ArchSpec), while loading just fine on an Intel Mac. I'm not sure how to add a test for this (it doesn't look like there's test coverage of this path in-tree). It seems like it would be pretty complicated to regression test: the host LLDB would need to be built for arm64e, we'd need a hand-crafted arm64e iOS crashlog, and we'd need a binary with an iOS deployment target. I'm open to other / simpler options. rdar://82679400 Differential Revision: https://reviews.llvm.org/D110013 | 4 年前 | |
[lldb] Use __lldb_init_module instead of "if lldb.debugger" idiom Update examples and docs to demonstrate using __lldb_init_module instead of the idiom that checks for lldb.debugger at the top-level. if __name__ == '__main__': ... elif lldb.debugger: ... Is replaced with: if __name__ == '__main__': ... def __lldb_init_module(debugger, internal_dict): ... This change is for two reasons. First, it's generally encouraged not to only use the convenience singletons (lldb.{debugger,process,target,etc}) interactively from the script command. Second, there's a bug where registering a python class as a command (using command script add -c ...), result in the command not being runnable. Note that registering function-backed commands does not have this bug. Differential Revision: https://reviews.llvm.org/D117237 | 4 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 | |
Harmonize Python shebang Differential Revision: https://reviews.llvm.org/D83857 | 5 年前 |