Re: seawasp failing, maybe in glibc allocator
| От | Andres Freund |
|---|---|
| Тема | Re: seawasp failing, maybe in glibc allocator |
| Дата | |
| Msg-id | 20210521215838.cs7f4pn3kpxbgeav@alap3.anarazel.de обсуждение исходный текст |
| Ответ на | Re: seawasp failing, maybe in glibc allocator (Thomas Munro <thomas.munro@gmail.com>) |
| Ответы |
Re: seawasp failing, maybe in glibc allocator
Re: seawasp failing, maybe in glibc allocator |
| Список | 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
В списке pgsql-hackers по дате отправления: