From: Julian Seward Date: Sun, 16 Aug 2009 22:56:53 +0000 (+0000) Subject: Comment that we never actually expect to see the string ]]> in a X-Git-Tag: svn/VALGRIND_3_5_0~18 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=1d4a525a8c87b93e02495b8083088ad15ae0aae9;p=thirdparty%2Fvalgrind.git 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 --- diff --git a/docs/internals/xml-output-protocol4.txt b/docs/internals/xml-output-protocol4.txt index 7da70a99a0..7db5d152ae 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 ------