LeakTracer(1)

✨ LeakTracer ✨ (manual name: LeakTracer(1))

bestie, okay so LeakTracer is a memory-usage debugger for C++ programs 🔍💜 and it is literally about to save your whole life 😭🫶

---

🌸 NAME 🌸

LeakTracer — a memory-usage debugger for C++ programs 💖

---

🎀 SYNOPSIS 🎀

LeakCheck program [ program arguments ... ]

leak-analyze program [ leak.out ] [ main ] [ program arguments ... ]

---

💅 DESCRIPTION 💅

okay so this page is about two commands, LeakCheck and leak-analyze 🦋

this page was written for the Debian distribution because the original program doesn't have a manual page of its own 🙈 it has HTML docs instead, which you'll find in the SEE ALSO section, no cap

LeakCheck is a little script that runs your C++ program and logs everything about calls to new and delete into a leak.out file 📝✨ it's giving tiny but mighty energy 🧚

leak-analyze gives you a human-readable report of what's inside a leak.out file 💜 it calls gdb(1) to display the faulty lines, so you can see exactly where things went wrong 😭🔥

---

👑 OPTIONS 👑

these programs don't take any special options 💀 for an explanation of the possible arguments to leak-analyze, check the full documentation, bestie 🌈

---

🦋 SEE ALSO 🦋

the official documentation lives in /usr/share/doc/leaktracer/README.*, available in both HTML and plain text 📚💖

• gdb(1)

---

🫶 AUTHOR 🫶

this manual page was written by Yann Dirson <dirson@debian.org> for the Debian system (but anyone can use it 🍓). permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1, as published by the Free Software Foundation, with no Invariant Sections, no Front-Cover Texts and no Back-Cover Texts ⭐

---

bestie, that's the whole tea ☕💅 this page is from 23 March 2020, and it's still giving 🌸✨ see you in the next debugging session, muah 💋🎀