Steve Hay wrote on 2011-02-07:
Steve Hay wrote on 2011-02-07:
Steve Hay wrote on 2011-02-04:
William A. Rowe Jr. wrote on 2011-02-04:
On 2/4/2011 3:49 PM, Steve Hay wrote:
It looks like the original environ[] was allocated by msvcr100.dll
using something other than a function matching the
On 2/8/2011 8:29 AM, Steve Hay wrote:
+int len = (int)strlen(newarr[arg]) + 1;
+*env = (char*)_malloc_dbg(len * sizeof(char), _CRT_BLOCK, __FILE__,
__LINE__);
+strcpy_s(*env, len, newarr[arg]);
That's just sick ... It's inexcusable to use strcpy when len is already
William A. Rowe Jr. wrote on 2011-02-08:
On 2/8/2011 8:29 AM, Steve Hay wrote:
+int len = (int)strlen(newarr[arg]) + 1; +*env =
(char*)_malloc_dbg(len * sizeof(char), _CRT_BLOCK, __FILE__, __LINE__);
+strcpy_s(*env, len, newarr[arg]);
That's just sick ... It's
On 2/8/2011 4:29 PM, Steve Hay wrote:
William A. Rowe Jr. wrote on 2011-02-08:
On 2/8/2011 8:29 AM, Steve Hay wrote:
+int len = (int)strlen(newarr[arg]) + 1; +*env =
(char*)_malloc_dbg(len * sizeof(char), _CRT_BLOCK, __FILE__, __LINE__);
+strcpy_s(*env, len,
Steve Hay wrote on 2011-02-04:
William A. Rowe Jr. wrote on 2011-02-04:
On 2/4/2011 3:49 PM, Steve Hay wrote:
It looks like the original environ[] was allocated by msvcr100.dll
using something other than a function matching the HeapFree() function
where the crash finally happens. The CRT code
Steve Hay wrote on 2011-02-07:
Steve Hay wrote on 2011-02-04:
William A. Rowe Jr. wrote on 2011-02-04:
On 2/4/2011 3:49 PM, Steve Hay wrote:
It looks like the original environ[] was allocated by msvcr100.dll
using something other than a function matching the HeapFree() function
where the
I have found that VS2010 release mode builds of Apache/mod_perl crash on
Windows Vista, Windows Server 2008 and Windows 7, and I believe that the
problem may be something to do with the environment manipulation done by
Apache (although Apache itself runs fine when not loading mod_perl).
The same
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
On 2/4/2011 4:51 AM, Steve Hay wrote:
The crash comes here (which is exactly where the Apache/mod_perl setup
was crashing):
msvcr100.dll!free(void * pBlock) Line 51 C
msvcr100.dll!__crtsetenv(char * * poption, const int primary)
Line 211 + 0xa bytes C
William A. Rowe Jr. wrote on 2011-02-04:
On 2/4/2011 4:51 AM, Steve Hay wrote:
The crash comes here (which is exactly where the Apache/mod_perl setup
was crashing):
msvcr100.dll!free(void * pBlock) Line 51 C
msvcr100.dll!__crtsetenv(char * * poption, const int primary)
On 2/4/2011 3:49 PM, Steve Hay wrote:
Yes, Apache, Perl and mod_perl were all brand-new builds done one immediately
after another on the same machine, using the same VS2010 installation for
them all.
I presume by Apache you mean httpd as well as apr and apr-util, etc.
Also, note that the
William A. Rowe Jr. wrote on 2011-02-04:
On 2/4/2011 3:49 PM, Steve Hay wrote:
Yes, Apache, Perl and mod_perl were all brand-new builds done one
immediately after another on the same machine, using the same VS2010
installation for them all.
I presume by Apache you mean httpd as well as
12 matches
Mail list logo
