Re: seawasp failing, maybe in glibc allocator - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: seawasp failing, maybe in glibc allocator
Date
Msg-id alpine.DEB.2.22.394.2105150825160.1937283@pseudo
Whole thread Raw
In response to Re: seawasp failing, maybe in glibc allocator  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: seawasp failing, maybe in glibc allocator
List pgsql-hackers
Hello Andres,

It finally failed with a core on 8f72bba, in llvm_shutdown, AFAIKS in a 
free while doing malloc-related housekeeping.

My guess is that there is an actual memory corruption somewhere. It is 
unobvious whether it is in bleeding-edge llvm or bleeding-edge postgres 
though.

The issue is non-deterministically triggered in contrib checks, either in 
int or ltree, but not elsewhere. This suggests issues specific to these 
modules, or triggered by these modules. Hmmm…

I've just launched a run with valgrind enabled.

-- 
Fabien.

pgsql-hackers by date:

Previous
From: "Joel Jacobson"
Date:
Subject: Re: use AV worker items infrastructure for GIN pending list's cleanup
Next
From: Jaime Casanova
Date:
Subject: Re: use AV worker items infrastructure for GIN pending list's cleanup