Andrew Dunstan wrote:
> Andrew Dunstan wrote:
>> Magnus Hagander wrote:
>>> Andrew Dunstan wrote:
>>>> I've installed drmingw to handle exceptions instead, so we'll see if
>>>> that gives us useful info. If not, I'll see what I can do with gdb.
>>> Hadn't heard of drwmingw, I see how that can be useful :-)
>> report from DrMingw is below
> Further data point:
> The suspect patch is quite definitely the source of the problem. I undid
> the configure changes and surrounded the additions to port/win32.h with
> #ifdef WIN32_ONLY_COMPILER ... #endif. Result: the problem disappeared,
> and "make check" completed perfectly.
Per discussion I looked at just reverting that part, but that won't
work. If we do that, the call to SetEnvironmentVariable() will not be
run, which certainly isn't right..
The problem has to be in win32env.c. I originally thought we
accidentally called the putenv function twice in this case, but that
code seems properly #ifdef:ed to MSVC.
I'm not sure I trust the crash point at all - is this compiled with
debug info enabled? It seems like a *very* strange line to crash on...
I can't spot the error right off :-( Can you try to see if it's the
putenv() or the unsetenv() that gets broken? (by making sure just one of
them get replaced)
In response to
pgsql-hackers by date
|Next:||From: Magnus Hagander||Date: 2009-01-28 15:24:33|
|Subject: Re: [COMMITTERS] pgsql: Silence compiler warning on win32.|
|Previous:||From: Simon Riggs||Date: 2009-01-28 15:22:07|
|Subject: Re: 8.4 release planning|