Re: seawasp failing, maybe in glibc allocator

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: seawasp failing, maybe in glibc allocator
Date: 2021-05-11 08:22:02
Message-ID: alpine.DEB.2.22.394.2105111017010.763532@pseudo
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.

Possibly I have just added "ulimit -c unlimited" in the script, we should
see the effect on next round.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2021-05-11 08:25:58 Re: wal stats questions
Previous Message Kyotaro Horiguchi 2021-05-11 08:11:57 Re: Race condition in recovery?