# Configure the project and generate a native build system:
  # Must re-run this command whenever any CMakeLists.txt file has been changed.
  cmake -S ./ -B build/
# Compile and build the project:
  # rebuild only files that are modified since the last build
  cmake --build build/
  # or rebuild everything from scracth
  cmake --build build/ --clean-first
  # to see verbose output, do:
  cmake --build build/ --verbose
# Run program:
  ./build/app/shell-app
# Clean
  cmake --build build/ --target clean
# Clean and start over:
  rm -rf build/

valgrind --leak-check=full --track-origins=yes ./build/app/shell-app > <OUTPUT_file-txt> 2>&1

• Unitialized variable in main.
• Memory had to be deallocated for the pointer.

• out__commented.txt
• out_modifiedcode_commented.txt
• out_not_commented.txt

• What happens when the executable is linked statically? It tries to compile everything in one single executable.

• Does Valgrind still detect those same bugs? If the executable is linked statically, Valgrind detects a broader range of memory-related errors, potentially resulting in false negatives, where actual issues are overlooked.

• Why not? This is because numerous libraries in the shell-app and the CMake build of the project are dynamic. When you link libraries statically, their memory management behavior becomes integrated into your program's build, such as with CMake in this project. Valgrind may not distinguish between memory allocated by your program and that allocated by these libraries.

  valgrind.org answer:

  If your program is statically linked, most Valgrind tools will only work well if they are able to replace certain functions, such as malloc, with their own versions. By default, statically linked malloc functions are not replaced. A key indicator of this is if Memcheck says:

  All heap blocks were freed -- no leaks are possible

  when you know your program calls malloc. The workaround is to use the option --soname-synonyms=somalloc=NONE or to avoid statically linking your program.

  There will also be no replacement if you use an alternative malloc library such as tcmalloc, jemalloc, ... In such a case, the option --soname-synonyms=somalloc=zzzz (where zzzz is the soname of the alternative malloc library) will allow Valgrind to replace the functions.