C
You're viewing a free preview. Sign in free to read every script.
Why this exists Memory bugs in C rarely fail where they happen. An overflow may corrupt data that crashes the program an hour later, or never crashes and simply leaks information. Three tools turn these silent problems…
Finding Bugs: gdb, Valgrind and the Sanitizers
A deliberately broken program and the tools that catch each bug: AddressSanitizer and UBSan at compile time, Valgrind for leaks and invalid access, and gdb for crashes with a backtrace, breakpoints and watchpoints.
Sign in free to read this script, along with the rest of the library.
Sign in free