00:00Valgrind is a powerful suite of debugging and profiling tools for Linux.
00:05Its default and most popular tool is MemCheck, which detects memory leaks, invalid reads, slash writes, and use of uninitialized
00:13memory in C and C++ programs.
00:16Step 1. Install.
00:18Valgrind, open your Linux terminal and install Valgrind using your Distributions Package Manager, Ubuntu, Slack, and J, slash, Mint, Fedora,
00:27slash, Rails, Salty, Esch, Sudo, DNF, install Valgrind.
00:33Arch, Lies, Sudo, Passman, As, Valgrind.
00:36Verify the installation, Valgrind, version.
00:40Use code with caution.
00:42Step 2. Compile your program with debug symbols.
00:45To make Valgrind's error reports, point to the exact line numbers in your source code rather than just memory addresses.
00:52Compile your program with the DIQ flag using GCC or G++.
00:58GCT dash use.
00:59Oh, my my program, my my program, my my dot C.
01:03Use code with caution.
01:05Tip. Using those zero turns off compiler optimizations, preventing the compiler from moving or rewriting code in ways that can
01:11make debugging harder.
01:12Step 3. Run your program with Valgrind.
01:15Run Valgrind on your compiled binary the same way you normally would run it, prefixing the command with Valgrind.
01:21Valgrind. Valgrind.
01:23May Shami program use code with caution.
01:26By default, Valgrind launches its MemCheck tool and prints diagnostic output to your terminal as your program executes.
01:33Step 4. Read and interpret the output Valgrind.
01:36Output can look intimidating, but it breaks down into a few critical sections.
01:41Process ID and header shows the Valgrind version and the PID monitoring the run.
01:47Error reports. If any, if your code has bugs, you will see blocks like this.
01:53In Dalit Read Write, you access memory outside of an allocated array or buffer.
01:57Conditional jump depends on uninitialized value. You use a variable before assigning a value to it.
02:02Source slash destination overlap. A misuse of functions like StessiPy or MemCopy.
02:08Each error gives a stack trace showing the exact function and line number where the issue occurred.
02:14Heap summary. At the end of the run, Valgrind displays a summary of dynamic memory usage.
02:21Definitely lost memory you allocated, for example, via malloc or new, that you never freed and lost all pointers to
02:28a true memory leak.
02:31Indirectly lost memory loss because it was pointed to by a definitely lost block.
02:36Still reachable. Memory still allocated when the program exited, often global static variables or library caches.
02:42Not always a bug.
02:44Step 5. Useful flags to level up.
02:46You can add extra flags to get more detailed reports.
02:50Show leak details.
02:51Valgrind leak check exful dash my wukrogram. Use code with caution.
02:59Track where lost memory was allocated.
03:02Valgrind leak check equal full.
03:05Show leak kinds equals all track originese equals jess.
03:12My aunts program. Use code with caution.
03:14Lock output to a file instead of the terminal.
03:18Valgrind log file equal valgrindusrreport.txt my number corbrom. Use code with caution.
03:25And that's the full picture.
03:27If this saved you a search, hit like and subscribe.
03:30One clear answer.
03:32Every day.
03:33See you in the next one.
