On Mon, Jun 6, 2022 at 3:06 PM Paul Eggert <eggert@cs.ucla.edu> wrote:
On 6/6/22 12:37, Jim Meyering wrote:
Once you push that (and assuming you have nothing else pending), I'll
prepare another pre-release snapshot.
Thanks, I pushed it into grep master, after fixing the commentary issue
Bruno noted.
I was going to make a snapshot, but figured I should first run the
usual *SAN check:
i.e., configure && make as usual, but then "make clean" followed by
this on a linux system:
san='-fsanitize-address-use-after-scope -fsanitize=address
-static-libasan';
ASAN_OPTIONS=detect_leaks=1,allocator_may_return_null=1 make
CFLAGS='-O0 -ggdb3' AM_CFLAGS="$san" AM_LDFLAGS="$san" check
and it failed nearly every test, all due to leaks.
You can see a few leaks with an even simpler test using valgrind and a
no-ASAN binary:
(this was with the patch attached below, which fixed the first one I found)