| commit | f15cc2be5c6f2d1a2c669c00c5b88f73cf2ad6ed | |
| author | Ben Kibbey <bjk@luxsci.net> | |
| Sun, 14 Aug 2016 02:50:59 +0000 (13 22:50 -0400) | ||
| committer | Ben Kibbey <bjk@luxsci.net> | |
| Sun, 14 Aug 2016 02:50:59 +0000 (13 22:50 -0400) | ||
| tree | c13a1320c12a049277df879b1c3b4a7e14138fd4 | treesnapshot (tar.gz zip) |
| parent | 936ee01d0da88019a04be28f2dcfe70d60bcb275 | commitdiff |
New custom memory allocators.
This version doesn't require any mutex and is somewhat faster for lots
of allocations. Valgrind now shows a whole lot of "possibly lost"
warnings but they disappear when --enable-mem-debug is passed to
configure. I noticed that when using the old allocators that Valgrind
has trouble detecting some errors that are discoverable with
--enable-mem-debug. So we'll just do --enable-mem-debug to check for
errors.
This was a suggestion by Justus Winter [1].
1. https://lists.gnupg.org/pipermail/gnupg-devel/2016-August/031406.html
This version doesn't require any mutex and is somewhat faster for lots
of allocations. Valgrind now shows a whole lot of "possibly lost"
warnings but they disappear when --enable-mem-debug is passed to
configure. I noticed that when using the old allocators that Valgrind
has trouble detecting some errors that are discoverable with
--enable-mem-debug. So we'll just do --enable-mem-debug to check for
errors.
This was a suggestion by Justus Winter [1].
1. https://lists.gnupg.org/pipermail/gnupg-devel/2016-August/031406.html
| src/mem.c | diffblobblamehistory | |
| src/mem.h | diffblobblamehistory | |
| src/pwmd-dump.c | diffblobblamehistory | |
| src/pwmd.c | diffblobblamehistory |