Re: BUG #15133: make check fails - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #15133: make check fails
Date
Msg-id 20180328151230.kry23xe4d7s77t63@alvherre.pgsql
Whole thread Raw
In response to BUG #15133: make check fails  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15133: make check fails
List pgsql-bugs
PG Bug reporting form wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      15133
> Logged by:          Stefan Krüger
> Email address:      stadtkind2@gmx.de
> PostgreSQL version: 10.3
> Operating system:   Solaris 11.4 Beta
> Description:        

I'm not sure of the support status for Solaris 11.  We don't have any
buildfarm member for that, much less the 11.4 beta.  Maybe this is a
problem in the OS, or the compiler?  I can't see siglongjmp() failing in
this way being a Postgres bug, frankly ...

> Here's the core dump information:
> 
> $ mdb ./src/backend/postgres ./src/test/regress/tmp_check/data/core
> postgres:core> ::status
> debugging core file of postgres (64-bit) from solaris
> file: src/backend/postgres
> initial argv: postgres -D
> /tmp/postgresql-10.3/src/test/regress/./tmp_check/data -F -c listen
> threading model: raw lwps
> status: process terminated by SIGABRT (Abort), pid=7312 uid=12273 code=-1
> postgres:core> $C
> ffffffe0b0839b41 libc.so.1`__lwp_sigqueue+8(6, ffffffffffffffec, ffffffe0b083a3e0, 5, 0, 0)
> ffffffe0b0839bf1 libc.so.1`abort+0xfc(1, 1210, 0, 1000, 1fff248d83b830, 1fff248d83b730)
> ffffffe0b0839cd1 libc.so.1`adistack_clear_stack_impl+0x178(ffffffe0b083a640, ffffffe0b0a362e1, 0, 0,
ffffffe0b08d1f31,1)
 
> ffffffe0b0839d81 libc.so.1`adistack_clear_stack%sun4v-adi+0x70(ffffffe0b0a360e1, 1, ffffffe0b0a360e1, 1, 0,
ffffffe0b083acc0)
> ffffffe0b083a131 libc.so.1`setcontext+0x4c(ffffffe0b083ad80, ffffffe0b083ad78, 1fff248f2a2a40, 1fff248d828000,
ffffffe0b083a9e0,1)
 
> ffffffe0b083a4c1 libc.so.1`siglongjmp+0x144(ffffffe0b0a369c8, 1, 1, ffffffe0b0a362e1, ffffffe0b0a368e0,
ffffffe0b083ad80)
> ffffffe0b083a861 postgres`pg_re_throw+0x50(0, 1fff248eeaa958, 30000034b26db478, 2f000000, 2f, 8080808080808080)
> ffffffe0b083a921 postgres`errfinish+0x260(0, 0, 0, 1fff248dfa8960, 0, 20000034b4a85be0)
> ffffffe0b083aa21 check_stack_depth+0x114(20000034b4a86320, 20000034b4a86520, 20000034b4a865a0, 0, 800000, 0)
> ffffffe0b083aaf1 transformExprRecurse+0x44(20000034b4a865a0, 20000034b4a86320, 0, 0, 0, 0)
> ffffffe0b083ac41 transformExpr+0x50(20000034b4a865a0, 20000034b4a86320, d, 110, 101010100000000, 1010101)
> ffffffe0b083ad31 transformTargetEntry+0x98(20000034b4a865a0, 20000034b4a86320, 0, d, 0, 0)

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-bugs by date:

Previous
From: Rémi Aubel
Date:
Subject: Re: BUG: Unable to bind a null value typed as a UUID in a PreparedStatement
Next
From: Tom Lane
Date:
Subject: Re: BUG #15133: make check fails