Skip to content

Home

Jump to bottom Edit New page
Matthias Vogelgesang edited this page Apr 7, 2014 · 3 revisions

Checking leaks with Valgrind

Memory leaks must be fixed as these could exhaust memory in long-running data acquisitions. For this we could check the uca-grab binary with the following command

G_DEBUG=resident-modules G_SLICE=always-malloc valgrind \
    --show-possibly-lost=no \
    --tool=memcheck \
    --leak-check=full \
    --log-file="valgrind.log" \
    uca-grab -n 5 $PLUGIN

Check the valgrind.log file for suspicious memory accesses and leaks. If everything looks alright, turn --show-possibly-lost off and check again. Most false positives will come from GLib and GObject though.

Add a custom footer
Add a custom sidebar
Clone this wiki locally