Add missing error kinds for Memcheck into XML output protocol 4.

Error kinds have been re-ordered to match MC_ErrorTag.
Patch by: John Davis <jedavis@alumni.cmu.edu>

diff --git a/docs/internals/xml-output-protocol4.txt b/docs/internals/xml-output-protocol4.txt
index 65c055da8d6db3d0edc8dff961cb7c09b4520a92..3703bbd0250b806ba90c387c34a5260be6903719 100644 (file)
--- a/docs/internals/xml-output-protocol4.txt
+++ b/docs/internals/xml-output-protocol4.txt
@@ -9,9 +9,8 @@ are four variants of Protocol 4, one for each tool, since they
 produce different errors.  The four variants differ only in the
 definition of the ERROR nonterminal and are otherwise identical.
 
-NOTE that Protocol 4 (for the current svn trunk, which will eventually
-become 3.7.x) is still under development.  The text herein should not
-be regarded as the final definition.
+NOTE that Protocol 4 (for the current git master) is still under development.
+The text herein should not be regarded as the final definition.
 
 
 Identification of Protocols
@@ -498,14 +497,17 @@ KIND for Memcheck
 This is a small enumeration indicating roughly the nature of an error.
 The possible values are:
 
-   InvalidFree
+   UninitValue
 
-      free/delete/delete[] on an invalid pointer
+      other use of undefined value (primarily memory addresses)
 
-   MismatchedFree
+   UninitCondition
 
-      free/delete/delete[] does not match allocation function
-      (eg doing new[] then free on the result)
+      conditional jump/move depends on undefined value
+
+   CoreMemError
+
+      caused by unaddressable bytes in a signal handler frame
 
    InvalidRead
 
@@ -519,30 +521,27 @@ The possible values are:
 
       jump to an invalid address
 
-   Overlap
-
-      args overlap other otherwise bogus in eg memcpy
-
-   InvalidMemPool
+   SyscallParam
 
-      invalid mem pool specified in client request
+      system call params are undefined or point to
+      undefined/unaddressible memory
 
-   UninitCondition
+   ClientCheck
 
-      conditional jump/move depends on undefined value
+      "error" resulting from a client check request
 
-   UninitValue
+   InvalidFree
 
-      other use of undefined value (primarily memory addresses)
+      free/delete/delete[] on an invalid pointer
 
-   SyscallParam
+   MismatchedFree
 
-      system call params are undefined or point to
-      undefined/unaddressible memory
+      free/delete/delete[] does not match allocation function
+      (eg doing new[] then free on the result)
 
-   ClientCheck
+   Overlap
 
-      "error" resulting from a client check request
+      args overlap other otherwise bogus in eg memcpy
 
    Leak_DefinitelyLost
 
@@ -562,6 +561,15 @@ The possible values are:
 
       memory leak; pointers to un-freed blocks are still available
 
+   InvalidMemPool
+
+      invalid mem pool specified in client request
+
+   FishyValue
+
+      arguments to memory allocation function are very large,
+      indicating probable integer overflow or cast from negative signed
+
 
 ====================================================================