Am Donnerstag, 11. Dezember 2003 07:08 schrieb Dave Airlie: > I'm trying to valgrind my application and in the process DRI :-), > > However I can't get over the Mesa MMX checks, is there any env variable I > can set so Mesa doesn't do all the stuff that requires SIGFPE and I can > force it to use a certain type of instruction set? > > I've been just setting ALWAYS_INDIRECT for now but that doesn't find any > issues in my DRI driver (not that I think there are any but it never hurts > to look)...
Ah, this one is much better: http://valgrind.kde.org/faq.html ----------------------------------------------------------------- Q11. I really need to use the NVidia libGL.so in my app. Help! A11. NVidia also noticed this it seems, and the "latest" drivers (version 4349, apparently) 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. Set __GL_FORCE_GENERIC_CPU=1 and Valgrind should work. This has been confirmed by various people. Thanks NVidia! ----------------------------------------------------------------- -- Dieter Nützel @home: <Dieter.Nuetzel () hamburg ! de> ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id78&alloc_id371&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
