summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorsewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9>2009-08-16 22:56:53 +0000
committersewardj <sewardj@a5019735-40e9-0310-863c-91ae7b9d1cf9>2009-08-16 22:56:53 +0000
commit1ffe69e9b831fbd584afea304f8064936cc5d781 (patch)
tree35710f1006b119a68ae733d585b7c274e986180c /docs
parentf585e485d4e9881fbfaac828b4c9a9a2128556be (diff)
Comment that we never actually expect to see the string ]]> in a
generated suppression, and hence the problem of having to split it into multiple CDATA blocks is moot. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@10832 a5019735-40e9-0310-863c-91ae7b9d1cf9
Diffstat (limited to 'docs')
-rw-r--r--docs/internals/xml-output-protocol4.txt8
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/internals/xml-output-protocol4.txt b/docs/internals/xml-output-protocol4.txt
index 7da70a99..7db5d152 100644
--- a/docs/internals/xml-output-protocol4.txt
+++ b/docs/internals/xml-output-protocol4.txt
@@ -318,6 +318,14 @@ ending with data "]]" and the other beginning with data "<". This is
why the spec calls for one or more CDATA blocks rather than exactly
one.
+Note that, so far, we cannot envisage a circumstance in which a
+generated suppression would contain the string "]]>", since neither
+"]" nor ">" appear to turn up in mangled symbol names. Hence it is
+not envisaged that there will ever be more than one CDATA block, and
+indeed the implementation as of Valgrind 3.5.0 will only ever generate
+one block (it ignores any possible escaping problems). Nevertheless
+the specification allows multiple blocks, as a matter of safety.
+
SFRAME
------