A quick-and-dirty but surprisingly effective way to debug memory leaks is to let the leak grow until it consumes most of a program's memory, and then attach gdb and just x random pieces of memory. Since the leaked data is using up most of memory, you'll usually hit it pretty quickly, and can try to interpret what it must have come from.
No matter what you call it, SecDevOps, DevSecOps, or DevOpsSec, it’s important to have a DevSecOps pipeline with highly valuable security during integration, deployment, and delivery.
Authored Comments
A quick-and-dirty but surprisingly effective way to debug memory leaks is to let the leak grow until it consumes most of a program's memory, and then attach gdb and just x random pieces of memory. Since the leaked data is using up most of memory, you'll usually hit it pretty quickly, and can try to interpret what it must have come from.
No matter what you call it, SecDevOps, DevSecOps, or DevOpsSec, it’s important to have a DevSecOps pipeline with highly valuable security during integration, deployment, and delivery.