Re: seawasp failing, maybe in glibc allocator

From: Andres Freund <andres(at)anarazel(dot)de>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: seawasp failing, maybe in glibc allocator
Date: 2021-05-11 01:08:48
Message-ID: 20210511010848.3jp6dvhfrecwivec@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pengchengliu 2021-05-11 01:26:23 RE: Parallel scan with SubTransGetTopmostTransaction assert coredump
Previous Message Andres Freund 2021-05-11 00:55:20 Zeroing partial pages in walreceiver