pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Regina Obe <lr@pcorp.us>
Cc: 'Juan José Santamaría Flecha' <juanjo.santamaria@gmail.com>
Cc: 'PostgreSQL mailing lists' <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head
Date: Fri, 12 Mar 2021 16:47:59 -0500
Message-ID: <2555584.1615585679@sss.pgh.pa.us> (raw)
In-Reply-To: <000201d71781$a0c5da20$e2518e60$@pcorp.us>
References: <16920-2332590daf58407c@postgresql.org>
	<2291040.1615474929@sss.pgh.pa.us>
	<000501d71691$c616a200$5243e600$@pcorp.us>
	<2294904.1615480631@sss.pgh.pa.us>
	<000401d716a0$1ed0fc70$5c72f550$@pcorp.us>
	<2309396.1615485820@sss.pgh.pa.us>
	<CAC+AXB3_u1LQ7+WPLu2jZN5Y0kdVx10kkSi7XARN4oLSq9-vrQ@mail.gmail.com>
	<004301d71772$f3336020$d99a2060$@pcorp.us>
	<2551612.1615579995@sss.pgh.pa.us>
	<000201d71781$a0c5da20$e2518e60$@pcorp.us>

"Regina Obe" <lr@pcorp.us> writes:
> The backtrace of that looks like this:

> #0  0x00007ffe76032136 in ntdll!RtlRaiseStatus ()
>    from C:\WINDOWS\SYSTEM32\ntdll.dll
> #1  0x00007ffe75f60bb3 in ntdll!RtlUnwindEx ()
>    from C:\WINDOWS\SYSTEM32\ntdll.dll
> #2  0x00007ffe74002eed in msvcrt!_setjmpex ()
>    from C:\WINDOWS\System32\msvcrt.dll
> #3  0x00000000008da31a in pg_re_throw () at elog.c:1776
> #4  0x00000000008da19d in errfinish (filename=<optimized out>,
>     filename@entry=0xa291a0 <BinarySignature+24> "copyto.c",
>     lineno=lineno@entry=490,
>     funcname=funcname@entry=0xa29980 <__func__.112127> "BeginCopyTo")
>     at elog.c:589
...

> I'll go thru the other tests to see which ones are crashes and provide a bt
> of those too if you find it useful.
> Anyway at a glance they all seem to be on tests designed to throw an error.

It does look suspiciously like something is broken in our attempt to
longjmp back to the server's outermost loop.  We had a similar report
last fall, also about MinGW:

https://www.postgresql.org/message-id/flat/CA%2BBEBhvHhM-Bn628pf-LsjqRh3Ang7qCSBG0Ga%2B7KwhGqrNUPw%4...

and I don't think we ever figured out what was happening there either.

(FWIW, walleye's owners report that the failure goes away when they
change their compiler options to more debug-friendly settings.  Hmm.)

			regards, tom lane





view thread (33+ messages)  latest in thread

Message-ID: <2555584.1615585679@sss.pgh.pa.us>
Permalink:  ../2555584.1615585679@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2555584.1615585679@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, lr@pcorp.us, juanjo.santamaria@gmail.com, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #16920: Can't compile PostGIS with MingW64 against PostgreSQL 14 head
  In-Reply-To: <2555584.1615585679@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox