From: Brian P. <br...@tu...> - 2003-11-07 17:48:31
|
On Linux, you can set the MALLOC_CHECK env var to do some rudimentary checking (man malloc). Electric Fence is another simple, but useful tool. I haven't upgraded to RH9 yet so I have no first-hand experience with this issue. When NVIDIA's libGL causes me grief with valgrind I switch to Mesa. -Brian Dale Beermann wrote: > This was from a while ago, but I thought some people might be interested > in this information. > > With RH9 and Nvidia drivers the deal with the /usr/lib/tls GL drivers > causes problems with valgrind too. Using the __GL_FORCE_GENERIC_CPU thing > doesn't work. You might get an error like: > > valgrind: vg_ldt.c:167 (vgPlain_do_useseg): Assertion `(seg_selector & 7) > == 7' failed. > > If you prevent the tls libraries from being loaded, you can at least run > valgrind, but not that successfully. I get lots of errors from the OpenGL > library, and a lot more are suppressed. I found some information about > the problem on the valgrind email list, but it doesn't seem that it's been > resolved. It would be nice to have something to use. Does anyone use any > other applications for finding memory errors in linux that might work? > > Dale Beermann > University of Virginia > bee...@cs... > > On Fri, 22 Aug 2003, Brian Paul wrote: > > >>David Thompson wrote: >> >>>>>... >>>>>I've used valgrind for a few things I've been doing, but I've never been >>>>>able to get it to work when you're linking to the OpenGL library. I >>>>>remember reading that this is a problem with the NVidia library, do you >>>>>have a similar problem with Mesa? >>>> >>>>Yeah, with NVIDIA's libGL it gets stopped early. Using Mesa instead >>>>works. >>> >>> >>>Is this different than the issue solved by >>> setenv __GL_FORCE_GENERIC_CPU 1 >>>where unsupported SSE or 3DNOW instructions are run? It seems like I've >>>run valgrind at least once or twice with nVidia's GL with good results. >> >>That's a new one for me. I wasn't aware of that env var. >> >>-Brian >> >> > > > |