-
Lucas De Marchi authored
Keep valgrind happy with the normal allocations so we can find the real leaks. Avoid this kind of leak: ==806592== 8 bytes in 1 blocks are definitely lost in loss record 46 of 188 ==806592== at 0x4846828: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==806592== by 0x4BD534E: strdup (strdup.c:42) ==806592== by 0x10E6AA: parse_options (settings.c:863) ==806592== by 0x10D2DD: main (runner.c:19) This only fixes the leaks on success. The error path handling on both igt_resume and igt_runner will need some more work on how they are interacting with all the initializations/cleanups. Tested-by:
Peter Senna Tschudin <peter.senna@linux.intel.com> Reviewed-by:
Gustavo Sousa <gustavo.sousa@intel.com> Link: https://lore.kernel.org/r/20250207231039.2883195-4-lucas.demarchi@intel.com Signed-off-by:
Lucas De Marchi <lucas.demarchi@intel.com>
Lucas De Marchi authoredKeep valgrind happy with the normal allocations so we can find the real leaks. Avoid this kind of leak: ==806592== 8 bytes in 1 blocks are definitely lost in loss record 46 of 188 ==806592== at 0x4846828: malloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so) ==806592== by 0x4BD534E: strdup (strdup.c:42) ==806592== by 0x10E6AA: parse_options (settings.c:863) ==806592== by 0x10D2DD: main (runner.c:19) This only fixes the leaks on success. The error path handling on both igt_resume and igt_runner will need some more work on how they are interacting with all the initializations/cleanups. Tested-by:
