From: | Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Heath Lord <heath(dot)lord(at)crunchydata(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: REL_13_STABLE Windows 10 Regression Failures |
Date: | 2020-11-11 09:27:15 |
Message-ID: | CAC+AXB0+1=GEqxZt2LhkeR767aGLD2nu5hEA3QMsmWuw4xeLRg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Nov 11, 2020 at 2:32 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> High,
>
> On 2020-11-09 12:18:34 -0500, Tom Lane wrote:
> > Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> > > Hmm, line 202 is the ereport in this test:
> >
> > > if (!IsA(expr, ColumnRef))
> > > ereport(ERROR,
> > > (errcode(ERRCODE_FEATURE_NOT_SUPPORTED),
> > > errmsg("only simple column references are allowed
> in CREATE STATISTICS")));
> >
> > > Not sure why that gives rise to the upper parts of the stack there.
> >
> > Yeah, it seems like the error-recovery longjmp has suddenly broken;
> > but why here? There's nothing unusual about this specific error case.
>
> Perhaps PG_exception_stack got corrupted somehow? An oversized write to
> a neighboring var?
>
> Not sure if that works on mingw, but building with address sanitizer /
> asan might be informative.
>
This looks like a known issue in MinGW64 builds [1], which is derived from
an also known issue in MSVC's handling of setjmp/longjmp [2].
[1] https://sourceforge.net/p/mingw-w64/bugs/406/
[2] https://docs.microsoft.com/en-us/cpp/cpp/using-setjmp-longjmp
Regards,
Juan José Santamaría Flecha
From | Date | Subject | |
---|---|---|---|
Next Message | Kurt Roeckx | 2020-11-11 09:49:18 | Re: BUG #16707: Memory leak |
Previous Message | Andres Freund | 2020-11-11 01:38:08 | Re: BUG #16707: Memory leak |