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+hUKGKRu0bNbvGoW+27y2edc=HhKqsvzd5O8rj3vgBRqqA9gQ@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 6:59 PM Fabien COELHO <coelho@cri.ensmp.fr> wrote:
> > Is gdb installed, and are core files being dumped by that SIGABRT, and
> > are they using the default name (/proc/sys/kernel/core_pattern = core),
> > which the BF can find with the value it's using, namely 'core_file_glob'
> > => 'core*'?
>
> Nope:
>
>    sh> cat /proc/sys/kernel/core_pattern
>    |/usr/share/apport/apport %p %s %c %d %P %E

If you don't care about Ubuntu "apport" on this system (something for
sending crash/bug reports to developers with a GUI), you could
uninstall it (otherwise it overwrites the core_pattern every time it
restarts, no matter what you write in your sysctl.conf, apparently),
and then sudo sysctl -w kernel.core_pattern=core to undo the setting
immediately (or reboot).  Then hopefully the build farm would succeed
in dumping a backtrace into the log.



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: Remove "FROM" in "DELETE FROM" when using tab-completion
Next
From: Bharath Rupireddy
Date:
Subject: Re: GetSubscriptionRelations declares too many scan keys