Enrico Granata 9fb5ab558b Our commands that end up displaying a ValueObject as part of their workflow use OptionGroupValueObjectDisplay as their currency for deciding the final representation ...

ValueObjects themselves use DumpValueObjectOptions as the currency for the same purpose

The code to convert between these two units was replicated (to varying degrees of correctness) in several spots in the code
This checkin provides one and only one (and hopefully correct :-) entry point for this conversion

llvm-svn: 178044

2013-03-26 18:04:53 +00:00

..

Args.cpp

<rdar://problem/13184855>

2013-03-05 23:52:49 +00:00

CMakeLists.txt

Adding CMake build system to LLDB. Some known issues remain:

2013-02-21 20:58:22 +00:00

CommandInterpreter.cpp

<rdar://problem/13404189>

2013-03-13 18:25:49 +00:00

CommandObject.cpp

Convert from the C-based LLVM Disassembler shim to the full MC Disassembler API's.

2013-03-02 00:26:47 +00:00

CommandObjectRegexCommand.cpp

The regular expression command object was resetting the execution context of the

2013-03-15 22:18:26 +00:00

CommandObjectScript.cpp

*ahem* Enrico.

2013-02-20 23:51:13 +00:00

CommandObjectScript.h

Fix a few more clang (3.2) warnings on Linux:

2012-12-07 22:21:08 +00:00

CommandReturnObject.cpp

<rdar://problem/13069948>

2013-01-25 18:06:21 +00:00

embedded_interpreter.py

Split up the Python script interpreter code to allow multiple script interpreter objects to

2011-01-14 00:29:16 +00:00

Makefile

Fix a few more clang (3.2) warnings on Linux:

2012-12-07 22:21:08 +00:00

OptionGroupArchitecture.cpp

<rdar://problem/12798131>

2012-12-04 00:32:51 +00:00

OptionGroupBoolean.cpp

<rdar://problem/12798131>

2012-12-04 00:32:51 +00:00

OptionGroupFile.cpp

<rdar://problem/12798131>

2012-12-04 00:32:51 +00:00

OptionGroupFormat.cpp

Fix clang warnings related to python macro redefinition and printf format specifiers.

2013-02-21 23:55:31 +00:00

OptionGroupOutputFile.cpp

<rdar://problem/12798131>

2012-12-04 00:32:51 +00:00

OptionGroupPlatform.cpp

<rdar://problem/12990038>

2013-01-11 20:49:54 +00:00

OptionGroupString.cpp

<rdar://problem/12798131>

2012-12-04 00:32:51 +00:00

OptionGroupUInt64.cpp

<rdar://problem/12798131>

2012-12-04 00:32:51 +00:00

OptionGroupUUID.cpp

<rdar://problem/12798131>

2012-12-04 00:32:51 +00:00

OptionGroupValueObjectDisplay.cpp

Our commands that end up displaying a ValueObject as part of their workflow use OptionGroupValueObjectDisplay as their currency for deciding the final representation

2013-03-26 18:04:53 +00:00

OptionGroupVariable.cpp

<rdar://problem/12978143>

2013-01-28 23:47:25 +00:00

OptionGroupWatchpoint.cpp

<rdar://problem/12798131>

2012-12-04 00:32:51 +00:00

Options.cpp

Define isprint8() wrapper around isprint() in order to avoid crashes on Linux

2012-12-05 20:24:57 +00:00

OptionValue.cpp

<rdar://problem/11757916>

2012-08-29 21:13:06 +00:00

OptionValueArch.cpp

<rdar://problem/12978143>

2013-01-28 23:47:25 +00:00

OptionValueArgs.cpp

Reimplemented the code that backed the "settings" in lldb. There were many issues with the previous implementation:

2012-08-22 17:17:09 +00:00

OptionValueArray.cpp

Resolve printf formatting warnings on Linux:

2012-11-29 21:49:15 +00:00

OptionValueBoolean.cpp

<rdar://problem/12022079>

2012-08-23 00:22:02 +00:00

OptionValueDictionary.cpp

<rdar://problem/12978143>

2013-01-28 23:47:25 +00:00

OptionValueEnumeration.cpp

Resolve printf formatting warnings on Linux:

2012-11-29 21:49:15 +00:00

OptionValueFileSpec.cpp

Rolled back r176719 because settings with file

2013-03-15 01:39:44 +00:00

OptionValueFileSpecLIst.cpp

Ran the sources through the compiler with -Wshadow warnings

2012-10-04 22:47:07 +00:00

OptionValueFormat.cpp

<rdar://problem/12978143>

2013-01-28 23:47:25 +00:00

OptionValuePathMappings.cpp

Ran the sources through the compiler with -Wshadow warnings

2012-10-04 22:47:07 +00:00

OptionValueProperties.cpp

Added the infrastructure necessary for plug-ins to be able to add their own settings instead of having settings added to existing ones. In particular "target.disable-kext-loading" was added to "target" where it should actually be specific to the the dynamic loader plugin. Now the plug-in manager has the ability to create settings at the root level starting with "plugin". Each plug-in type can add new sub dictionaries, and then each plug-in can register a setting dictionary under its own short name. For example the DynamicLoaderDarwinKernel plug-in now registers a setting dictionary at:

2012-10-19 18:02:49 +00:00

OptionValueRegex.cpp

Reimplemented the code that backed the "settings" in lldb. There were many issues with the previous implementation:

2012-08-22 17:17:09 +00:00

OptionValueSInt64.cpp

Resolve printf formatting warnings on Linux:

2012-11-29 21:49:15 +00:00

OptionValueString.cpp

Now that "settings set" will strip leading and trailing spaces, we need a way to be able to specify string values that contain spaces. So now settings setting <property> <value>" can have a <value> that is quoted:

2013-03-06 02:19:38 +00:00

OptionValueUInt64.cpp

Resolve printf formatting warnings on Linux:

2012-11-29 21:49:15 +00:00

OptionValueUUID.cpp

Fix Linux build warnings due to redefinition of macros:

2012-12-05 00:20:57 +00:00

Property.cpp

Fix Linux build warnings due to redefinition of macros:

2012-12-05 00:20:57 +00:00

PythonDataObjects.cpp

<rdar://problem/13069948>

2013-01-25 18:06:21 +00:00

ScriptInterpreter.cpp

Fix Linux build warnings due to redefinition of macros:

2012-12-05 00:20:57 +00:00

ScriptInterpreterNone.cpp

Fix Linux build warnings due to redefinition of macros:

2012-12-05 00:20:57 +00:00

ScriptInterpreterPython.cpp

This checkin removes the last Cocoa formatters that were implemented in Python and reimplements them in C++. The Python Cocoa formatters are not shipped as part of LLDB anymore, but still exist in the source repository for user reference. Python formatters still exist for STL classes and users can still define their own Python formatters

2013-03-19 00:27:22 +00:00