Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Wrapped up the work I am going to do for now for the "add-dsym" or "target ↵ | Greg Clayton | 2012-09-27 | 1 | -1/+51 |
| | | | | | | | | | | | | | | | | | | | | symfile add" command. We can now do: Specify a path to a debug symbols file: (lldb) add-dsym <path-to-dsym> Go and download the dSYM file for the "libunc.dylib" module in your target: (lldb) add-dsym --shlib libunc.dylib Go and download the dSYM given a UUID: (lldb) add-dsym --uuid <UUID> Go and download the dSYM file for the current frame: (lldb) add-dsym --frame llvm-svn: 164806 | ||||
* | Reimplemented the code that backed the "settings" in lldb. There were many ↵ | Greg Clayton | 2012-08-22 | 1 | -0/+70 |
issues with the previous implementation: - no setting auto completion - very manual and error prone way of getting/setting variables - tons of code duplication - useless instance names for processes, threads Now settings can easily be defined like option values. The new settings makes use of the "OptionValue" classes so we can re-use the option value code that we use to set settings in command options. No more instances, just "does the right thing". llvm-svn: 162366 |