History log of /external/lldb/source/Interpreter/OptionValueFileSpec.cpp
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
97a19b21dacd9063bb5475812df7781777262198 29-Apr-2013 Greg Clayton <gclayton@apple.com> Cleanup logging to use the new "std::string FileSpec::GetPath()" function. Also added a similar function for modules:

std::string
Module::GetSpecificationDescription () const;

This returns the module as "/usr/lib/libfoo.dylib" for normal files (calls "std::string FileSpec::GetPath()" on m_file) but it also might include the object name in case the module is for a .o file in a BSD archive ("/usr/lib/libfoo.a(bar.o)"). Cleaned up necessary logging code to use it.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@180717 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Interpreter/OptionValueFileSpec.cpp
eff83203b6895f472f208f881d2e30b2e029a67a 15-Mar-2013 Sean Callanan <scallanan@apple.com> Rolled back r176719 because settings with file
names were broken.

<rdar://problem/13422580>


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@177139 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Interpreter/OptionValueFileSpec.cpp
5243ff89c0b02fb2a6dc2df75ae716ccf656b363 08-Mar-2013 Sean Callanan <scallanan@apple.com> OptionValueFileSpec shouldn't be doing argument
parsing on the file name it gets. That confuses
it if there are spaces in the file name.

<rdar://problem/13380392>


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@176719 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Interpreter/OptionValueFileSpec.cpp
f509c5ec066599a3399fced39ea36996184939e8 29-Jan-2013 Enrico Granata <egranata@apple.com> <rdar://problem/12978143>

Data formatters now cache themselves.
This commit provides a new formatter cache mechanism. Upon resolving a formatter (summary or synthetic), LLDB remembers the resolution for later faster retrieval.
Also moved the data formatters subsystem from the core to its own group and folder for easier management, and done some code reorganization.
The ObjC runtime v1 now returns a class name if asked for the dynamic type of an object. This is required for formatters caching to work with the v1 runtime.
Lastly, this commit disposes of the old hack where ValueObjects had to remember whether they were queried for formatters with their static or dynamic type.
Now the ValueObjectDynamicValue class works well enough that we can use its dynamic value setting for the same purpose.




git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@173728 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Interpreter/OptionValueFileSpec.cpp
ba687bbd7c07fe4a3b896ff320c7dc03e6d45b74 10-Dec-2012 Greg Clayton <gclayton@apple.com> <rdar://problem/12827031>

Fix the OptionValueFileSpec option value to correctly get the file path when trailing spaces are on the path. The "settings set" command uses the OptionValueFileSpec class to set file paths and if extra spaces are at the end it will include those in the paths. Now we chop up the value send to to OptionValueFileSpec::SetValueFromCString(...) function with "lldb_private::Args" and give an appropriate error if more than one path is used. It also allows for quotes to be used when specifying the path.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@169753 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Interpreter/OptionValueFileSpec.cpp
d891f9b872103235cfd2ed452c6f14a4394d9b3a 05-Dec-2012 Daniel Malea <daniel.malea@intel.com> Fix Linux build warnings due to redefinition of macros:
- add new header lldb-python.h to be included before other system headers
- short term fix (eventually python dependencies must be cleaned up)

Patch by Matt Kopec!




git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@169341 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Interpreter/OptionValueFileSpec.cpp
fb332f9349eff4e19051768a6fc3fb681984ef3a 11-Oct-2012 Jason Molenda <jmolenda@apple.com> When OptionValueFileSpec is given a filename starting
with ~, we need to realpath it. Fixes the case where

settings set target.expr-prefix ~/lldb.prefix.header

wouldn't read this prefix header file. <rdar://problem/12475676>


git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@165704 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Interpreter/OptionValueFileSpec.cpp
437b5bccea45a5981edbbbeb4e23424aec4ce774 28-Sep-2012 Greg Clayton <gclayton@apple.com> 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



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@164806 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Interpreter/OptionValueFileSpec.cpp
fc04d2463ad654c28f9ee2ee836174cc86b7f8b8 30-Aug-2012 Greg Clayton <gclayton@apple.com> 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.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@162921 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Interpreter/OptionValueFileSpec.cpp
c6e82e4a323d7a7168b05365c53c9bc2e0d418e3 22-Aug-2012 Greg Clayton <gclayton@apple.com> Remove further outdated "settings" code and also implement a few missing things.



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@162376 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Interpreter/OptionValueFileSpec.cpp
73844aa19a7360b662e2be710fc3c969d6c86606 22-Aug-2012 Greg Clayton <gclayton@apple.com> 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".



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@162366 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/source/Interpreter/OptionValueFileSpec.cpp