4 Commits

Author	SHA1	Message	Date
Greg Clayton	b5f0feabae	Wrapped up the work I am going to do for now for the "add-dsym" or "target 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	2012-09-27 22:26:11 +00:00
Greg Clayton	0b0b512fd6	OptionValueFileSpec had an accessor to read the contents of the file and return the data. This can end up being used to get the string contents of a text file and could end up not being NULL terminated. I added accessors to get the file contents raw, or with a null terminator. Added the needed calls to make this happen in the FileSpec and File classes. ... llvm-svn: 162921	2012-08-30 18:15:10 +00:00
Greg Clayton	6920b52be6	Remove further outdated "settings" code and also implement a few missing things. ... llvm-svn: 162376	2012-08-22 18:39:03 +00:00
Greg Clayton	67cc06366c	Reimplemented the code that backed the "settings" in lldb. There were many 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	2012-08-22 17:17:09 +00:00