Re: How to disable leak check from inside a program
Derrick McKee <[email protected]>
| Newsgroups | gmane.comp.debugging.valgrind |
|---|---|
| Message-ID | <CAJoBWHxBEsMqhA2k+DqrvL_XRmmJ5u_e6zEAgXXcHR1NSdAnkg@mail.gmail.com> |
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 <[email protected]> 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 report can be very > long and will be totally useless. > > 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. > > Is that possible and if not, is that something that could get > implemented in the future? > Is this something that anyone else has ever requested ? > > Regards, > Monty > > > _______________________________________________ > Valgrind-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/valgrind-users -- Derrick McKee Phone: (703) 957-9362 Email: [email protected]