Re: BUG #14490: psql and createdb crash with SIGSEGV

On Wed, Jan 11, 2017 at 5:29 AM, <mr(at)marcelruff(dot)info> wrote:
> Bug reference: 14490
> Logged by: Marcel Ruff
> Email address: mr(at)marcelruff(dot)info
> PostgreSQL version: 9.6.1
> Operating system: Debian GNU/Linux 8 (jessie) 3.18.44 x86_64
> Description:
>
> psql --version
> psql (PostgreSQL) 9.6.1
>
> strace pqsl
> ...
> connect(3, {sa_family=AF_LOCAL, sun_path="/tmp/.s.PGSQL.5432"}, 110) = 0
> getsockopt(3, SOL_SOCKET, SO_ERROR, [0], [4]) = 0
> getsockname(3, {sa_family=AF_LOCAL, NULL}, [2]) = 0
> poll([{fd=3, events=POLLOUT|POLLERR}], 1, 4294967295) = 1 ([{fd=3,
> revents=POLLOUT}])
> sendto(3, "\0\0\0R\0\3\0\0user\0watchee\0database\0wa"..., 82, MSG_NOSIGNAL,
> NULL, 0) = 82
> poll([{fd=3, events=POLLIN|POLLERR}], 1, 4294967295) = 1 ([{fd=3,
> revents=POLLIN}])
> recvfrom(3, "R\0\0\0\10\0\0\0\0E\0\0\0\\SFATAL\0VFATAL\0C3D0"..., 16384, 0,
> NULL, NULL) = 102
> --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
> +++ killed by SIGSEGV +++
>
> createdb xxxx
> crashes with SIGSEGV as well

This is strange. No buildfarm machines complain about a similar
behavior... Nor do my dev environments say something.
--
Michael