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

From Thomas Munro
Subject Re: seawasp failing, maybe in glibc allocator
Date
Msg-id CA+hUKG+Wq_fjD1HFgd4K-6ViCjket4KLz57XLy7BVa5R7OL_jQ@mail.gmail.com
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
On Mon, May 10, 2021 at 11:21 PM Fabien COELHO <coelho@cri.ensmp.fr> wrote:
> > And of course this time it succeeded :-)
>
> Hmmm. ISTM that failures are on and off every few attempts.

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.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Is element access after HASH_REMOVE ever OK?
Next
From: David Rowley
Date:
Subject: Re: PG 14 release notes, first draft