From: Julian S. <js...@ac...> - 2003-04-11 07:33:21
|
The non-working of valgrind with nvidia drivers might go away when we finally get around to implementing SSE/SSE2 instructions, which we hope will happen soon. However, NVidia also noticed this it seems, and the "latest" drivers (don't ask me what version, I don't use them) come with this text DISABLING CPU SPECIFIC FEATURES Setting the environment variable __GL_FORCE_GENERIC_CPU to a non-zero value will inhibit the use of CPU specific features such as MMX, SSE, or 3DNOW!. Use of this option may result in performance loss. This option may be useful in conjunction with software such as the Valgrind memory debugger. __GL_FORCE_GENERIC_CPU=1 valgrind ... whatever ... apparently does work. Great stuff. Ah yes, version 4349 according to Sylvain's just-arrived message. J On Friday 11 April 2003 5:36 am, Paul Cheyrou-lagreze wrote: > I use both on the same linux system : > > 1. install latest nvidia driver > 2. download Mesa source from mesa3d.org > 3. compile and install Mesa from sources (make install should install it in > /usr/local/lib/) (if you're coding some opengl try configure --enable-warn > --enable-trace, you'll get some VERY useful information) > > Then, when you want to use Mesa, > just launch a shell command > export LD_LIBRARY_PATH=/usr/local/lib > and launch apps. (Valgrind included) > > When you want to use hardware opengl, > export LD_LIBRARY_PATH= > > Then you can test code with both, and debug with Mesa, wich is easier. > > -Paul > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger > for complex code. Debugging C/C++ programs can leave you feeling lost and > disoriented. TotalView can help you find your way. Available on major UNIX > and Linux platforms. Try it free. www.etnus.com > _______________________________________________ > Valgrind-users mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-users |