Re: XShmQueryExtension, valgrind and a "still reachable" block.

2012-03-16 Thread Antonio Ospite
On Fri, 16 Mar 2012 14:50:22 -0400 Adam Jackson wrote: > On 3/16/12 12:19 PM, Antonio Ospite wrote: > > > ==27577== 24 bytes in 1 blocks are still reachable in loss record 1 of 1 > > ==27577==at 0x402894D: malloc (in > > /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) > > ==27577==

Re: XShmQueryExtension, valgrind and a "still reachable" block.

2012-03-16 Thread Adam Jackson
On 3/16/12 12:19 PM, Antonio Ospite wrote: ==27577== 24 bytes in 1 blocks are still reachable in loss record 1 of 1 ==27577==at 0x402894D: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==27577==by 0x4A30AFD: XextCreateExtension (in /usr/lib/x86_64-linux-gnu/libXext.so

XShmQueryExtension, valgrind and a "still reachable" block.

2012-03-16 Thread Antonio Ospite
Hi, with the attached simple program I can always see that calling XShmQueryExtension makes valgrind report a "still reachable" block: $ valgrind --leak-check=full \ --show-reachable=yes ./XShmQueryExtension_test ... ==27577== 24 bytes in 1 blocks are still reachable in loss record 1 of 1 ==27