Re: seawasp failing, maybe in glibc allocator
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-05-21T21:58:38Z
Lists: pgsql-hackers
Hi, On 2021-05-21 21:37:22 +1200, Thomas Munro wrote: > I installed Clang/LLVM version > "1:13~++20210520071732+02f2d739e074-1~exp1~20210520052519.57" from > https://apt.llvm.org/ on a Debian buster box, and I saw that > contrib/ltree's test fail about half the time with a range of weird > and wonderful outputs (wrong answers) similar to seawasp, but it never > crashed. I ran it under valgrind and I managed to get: Interesting. I tried this with a slightly older LLVM checkout (6f4f0afaa8ae), from 2021-04-20, contrib/ltree tests run without an issue, even if I force everything to be jitted+inlined+optimized. The git hash in the package version indicates the commit is from 2021-05-20. Upgrading my local checkout to see whether I can repro the problem. If I can we at least have a not too large bisection window... Greetings, Andres Freund
Commits
-
Prepare for forthcoming LLVM 13 API change.
- 6ada4fd06666 11.13 landed
- 47d22649e6a2 12.8 landed
- d9c05a9ec493 13.4 landed
- 9b4e4cfe66ff 14.0 landed