On 05-12-24 14:19, Wojciech Bocer wrote:
Hello, I have a problem with Valgrind taking a lot of time trying to determine if there are memory leaks before it exits.
Roughly speaking leak detection involves scanning though all accessible memory using pointer-size alignment to look for any pointers to unfreed memory blocks. This code does handle segfaults.
I don't have any real idea why the combination of x86 and Docker gives large numbers of segfaults and a major slowdown.
I suggest that you get the source for Valgrind and set these macros in mc_leakcheck.c to 1
// Define to debug the memory-leak-detector. #define VG_DEBUG_FIND_CHUNK 0 #define VG_DEBUG_LEAKCHECK 0 #define VG_DEBUG_CLIQUE 0 and then build Valgrind. A+ Paul _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
