1de51eb727
The current model causes an issue when trying to spot memory leaks, because malloc(0) or realloc(0) do not count as allocations since we only account for the application-usable size. This is the problem that made issue #1406 not to appear as a leak. What we're doing now is to account for one extra pointer (the one that memory allocators usually place before the returned area), so that a malloc(0) will properly account for 4 or 8 bytes. We don't need something exact, we just need something non-zero so that a realloc(X) followed by a realloc(0) without a free() gives a small non-zero result. It was verified that the results are stable including in the presence of lots of malloc/realloc/free as happens when stressing Lua. It would make sense to backport this to 2.4 as it helps in bug reports.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)