1. 20 Nov, 2012 1 commit
  2. 13 Nov, 2012 1 commit
  3. 21 Sep, 2012 3 commits
  4. 20 Sep, 2012 2 commits
  5. 12 Sep, 2012 1 commit
  6. 06 Sep, 2012 1 commit
  7. 16 Aug, 2012 2 commits
  8. 08 Aug, 2012 1 commit
    • Naoki Kambe's avatar
      [2136] Changes regarding the test config file · e0a964e8
      Naoki Kambe authored
      - moved b10-config_test.db from src/bin/stats/tests to
        src/bin/stats/tests/testdata
      
      - renamed its name to b10-config.db
      
      - changed its format to multiline
      
      These changes are due to the reviewer's comment.
      e0a964e8
  9. 03 Aug, 2012 1 commit
  10. 02 Aug, 2012 3 commits
  11. 25 Jul, 2012 1 commit
  12. 18 Jul, 2012 2 commits
  13. 16 Jul, 2012 1 commit
  14. 12 Jul, 2012 1 commit
  15. 11 Jul, 2012 1 commit
  16. 06 Jul, 2012 3 commits
  17. 04 Jul, 2012 1 commit
  18. 29 Jun, 2012 1 commit
  19. 26 Jun, 2012 1 commit
  20. 18 Jun, 2012 1 commit
  21. 15 Jun, 2012 1 commit
  22. 14 Jun, 2012 1 commit
  23. 13 Jun, 2012 2 commits
    • Mukund Sivaraman's avatar
      [2036] Introduce --enable-valgrind-suppressions configure switch · 3039e3cd
      Mukund Sivaraman authored
      The rationale for this is:
      
      * Developers configure with `--enable-valgrind` and run `make check` to
        see all the error reports (`make check` continues testing even if
        there are Valgrind issues). This encourages us to fix these issues,
        especially if we are modifying those parts of the code as part of
        another bug.
      
      * Builders configure with `--enable-valgrind
        --enable-valgrind-suppressions` and run `make check` with
        suppressions. `make check` doesn't show existing suppressed issues and
        stops building if it finds a new Valgrind issue that is not
        suppressed.
      3039e3cd
    • Mukund Sivaraman's avatar
      [2036] Show even deeper stacks · 61814fef
      Mukund Sivaraman authored
      61814fef
  24. 12 Jun, 2012 7 commits