summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJim Ingham <jingham@apple.com>2019-07-25 21:37:57 +0000
committerJim Ingham <jingham@apple.com>2019-07-25 21:37:57 +0000
commit2b6afdf71046735671405902ae77b08874cd1d76 (patch)
tree7f312bbe52fbd55a791025f442afd0cbe379a66b
parent971f9ca612f22d251631f6b7dcc5efd8324bc0f2 (diff)
downloadbcm5719-llvm-2b6afdf71046735671405902ae77b08874cd1d76.tar.gz
bcm5719-llvm-2b6afdf71046735671405902ae77b08874cd1d76.zip
Mention adding predicates to settings in the projects page.
llvm-svn: 367059
-rw-r--r--lldb/docs/status/projects.rst14
1 files changed, 14 insertions, 0 deletions
diff --git a/lldb/docs/status/projects.rst b/lldb/docs/status/projects.rst
index d3433a780b9..5863897ce31 100644
--- a/lldb/docs/status/projects.rst
+++ b/lldb/docs/status/projects.rst
@@ -409,3 +409,17 @@ If we could predict the catching frame, we could do this right.
And of course, this would be a useful piece of information to display when stopped
at a throw point.
+
+Add predicates to the nodes of settings
+---------------------------------------
+
+It would be very useful to be able to give values to settings that are dependent
+on the triple, or executable name, for targets, or on whether a process is local
+or remote, or on the name of a thread, etc. The original intent (and there is
+a sketch of this in the settings parsing code) was to be able to say:
+
+::
+
+ (lldb) settings set target{arch=x86_64}.process.thread{name=foo}...
+
+The exact details are still to be worked out, however.
OpenPOWER on IntegriCloud