On 12/05/10 20:34 , PawełGóralski wrote: > I've tried to run osgviewer debug version with valgrind and memcheck tool, > but there is > a problem, because viewer cannot open display when running with valgrind. > Anyone knows > about any workaround? > > I'm attaching the log.
Odd, I've just run the same valgrind version on the release binary without problems. It came back pretty clean: ==19968== LEAK SUMMARY: ==19968== definitely lost: 64 bytes in 2 blocks ==19968== indirectly lost: 0 bytes in 0 blocks ==19968== possibly lost: 320 bytes in 1 blocks ==19968== still reachable: 27,354 bytes in 378 blocks ==19968== suppressed: 0 bytes in 0 blocks There are quite a few (52 of 58) of these that might be worth looking at: ==19968== at 0x4A05E77: malloc (vg_replace_malloc.c:195) ==19968== by 0x3E4745898B: create (lcGeneric.c:70) ==19968== by 0x3E4745AD23: _XlcCreateLC (lcPubWrap.c:78) ==19968== by 0x3E47478C5F: _XlcDefaultLoader (lcDefConv.c:766) ==19968== by 0x3E47461A62: _XOpenLC (lcWrap.c:296) ==19968== by 0x3E47461B57: _XlcCurrentLC (lcWrap.c:357) ==19968== by 0x3E474977F4: _XkbGetCharset (XKBCvt.c:333) ==19968== by 0x3E47495014: XkbTranslateKeySym (XKBBind.c:591) ==19968== by 0x3E47495703: XLookupString (XKBBind.c:808) ==19968== by 0x63E3160: osgViewer::GraphicsWindowX11::adaptKey(XKeyEvent&, int&) (in /export/local.fc10.64bit/lib64/libosgViewer.so.2.9.8) Could it be your GL driver? What are you using? (Sorry if I missed that from an earlier mail.) Cheers, /ulrich _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
