- 01 May, 2017 2 commits
-
-
Luca Boccassi authored
Solution: pass -g so that valgrind/asan can print useful backtraces
-
Luca Boccassi authored
Solution: don't, libzmq's CI tests are not responsible for testing libsodium stable releases. Save some time in the CI.
-
- 27 Dec, 2016 2 commits
-
-
Luca Boccassi authored
Solution: rework the bash test to avoid build failures as intended and make it an easier one-liner
-
Luca Boccassi authored
Solution: use packages on Ubuntu and brews on OSX. The packages and the brews are always kept up to date, so it's no use to rebuild the libsodium stable branch manually everytime.
-
- 19 Mar, 2016 2 commits
-
-
Luca Boccassi authored
Solution: update builds/valgrind/valgrind.supp to ignore glibc's __libc_freeres calls. This code runs after the program exits, and tries to de-allocate memory allocated internally by glibc, so it has nothing to do with libzmq code. This suppression is added by default in newer versions of Valgrind, not yet available on older distributions.
-
Luca Boccassi authored
Solution: run Valgrind only on the default Linux build to avoid increasing the runtime.
-
- 26 Mar, 2012 1 commit
-
-
Pieter Hintjens authored
-