This guide explains Linux's virtual‑physical memory model, shows how to inspect system and process memory via /proc files, demonstrates a 100 MiB allocation test, and provides a step‑by‑step workflow—including ps sorting and Valgrind usage—to locate and fix memory leaks.
This article explains what memory leaks are in C++ on Linux, why they matter, how they occur, and provides practical guidance on detecting them with tools like Valgrind, AddressSanitizer, GDB, and mtrace, followed by concrete solutions such as proper new/delete usage, smart pointers, RAII, custom allocators, and memory pools.
This article provides a comprehensive guide to C++ debugging, covering the installation, core commands, and practical examples of GDB and Valgrind, along with advanced techniques, common pitfalls, and best‑practice recommendations to help developers efficiently locate and fix memory and segmentation errors.
This article explains what memory out-of-bounds errors are, why they are dangerous in Linux C programs, and provides step‑by‑step debugging methods using logs, GDB, Valgrind, core dumps, mprotect, static analysis, and preventive coding practices.
This article provides an in‑depth overview of Valgrind, explaining its architecture, the capabilities of its various tools such as Memcheck, Cachegrind, Callgrind, Helgrind and Massif, and offers step‑by‑step installation, configuration, and practical code examples for detecting memory errors, leaks, and performance bottlenecks in C/C++ programs.
This article explains Linux CPU cache architecture—from physical and logical cores, through L1/L2/L3 hierarchy and cache‑line basics, to write‑through/write‑back policies and coherence mechanisms—while demonstrating practical analysis with Valgrind and perf tools.
This article introduces Valgrind, outlines its main debugging tools, provides step‑by‑step installation and usage instructions on Linux, demonstrates memory‑error detection with a sample C program, and explains how to cross‑compile Valgrind for ARM targets.
After noticing abnormal memory usage in a production service, the author traced a leak to a race condition in shared data during a C++ code refactor, demonstrated the debugging steps, explained why traditional tools like Valgrind help, and shared lessons on avoiding multithreaded memory leaks.
This article examines why MySQL instances are often targeted by the Linux OOM killer, explains proper InnoDB buffer pool sizing, introduces memory leak concepts, and demonstrates how to use Valgrind's Memcheck tool to detect leaks and improve database memory management.
This article introduces three popular Linux performance profiling tools—Perf, gprof, and Valgrind—explaining their installation, basic command‑line usage, and how to visualize results with flame graphs, call graphs, or KCachegrind, while comparing their intrusiveness, startup methods, and output formats.
The article details how to identify and resolve memory leaks and performance bottlenecks in high‑concurrency Nginx workloads using tools such as Valgrind, AddressSanitizer, perf and flame‑graphs, while also sharing practical tips and personal reflections on debugging under pressure.
This article details a real‑world investigation of extremely low‑probability core dumps and memory leaks in a heavily modified Nginx/OpenSSL stack, covering debugging strategies, custom traffic‑control testing, distributed load generation, use of valgrind and AddressSanitizer, performance profiling with perf, and the mindset needed to solve such high‑concurrency bugs.
The article describes a real‑world investigation of extremely rare core‑dump bugs and memory‑leak issues in a heavily modified Nginx+OpenSSL stack under high‑concurrency, detailing the debugging workflow, custom stress‑test tools, use of gdb, valgrind, AddressSanitizer, perf, flame graphs and performance‑tuning lessons.
This article shares a detailed post‑mortem of debugging extremely rare core dumps and memory leaks in a high‑concurrency Nginx HTTPS implementation, covering root‑cause analysis, custom stress‑test frameworks, and the use of tools such as gdb, valgrind, AddressSanitizer, perf and flame graphs to locate and fix the issues.
