From: David E. <da...@2g...> - 2003-06-03 18:17:30
|
On Tue, 2003-06-03 at 19:51, Patrick McFarland wrote: > Hi, Ive just started using valgrind, and Im getting odd errors reported by > valgrind: > > "Conditional jump or move depends on uninitialised value(s)" from code that > uses a if/else checking if foo == NULL or not Then "foo" hasn't been initialized where it came from. Check the backtrace. > "Invalid write of size 1" when freeing. Maybe freeing the same memory twice? > "Use of uninitialised value of size x" when using GLfloat foo = bar; (or any > typedefed type for that matter) Probably "bar" hasn't been initialized where it came from. Check the backtrace. > How do I fix these, or do I just ignore them? At least don't ignore them if it's your own code :-) -- -\- David Eriksson -/- www.2GooD.nu "I personally refuse to use inferior tools because of ideology." - Linus Torvalds |