On 11/4/16 12:35 AM, Eduardo A. Bustamante López wrote:
> I ran the configure script with the following arguments:
>
> hp% ./configure CC=gcc-6 CFLAGS='-Wall -g -ggdb -O0 -fsanitize=address'
> LDFLAGS=-fsanitize=address --without-bash-malloc
>
> Which enables the LeakSanitizer
> (https://github.com/google/sanitizers/wiki/AddressSanitizerLeakSanitizer).
>
> It detected the following memory leak:
It `leaks' in the child process. The parent eventually stores that memory
in the jobs list and frees it when the job is deleted. The leaks don't
accumulate; they are individual to each child process. It's never been a
big deal in practice.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://cnswww.cns.cwru.edu/~chet/
