Originally posted by chrisb
View Post
Announcement
Collapse
No announcement yet.
Valgrind Finds Thousands Of Potential Issues With Mesa
Collapse
X
-
Originally posted by Cyborg16 View PostThis article is seriously confusing.
Valgrind can (and frequently does) report one issue many times, which is probably the main reason the number is so big. I understand no more from it than "valgrind has found some issues".
Secondly, as pointed out, valgrind does report false positives.
Yes, they should probably be checked, but why the hell make a big deal of it like something major is up? Especially when you don't understand what it's about?
I know there's a bit of trolling on these forums but sometimes it seems Michael acts like a troll too...
I remember valgrind having fits with threads before. It would rack up errors every time a thread was merged or destroyed. It's actually one of the reasons I went to virtual timers.
Comment
-
-
Originally posted by Cyborg16 View PostI know there's a bit of trolling on these forums but sometimes it seems Michael acts like a troll too...
Comment
-
Originally posted by peppercats View Postopensource drivers are trash, more at 11.
The problem is that, by default, Valgrind doesn't always understand IOCTLs or GPU memory mappings. You can add annotations to teach Valgrind about these things, which eliminates most of the problem. As someone mentioned, libdrm does this if you build it with --enable-valgrind.
On the classic i965 driver, I ran 'valgrind glxgears' and it reported no errors at all.Free Software Developer .:. Mesa and Xorg
Opinions expressed in these forum posts are my own.
Comment
-
AFAIK it is enabled by default if valgrind is present when running the autogen.sh/configure script for libdrm. The problem is that you need to have the valgrind headers files available when you compile libdrm, so it's probably not activated in distributions that deliver binaries.
Comment
-
Originally posted by dh04000 View PostInstead of saying thank you for finding these problems and calling all available programmers to help the debug, the only poster basically says "there isn't any bugs, your program isn't working right, we're prefect and incapable of generating bugs for we're gods. 100% your fault".
And these people make the drivers? That should scare you a bit. Humility is a good feature in a person, not a bad one
I admit he (and everyone on mesa) should make a correct suppression file for this cases, so the actual leaks can be found without lots and lots of noise.
Comment
Comment