Re: seawasp failing, maybe in glibc allocator

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: seawasp failing, maybe in glibc allocator
Date: 2021-05-11 00:16:44
Message-ID: CA+hUKG+Wq_fjD1HFgd4K-6ViCjket4KLz57XLy7BVa5R7OL_jQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 10, 2021 at 11:21 PM Fabien COELHO <coelho(at)cri(dot)ensmp(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2021-05-11 00:35:28 Re: PG 14 release notes, first draft
Previous Message Tom Lane 2021-05-11 00:15:41 Re: Is element access after HASH_REMOVE ever OK?