On 17/01/2025 09:14, Daniel Santos wrote:
Hi,
I was running valgrind with the —leak-check=yes option which gives a
very detailed output of memcheck.
Without that option, the probable memory leaks don’t appear any more.
I will make a simple test program, to test this, using the option set
to yes and post it here.
Thanks.
One possibility is a false positive. You could try using LeakSanitizer
('make -asan=yes' using the latest gnustep mak/base in the git
repository) to see if it agrees with valgrind.
Also, behavior of the leak detection may vary depending on how/when it's
executed (which will change what is considered a leak).
Anyway, if I have a test program and details on how to build to
reproduce the issue I can take a look.
