https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108083
--- Comment #3 from stefanos <ssofroni at cytanet dot com.cy> --- (In reply to Jonathan Wakely from comment #2) > (In reply to stefanos from comment #0) > > With my Makefile, I generate an executable with the following steps: > > > > ccache g++ -Wall -Wextra -Werror -Wpedantic -std=c++20 -g -Og > > -D_GLIBCXX_DEBUG -I src -c src/tmp.cpp -o obj/tmp.o > > You're not compiling with sanitizers, only linking: > > > ccache g++ obj/tmp.o -o bin/tmp -fno-strict-aliasing -fwrapv -lfmt -lm > > -fsanitize=address,undefined > > Your makefile is incorrect. Even if I do so, it does not trigger the memory leak...unless I misunderstood you. stefanos@debian:~/code/cpp/tmp $ make ccache g++ -Wall -Wextra -Werror -Wpedantic -std=c++20 -g -Og -D_GLIBCXX_DEBUG -fsanitize=address,undefined -I src -c src/tmp.cpp -o obj/tmp.o ccache g++ obj/tmp.o -o bin/tmp -fno-strict-aliasing -fwrapv -lfmt -lm -fsanitize=address,undefined make -j4 --jobserver-auth=3,4 got executed in debug mode... stefanos@debian:~/code/cpp/tmp $ bin/tmp histefanos@debian:~/code/cpp/tmp $
