What would help a lot is to have a VALGRIND request, like
VALGRIND_DO_CLIENT_REQUEST_STMT, that we could use in our signal
handler to turn off leak checking.
In valgrind-3.16 (to be released in 3 days; RC2 available today) see
valgrind --help-dyn-options
___
On Fri, 2020-05-22 at 15:22 +0300, Michael Widenius wrote:
> Hi!
> I have searched documentation, internet and header files like
> memcheck.h, but not found a solution:
>
> When running the MariaDB test suite under valgrind, we sometimes may
> get a core dump. In this case, the leaked memory repo
I am not too familiar with memcheck, but there are client requests to
enable/disable checks within a memory range using
VG_USERREQ__ENABLE_ADDR_ERROR_REPORTING_IN_RANGE and
VG_USERREQ__DISABLE_ADDR_ERROR_REPORTING_IN_RANGE.
On Fri, May 22, 2020 at 8:24 AM Michael Widenius
wrote:
>
> Hi!
> I have
Hi!
I have searched documentation, internet and header files like
memcheck.h, but not found a solution:
When running the MariaDB test suite under valgrind, we sometimes may
get a core dump. In this case, the leaked memory report can be very
long and will be totally useless.
What would help a lot
