Comment 21 for bug 929384

@colin: it doesn't crash in valgrind either, but shows 1 unfreed block in libGL.

$ valgrind --leak-check=full --show-reachable=yes /usr/lib/nux/unity_support_test
==22940== Memcheck, a memory error detector
==22940== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==22940== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==22940== Command: /usr/lib/nux/unity_support_test
==22940==
--22940-- WARNING: Serious error when reading debug info
--22940-- When reading debug info from /usr/lib/nvidia-current/libGL.so.290.10:
--22940-- Can't make sense of .got.plt section mapping
--22940-- WARNING: Serious error when reading debug info
--22940-- When reading debug info from /usr/lib/nvidia-current/libnvidia-glcore.so.290.10:
--22940-- Can't make sense of .got section mapping
==22940==
==22940== HEAP SUMMARY:
==22940== in use at exit: 32 bytes in 1 blocks
==22940== total heap usage: 42 allocs, 41 frees, 122,009 bytes allocated
==22940==
==22940== 32 bytes in 1 blocks are still reachable in loss record 1 of 1
==22940== at 0x402BE68: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==22940== by 0x42072DE: ??? (in /usr/lib/nvidia-current/libGL.so.290.10)
==22940== by 0xBED338E9: ???
==22940== by 0x454B5F44: ???
==22940==
==22940== LEAK SUMMARY:
==22940== definitely lost: 0 bytes in 0 blocks
==22940== indirectly lost: 0 bytes in 0 blocks
==22940== possibly lost: 0 bytes in 0 blocks
==22940== still reachable: 32 bytes in 1 blocks
==22940== suppressed: 0 bytes in 0 blocks
==22940==
==22940== For counts of detected and suppressed errors, rerun with: -v
==22940== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)