|
From: John D. <je...@al...> - 2017-08-16 01:44:23
|
Dear Valgrind developers,
I've been writing a tool which uses Memcheck's xml output, and noticed that
it could generate two error types not listed in the documentation for the
xml protocol. This patch adds documentation for these error types (to the
best of my understanding of them).
Diff:
-----------
diff --git a/docs/internals/xml-output-protocol4.txt
b/docs/internals/xml-output-protocol4.txt
index 65c055da8..f06e91234 100644
--- a/docs/internals/xml-output-protocol4.txt
+++ b/docs/internals/xml-output-protocol4.txt
@@ -540,6 +540,15 @@ The possible values are:
system call params are undefined or point to
undefined/unaddressible memory
+ FishyValue
+
+ arguments to memory allocation function are very large,
+ indicating probable integer overflow or cast from negative signed
+
+ CoreMemError
+
+ caused by unaddressable bytes in a signal handler frame
+
ClientCheck
"error" resulting from a client check request
--------------------------------------------------------------------------------------
I apologize if I have erred; I have no experience with diff/patch-based
workflows, and little with valgrind's internals.
Thanks,
John Davis
|
|
From: Ivo R. <iv...@iv...> - 2017-08-17 08:22:40
|
2017-08-16 3:19 GMT+02:00 John Davis <je...@al...>: > Dear Valgrind developers, > > I've been writing a tool which uses Memcheck's xml output, and noticed that > it could generate two error types not listed in the documentation for the > xml protocol. This patch adds documentation for these error types (to the > best of my understanding of them). John, Thank you for the report. Please have a look at the attached patch. I. |
|
From: Ivo R. <iv...@iv...> - 2017-08-18 11:59:16
|
2017-08-16 3:19 GMT+02:00 John Davis <je...@al...>: > Dear Valgrind developers, > > I've been writing a tool which uses Memcheck's xml output, and noticed that > it could generate two error types not listed in the documentation for the > xml protocol. John, Thank you for the patch. It has been integrated as commit 6c05c0edf42c76ccbc9180c848006adf4951cbf9: https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=6c05c0edf42c76ccbc9180c848006adf4951cbf9 I. |
|
From: John D. <je...@al...> - 2017-08-18 15:34:29
|
Looks good, thanks Ivo! On Fri, Aug 18, 2017 at 7:59 AM, Ivo Raisr <iv...@iv...> wrote: > 2017-08-16 3:19 GMT+02:00 John Davis <je...@al...>: > > Dear Valgrind developers, > > > > I've been writing a tool which uses Memcheck's xml output, and noticed > that > > it could generate two error types not listed in the documentation for the > > xml protocol. > > John, > > Thank you for the patch. It has been integrated as > commit 6c05c0edf42c76ccbc9180c848006adf4951cbf9: > https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h= > 6c05c0edf42c76ccbc9180c848006adf4951cbf9 > > I. > |