Re: seawasp failing, maybe in glibc allocator
Andres Freund <andres@anarazel.de>
From: Andres Freund <andres@anarazel.de>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Thomas Munro <thomas.munro@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2021-05-11T17:13:42Z
Lists: pgsql-hackers
On 2021-05-11 10:22:02 +0200, Fabien COELHO wrote: > > > On 2021-05-11 12:16:44 +1200, Thomas Munro wrote: > > > OK we got the SIGABRT this time, but still no backtrace. If the > > > kernel's core_pattern is "core", gdb is installed, then considering > > > that the buildfarm core_file_glob is "core*" and the script version is > > > recent (REL_12), then I'm out of ideas. ulimit -c XXX shouldn't be > > > needed because the perl script does that with rlimit. > > > > Unless perhaps the hard rlimit for -C is set? ulimit -c -H should show > > that. > > Possibly I have just added "ulimit -c unlimited" in the script, we should > see the effect on next round. If it's the hard limit that won't help, because the hard limit can only be increased by a privileged process.
Commits
-
Prepare for forthcoming LLVM 13 API change.
- 6ada4fd06666 11.13 landed
- 47d22649e6a2 12.8 landed
- d9c05a9ec493 13.4 landed
- 9b4e4cfe66ff 14.0 landed