Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of covener@gmail.com designates
 74.125.82.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=RE8k/Gj6ToedJAazramMQVT/Q/XLld8lhuESgUh9oVUM2Crho3bjE82tSjim55Z3eZ
         yUyM30AVm7uUBri6KHIL/HDmZ6MAW/TuCir7pEWELjAo9fIataCExwrfCU1NTskX0l++
         Oj4LYePw6Ihw+CWOHqq370dLt+Amq+TUGUpyo=
MIME-Version: 1.0
In-Reply-To: <1B32FF956ABF414C9BCE5E487A1497E708E7C17D@ukmail02.planit.group>
References: <1B32FF956ABF414C9BCE5E487A1497E708E7C17D@ukmail02.planit.group>
Date: Fri, 4 Feb 2011 06:17:05 -0500
Message-ID: <AANLkTimf0FxqSF+eoqOD21UQmvYevZvWZfFnYc1u-6Kr@mail.gmail.com>
Subject: Re: VS2010 release builds of Apache/mod_perl crash on Vista/2008/Win7
From: Eric Covener <covener@gmail.com>
To: dev@httpd.apache.org
Content-Type: text/plain; charset=ISO-8859-1

> I'm using Apache 2.2.17, mod_perl 2.0.4 and Perl 5.12.2 (patched as per
> 5.13.9 to allow building with VS2010). Apache/mod_perl crashes during
> start-up, downstream from ap_run_open_logs():

Two anecdotes in this neighborhood that might feed into your experimenting:

Once upon a time I had to use module built with an up-level windows
toolchain, which cared about native envvars set by the core of Apache.
 I found that the camel-case environment variable functions in windows
were "safer" for both sides to use, e.g. SetEnironmentVariable*
instead of putenv, the same ones used by APR already.

I also maintain a module that started crashing or  "several" windows
users, many years after it had been in use, out of hundreds/thousands
apparently due to putenv of a basic ascii string, but worked without
issue when it called SetEnvironmentVariable* via apr's env functions.