PDA

View Full Version : memory leak with GL, GLU libraries



glsmiles
10-31-2008, 02:00 PM
I am getting a memory leak report from valgrind when I include the libraries GL and GLU for linking with g++.
My code doesn't have to use the libraries for the leak to occur.
I am wondering if this leak report is simply a benign annoyance or is there something I am missing.

valgrind report:

==6443== Using valgrind-3.2.3-Debian, a dynamic binary instrumentation framework.
==6443== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al.
==6443== For more details, rerun with: -v
==6443==
==6443==
==6443== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 11 from 1)
==6443== malloc/free: in use at exit: 56 bytes in 1 blocks.
==6443== malloc/free: 64 allocs, 63 frees, 474,289 bytes allocated.
==6443== For counts of detected errors, rerun with: -v
==6443== searching for pointers to 1 not-freed blocks.
==6443== checked 2,022,160 bytes.
==6443==
==6443== LEAK SUMMARY:
==6443== definitely lost: 0 bytes in 0 blocks.
==6443== possibly lost: 0 bytes in 0 blocks.
==6443== still reachable: 56 bytes in 1 blocks.
==6443== suppressed: 0 bytes in 0 blocks.
==6443== Reachable blocks (those to which a pointer was found) are not shown.
==6443== To see them, rerun with: --leak-check=full --show-reachable=yes

my system:
ubuntu release 7.10
kernel Linux 2.6.22-15-generic
MESA 7.0.1
GNOME 2.20.1
AMD Athlon 64 X2 dual core
nvidia GeForce 7 series

thank you

glsmiles