Re: Cores almost on demand in patcompile()

[Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>]

On 20 October 2016 at 12:18, Peter Stephenson <p.stephenson@xxxxxxxxxxx> wrote:
> Hmm... well, what I've posted fixes the pointers at line 650 of
> pattern.c
>
>                 for (; pscan; pscan = next) {
>                     next = PATNEXT(pscan);
>
> where they would have been wrong before, so if you're *still* seeing
> problems after the change, you've found something else.

Valgrind points at patadd(NULL, 0, nmeta, 0). Wonder why not to its
interior? But to all logic, problem should be inside patadd() because
nothing else near dereferences a pointer. So there might be two
problems. Debugger didn't report inaccessible memory when I did
step-over on the patadd(), maybe memory is accessible but invalid from
other reason recognized by Valgrind.

Best regards,
Sebastian Gniazdowski