On Fri, 16 Mar 2012 14:50:22 -0400 Adam Jackson <a...@redhat.com> 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== by 0x4A30AFD: XextCreateExtension (in > > /usr/lib/x86_64-linux-gnu/libXext.so.6.4.0) > > ==27577== by 0x4A305A4: ??? (in > > /usr/lib/x86_64-linux-gnu/libXext.so.6.4.0) > > ==27577== by 0x4A3091C: ??? (in > > /usr/lib/x86_64-linux-gnu/libXext.so.6.4.0) > > ==27577== by 0x4A30D31: XextAddDisplay (in > > /usr/lib/x86_64-linux-gnu/libXext.so.6.4.0) > > ==27577== by 0x4A2B5B8: XShmQueryExtension (in > > /usr/lib/x86_64-linux-gnu/libXext.so.6.4.0) > > ==27577== by 0x4006D5: main (in > > /home/ao2/WIP/am7xxx-play/tests/XShmQueryExtension_test) > > ... > > > > Maybe this is intended and not an actual bug, but I wanted to ask > > here for confirmation. > > So, is this message OK or a symptom of an actual bug? > > It's a bug if you expect your program to survive disconnecting from the > X server, but most people don't expect that to be a thing. > Right, still inexperienced users could waste a couple of minutes figuring out the noise in the valgrind output. > That said, I'm unable to reproduce this on Fedora 16 (libX11 1.4.3 and > libXext 1.2.0). What OS are you seeing this on, and what versions of > those packages does it have? Debian Unstable: libx11-6 1.4.99.1 and libxext6 1.3.0 Thanks, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
pgpVMr18y0wIk.pgp
Description: PGP signature
_______________________________________________ xorg@lists.x.org: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: arch...@mail-archive.com
