Page 1 of 3 123 LastLast
Results 1 to 10 of 26

Thread: Valgrind Finds Thousands Of Potential Issues With Mesa

Hybrid View

  1. #1
    Join Date
    Jan 2007
    Posts
    15,178

    Default Valgrind Finds Thousands Of Potential Issues With Mesa

    Phoronix: Valgrind Finds Thousands Of Potential Issues With Mesa

    An open-source developer has spotted thousands of potential memory problems with Mesa when using Valgrind...

    http://www.phoronix.com/vr.php?view=MTQzNjk

  2. #2
    Join Date
    Aug 2012
    Posts
    502

    Default

    "David Airlie has been the only Mesa contributor to respond to the Mesa Valgrind posting yet and he suggests some of the errors may be due to kernel ioctls not known by Valgrind. "We access a lot of kernel data via ioctls that valgrind doesn't understand. I'm not saying that is definitely the case but it was in a lot of places."

    Wow, just wow.

    Instead 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

  3. #3
    Join Date
    Nov 2008
    Location
    Old Europe
    Posts
    932

    Default

    Quote Originally Posted by dh04000 View Post
    "David Airlie has been the only Mesa contributor to respond to the Mesa Valgrind posting yet and he suggests some of the errors may be due to kernel ioctls not known by Valgrind. "We access a lot of kernel data via ioctls that valgrind doesn't understand. I'm not saying that is definitely the case but it was in a lot of places."

    Wow, just wow.

    Instead 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
    You are seriously lacking reading skills, dude.
    Or you're just a f**king troll.

  4. #4
    Join Date
    Mar 2013
    Posts
    11

    Default

    Quote Originally Posted by dh04000 View Post
    Wow, just wow.

    Instead 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
    No, he didn't. He simply said that valgrind might be detecting code it doesn't reconize properly as bugs. Nothing else.

    He never even mentioned the other guy's code. I don't get how you reached the conclusion that he lacks humility unless you're trolling.

  5. #5
    Join Date
    Oct 2007
    Posts
    1,289

    Default

    Quote Originally Posted by dh04000 View Post
    Wow, just wow.
    Big Fonts! Melodrama!

  6. #6
    Join Date
    Aug 2012
    Posts
    502

    Default

    Quote Originally Posted by DanL View Post
    Big Fonts! Melodrama!
    What are we yelling about! Loud Noises!

  7. #7
    Join Date
    Feb 2013
    Posts
    359

    Default

    opensource drivers are trash, more at 11.

  8. #8
    Join Date
    Aug 2011
    Location
    Hillsboro, Oregon
    Posts
    136

    Default

    Quote Originally Posted by peppercats View Post
    opensource drivers are trash, more at 11.
    Not really. Back in the day, I was working on an OpenGL based MMO, and used a Radeon card at the time. I ran the game under Valgrind using the closed source Catalyst drivers, and it hit Valgrind's 10,000,000 error limit before I even got to the account log in screen, which made it really hard to debug my program. It's not a Mesa-specific problem.

    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.

  9. #9
    Join Date
    Nov 2012
    Posts
    621

    Default

    Quote Originally Posted by peppercats View Post
    opensource drivers are trash, more at 11.
    They're best thing that could ever happen in the computer world (just after GPL Linux). It seems you forgot about non graphic drivers, otherwise you wouldn't be writing such trash.

  10. #10
    Join Date
    Jan 2011
    Posts
    208

    Default

    Quote Originally Posted by peppercats View Post
    opensource drivers are trash, more at 11.
    Drivers are trash.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •