[PATCH 2/3] grep: make PCRE2 aware of custom allocator

From: =?UTF-8?q?Carlo=20Marcelo=20Arenas=20Bel=C3=B3n?= 94da9193a6 (grep: add support for PCRE v2, 2017-06-01) didn't include a way to override the system allocator, and so it is incompatible with custom allocators (e.g. nedmalloc). This problem became obvious when we tried to plug a memory leak

Re: [PATCH 2/3] grep: make PCRE2 aware of custom allocator

On Thu, Aug 8, 2019 at 6:57 AM Johannes Schindelin wrote: > On Tue, 6 Aug 2019, Carlo Marcelo Arenas Belón wrote: > > Suggested-by: Johannes Schindelin > > Actually not so much suggested by me, as your patch still causes > crashes (mine didn't): the "equivalent" version in v4[1], that is still n

Re: [PATCH 2/3] grep: make PCRE2 aware of custom allocator

Hi Carlo, On Tue, 6 Aug 2019, Carlo Marcelo Arenas Belón wrote: > Most of the code stolen from[1] to easy on comparison and including > the deficiency of setting the global context even for patterns that > won't need it. > > Ideally, the call from grep_init could be moved to a place where it > co

[PATCH 2/3] grep: make PCRE2 aware of custom allocator

Most of the code stolen from[1] to easy on comparison and including the deficiency of setting the global context even for patterns that won't need it. Ideally, the call from grep_init could be moved to a place where it could be set without needing a lock and at least with this approach we have a p