Author: Adrian Prantl
Date: 2019-12-11T13:30:05-08:00
New Revision: 0ca0fba94d48959a8c5d1e074c8242e46b263d59

URL: 
https://github.com/llvm/llvm-project/commit/0ca0fba94d48959a8c5d1e074c8242e46b263d59
DIFF: 
https://github.com/llvm/llvm-project/commit/0ca0fba94d48959a8c5d1e074c8242e46b263d59.diff

LOG: Add resurrecting Type Validators to projects.rst

Added: 
    

Modified: 
    lldb/docs/status/projects.rst

Removed: 
    


################################################################################
diff  --git a/lldb/docs/status/projects.rst b/lldb/docs/status/projects.rst
index 703a3c67d68a..48081da59578 100644
--- a/lldb/docs/status/projects.rst
+++ b/lldb/docs/status/projects.rst
@@ -408,3 +408,12 @@ 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.
+
+Resurrect Type Validators
+-------------------------
+
+This half-implemented feature was removed in
+https://reviews.llvm.org/D71310 but the general idea might still be
+useful: Type Validators look at a ValueObject, and make sure that
+there is nothing semantically wrong with the object's contents to
+easily catch corrupted data.


        
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to