Re: Unresolved error 0xC0000409 on Windows Server

From: Matthew Gerber <gerber(dot)matthew(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, Merlin Moncure <mmoncure(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Unresolved error 0xC0000409 on Windows Server
Date: 2012-11-12 02:45:54
Message-ID: CAOcpbfrRvr54XnzCbOb3Hrb7wF1rT-aL8N=jfYkc1QZgS6ufwQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Nov 11, 2012 at 8:27 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Noah Misch <noah(at)leadboat(dot)com> writes:
> > So, I can reproduce the lower threshold, but the exception type does not
> agree
> > with the one Matthew observed.
>
> I finally got around to looking at the link you provided about error
> 0xC0000409, and realized that I'd been completely confusing it with
> stack overflow --- but actually, it's a report that something scribbled
> past the end of a finite-size local-variable array. So I now think that
> Matthew's stumbled across two completely independent bugs, and we've
> fixed only one of them. The 0xC0000409 error is something else, and
> possibly a lot worse since it could conceivably be a security issue.
>
> It still seems likely that the actual location of the bug is either
> in PostGIS or in the GIST index code, but without the ability to
> reproduce the failure it's awfully hard to find it. Matthew, could
> you try a bit harder to find a self-contained test case that produces
> that error?
>
> regards, tom lane
>

Sure, it might take me a while to find time but I'll keep it on my list.

Matt

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2012-11-12 03:55:49 Re: Doc patch "only relevant" -> "relevant only"
Previous Message Tom Lane 2012-11-12 01:27:15 Re: Unresolved error 0xC0000409 on Windows Server