|
From: Johan K. <Joh...@en...> - 2014-09-29 17:15:44
|
Hi all,
I have implemented Valgrind support for a custom allocator and now I'm having problem
that valgrind only reports illegal free errors on the first warning.
The problem is that Valgrind only looks at the top four functions and they are all in my allocator.
I suggest that we never duplicate illegal frees. It is such a big error that I don't think any application
would be offended by the change.
--- memcheck/mc_errors.c-org 2013-10-23 12:50:23.000000000 +0200
+++ memcheck/mc_errors.c 2014-09-29 19:10:39.081346384 +0200
@@ -1132,7 +1132,6 @@
return ( extra1->Err.User.isAddrErr == extra2->Err.User.isAddrErr
? True : False );
- case Err_Free:
case Err_FreeMismatch:
case Err_Jump:
case Err_IllegalMempool:
@@ -1140,6 +1139,9 @@
case Err_Cond:
return True;
+ case Err_Free:
+ return False;
+
case Err_Addr:
return ( extra1->Err.Addr.szB == extra2->Err.Addr.szB
? True : False );
Best regards,
Johan Karlsson
|