From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: seawasp failing, maybe in glibc allocator |
Date: | 2021-05-16 10:58:49 |
Message-ID: | CA+hUKG+_uK8mGfXzsq8RsX2Jhh6Wo_gOyNZM3ZqYJJwYtTD=SA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, May 15, 2021 at 6:41 PM Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> wrote:
> 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…
Hmm, yeah. A couple of different ways that ltreetest fails without crashing:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=seawasp&dt=2021-05-13%2001%3A17%3A15
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=seawasp&dt=2021-05-12%2017%3A17%3A15
Otherwise it's mostly free() blowing up, and one case of an assertion
failure in llvm::StringMapImpl::RemoveKey, I guess before free() is
reached:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=seawasp&dt=2021-05-14%2009%3A17%3A15
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2021-05-16 12:11:33 | Typo in README.barrier |
Previous Message | Noah Misch | 2021-05-16 04:29:33 | Re: Windows default locale vs initdb |