Re: seawasp failing, maybe in glibc allocator
От | Andres Freund |
---|---|
Тема | Re: seawasp failing, maybe in glibc allocator |
Дата | |
Msg-id | 20210511171342.4fgskmhwglnjbc7i@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: seawasp failing, maybe in glibc allocator (Fabien COELHO <coelho@cri.ensmp.fr>) |
Ответы |
Re: seawasp failing, maybe in glibc allocator
|
Список | 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.
В списке pgsql-hackers по дате отправления: