| commit | 642135f3b2d6d6eb800153c76c4718239733c0e6 | [log] [tgz] |
|---|---|---|
| author | Behdad Esfahbod <behdad@behdad.org> | Tue Nov 03 11:26:34 2015 -0800 |
| committer | Behdad Esfahbod <behdad@behdad.org> | Tue Nov 03 11:26:34 2015 -0800 |
| tree | 209a0c114fafbd97ec06e437be05452343a0a247 | |
| parent | ed2024ef93ac3af214082016e5aa8c14db9d7515 [diff] |
[util] In --debug mode, duplicate font data This has the effect that the font data will end up in a memory section malloc()ed exactly to its size. This gives us better valgrind detection of out-of-bounds access. Previously, the font data was placed in a mmap()ed section or GString-allocated area, which didn't have proper protections at the end when running under valgrind.