How to do memory check on a daemon program?

c++ memory-management memory-leaks valgrind memory-leak-detector
Alwin Doss picture Alwin Doss · Feb 14, 2012 · Viewed 8.1k times · Source

I have written a C++ application, that runs forever until terminated manually. It monitors other important applications. As a result my Daemon application should not go down. Keeping that in mind, I want to see if there are any memory leaks in my application. I used valgrind but since this application keeps running forever the valgrind does not exit. if I do a control - C then I don't get complete info from the valgrind logfile.

Is there a tool that can do what Valgrind does?

Answer

Useless picture Useless · Feb 14, 2012

I believe you can connect gdb to a running valgrind process, and instruct it to run a leak check explicitly.

I haven't tried this, just seen it in the docs.

In case of link breakage:

Connecting GDB to a Valgrind gdbserver

$ valgrind --tool=memcheck --vgdb=yes --vgdb-error=0 ./prog

(the error parameter is the number of errors before the gdbserver becomes active: zero means it starts running right away).

Then start gdb on your program and connect to the remote target

$ gdb ./prog
(gdb) target remote | vgdb

and to trigger the check

(gdb) monitor leak_check full reachable any

See your docs or the linked ones for full details.

Related questions

How does a reference-counting smart pointer's reference counting work?

In other words, how does the implementation keeps track of the count? Is there a map-like object maintained which is accessible by all the shared_ptr instances whose key is the pointer's address and value is the number of references? …

Read More
Freeing memory twice

In C and C++, Freeing a NULL pointer will result in nothing done. Still, I see people saying that memory corruption can occur if you "free memory twice". Is this true? What is going on under the hood when you …

Read More
In what cases do I use malloc and/or new?

I see in C++ there are multiple ways to allocate and free data and I understand that when you call malloc you should call free and when you use the new operator you should pair with delete and it is …

Read More