summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/value/TestValueAPI.py
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2018-10-24 22:04:20 +0000
committerJonas Devlieghere <jonas@devlieghere.com>2018-10-24 22:04:20 +0000
commit9c6c201b588634ca9388c28ed325d8f07c3adf2c (patch)
tree30d631d257608d8bb550678ffdf20e8bbbc91e85 /lldb/packages/Python/lldbsuite/test/python_api/value/TestValueAPI.py
parente9f9a2a29cd227b5e6d701d1f45081e3ba99921c (diff)
downloadbcm5719-llvm-9c6c201b588634ca9388c28ed325d8f07c3adf2c.tar.gz
bcm5719-llvm-9c6c201b588634ca9388c28ed325d8f07c3adf2c.zip
[Settings] Add -force flag to "settings set"
The -force option allows you to pass an empty value to settings set to reset the value to its default. This means that the following operations are equivalent: settings set -f <setting> settings clear <setting> The motivation for this change is the ability to export and import settings from LLDB. Because of the way the dumpers work, we don't know whether a value is going to be the default or not. Hence we cannot use settings clear and use settings set -f, potentially providing an empty value. Differential revision: https://reviews.llvm.org/D52772 llvm-svn: 345207
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/value/TestValueAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud