Skip site navigation (1) Skip section navigation (2)

Re: mingw check hung

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: mingw check hung
Date: 2009-01-31 00:13:40
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

Hiroshi Inoue wrote:
> Eventually does the crash come from the call SetEnvironemntVariable
> (.., NULL) on mingw-XP(or older?)?
> I'm also interested in this issue and want to know the cause.

The debugger shows that we actually fail on a popen() call in intdb. 
However, if we replace the calls to SetEnvironmentVariable("foo",NULL) 
with calls to SetEnvironmentVariable("foo","") then there is no failure. 
My theory is that on XP somehow the former is corrupting the environment 
such that when popen() tries to copy the environment for the new child 
process, it barfs.



In response to


pgsql-hackers by date

Next:From: KaiGai KoheiDate: 2009-01-31 00:20:05
Subject: Re: How to get SE-PostgreSQL acceptable
Previous:From: Hiroshi InoueDate: 2009-01-31 00:00:20
Subject: Re: mingw check hung

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group