我一直在追逐与-lcairo和-lX11相关联的程序中的内存问题。最后，我决定评论main()中的所有行，并确保valgrind感到满意。令我惊讶的是，它不是：
==7570== Memcheck, a memory error detector
==7570== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==7570== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==7570== Command: ./Test
==7570==
==7570==
==7570== HEAP SUMMARY:
==7570== in use at exit: 10,360 bytes in 5 blocks
==7570== total heap usage: 5 allocs, 0 frees, 10,360 bytes allocated
==7570==
==7570== 2,072 bytes in 1 blocks are still reachable in loss record 1 of 5
==7570== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==7570== by 0x5FCCE9A: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5FCBACE: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5FCD585: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5F7F508: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x4010139: call_init.part.0 (dl-init.c:78)
==7570== by 0x4010222: _dl_init (dl-init.c:36)
==7570== by 0x4001309: ??? (in /lib/x86_64-linux-gnu/ld-2.19.so)
==7570==
==7570== 2,072 bytes in 1 blocks are still reachable in loss record 2 of 5
==7570== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==7570== by 0x5FCCE9A: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5FCA61F: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5FCD5A0: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5F7F508: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x4010139: call_init.part.0 (dl-init.c:78)
==7570== by 0x4010222: _dl_init (dl-init.c:36)
==7570== by 0x4001309: ??? (in /lib/x86_64-linux-gnu/ld-2.19.so)
==7570==
==7570== 2,072 bytes in 1 blocks are still reachable in loss record 3 of 5
==7570== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==7570== by 0x5FCCE9A: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5FE5A8F: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5FBC1A5: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5FCD5AB: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5F7F508: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x4010139: call_init.part.0 (dl-init.c:78)
==7570== by 0x4010222: _dl_init (dl-init.c:36)
==7570== by 0x4001309: ??? (in /lib/x86_64-linux-gnu/ld-2.19.so)
==7570==
==7570== 2,072 bytes in 1 blocks are still reachable in loss record 4 of 5
==7570== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==7570== by 0x5FCCE9A: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x60053CF: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5FCD5AB: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5F7F508: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x4010139: call_init.part.0 (dl-init.c:78)
==7570== by 0x4010222: _dl_init (dl-init.c:36)
==7570== by 0x4001309: ??? (in /lib/x86_64-linux-gnu/ld-2.19.so)
==7570==
==7570== 2,072 bytes in 1 blocks are still reachable in loss record 5 of 5
==7570== at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==7570== by 0x5FCCE9A: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5FCFCBF: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x5F7F508: ??? (in /usr/lib/x86_64-linux-gnu/libpixman-1.so.0.30.2)
==7570== by 0x4010139: call_init.part.0 (dl-init.c:78)
==7570== by 0x4010222: _dl_init (dl-init.c:36)
==7570== by 0x4001309: ??? (in /lib/x86_64-linux-gnu/ld-2.19.so)
==7570==
==7570== LEAK SUMMARY:
==7570== definitely lost: 0 bytes in 0 blocks
==7570== indirectly lost: 0 bytes in 0 blocks
==7570== possibly lost: 0 bytes in 0 blocks
==7570== still reachable: 10,360 bytes in 5 blocks
==7570== suppressed: 0 bytes in 0 blocks
==7570==
==7570== For counts of detected and suppressed errors, rerun with: -v
==7570== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
具有空main()的程序是否可以分配内存并最终得到一些可到达的块？有没有办法摆脱这个奇怪的问题？
答案 0 :(得分：2)
是。这是可能的。
一种方法是在链接的库中可能存在一些静态对象。 @ M.M
已经指出了这一点另一种方法是，如果要链接共享库，没有静态对象，并且此类库中的某些函数使用__attribute__((constructor))。此属性导致这些函数在main（）之前执行（仅适用于gcc），因此您可以看到内存分配。如果在程序中使用这些函数，库主要使用这些函数来声明有关其函数的某些属性。有关这些属性的更多详细信息，请参阅：