Skip to content
  • Valgrind 3.27 RC1 is out

    Uncategorized valgrind
    1
    0 Votes
    1 Posts
    0 Views
    P
    Valgrind 3.27 RC1 is outAn RC1 tarball for 3.27.0 is now available athttps://sourceware.org/pub/valgrind/valgrind-3.27.0.RC1.tar.bz2(md5sum = bd95111c1a9f81f136c5e4e2c62b493e)(sha1sum = 0eefb3a7d86a3bd0154480db3d2173bb8bd6d7c1)https://sourceware.org/pub/valgrind/valgrind-3.27.0.RC1.tar.bz2.ascPublic keys can be found at https://www.klomp.org/mark/gnupg-pub.txtPlease give it a try in configurations that are important for you andreport any problems you have, either on the developer/user mailing list, or(preferably) via our bug tracker athttps://bugs.kde.org/enter_bug.cgi?product=valgrindAn RC2 should be available Fri Apr 17The final 3.27.0 release is scheduled for Mon Apr 20.#valgrind
  • This codebase uses SQLite3.

    Uncategorized sqlite3 valgrind
    1
    0 Votes
    1 Posts
    0 Views
    charette@mstdn.caC
    This codebase uses SQLite3. Valgrind reports a huge amount of lost memory, one entry for every DB query.But every sqlite3_prepare_v2() is correctly followed by sqlite3_finalize(). I love Valgrind, but sometimes the output is difficult to interpret. #SQLite3 #Valgrind