|
From: Dimitri Papadopoulos-O. <pap...@sh...> - 2003-11-19 07:48:08
|
Hi,
> I got this report from a valgrind user. He found this bug in later versions
> of valgrind (>> 20031012). Is this information enough to solve the problem
> or may I ask the user for further information?
Just a few remarks:
> $ valgrind ./kmagui
> [...]
> ==3546== at 0x49ECDBB8: (within /usr/lib/libGL.so.1.0.4496)
> [...]
This is the latest NVidia driver. It has been reported that NVidia
drivers require __GL_FORCE_GENERIC_CPU be set for lack of MMX, SSE, or
3DNOW! support in Valgrind (see FAQ). I don't know if that's still the
case with curent version of Valgrind. Try setting this variable.
Maybe it would be worth trying on a machine without NVidia drivers, just
to test whether this is related to NVidia drivers.
> ==3546== Syscall param modify_ldt(ptr)(func=1 or 0x11) contains
uninitialised or unaddressable byte(s)
I don't understand this error message. I'd like to suggest rewriting it
using plain English, so that casual users can understand what's
happenning. I suspect many power users on this mailing list do
understand this message, but other programers just don't understand what
this means (that's the case at my place):
modify_ldt(ptr)(func=1 or 0x11)
> ==3546== Conditional jump or move depends on uninitialised value(s)
Again, some programers just wonder what this error message means. I
guess that it has to do with code looking like
if ( variable ) {
[...]
where "variable" isn't initialised. Again maybe this error message could
be rewritten using simple words, if at all possible.
Finally it's a pity there's no searchable archive for this mailing list.
--
Dimitri
|