http://bugs.php.net/15333
I've narrowed down the problem, but can't seem to get anywhere with it.
The state of the server when the problem occurrs:
All serviceable threads have been killed or have timed out.
A request is received prompting the spawning of a new thread.
The new thread then goes
bytes are encountered. I worked around this by writing my own string
copy function.
Billy Rose
[EMAIL PROTECTED]
-Original Message-
From: Joseph Tate [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 09, 2002 1:41 PM
To: Php-Dev List
Subject: [PHP-DEV] zend questions and bug #15333
Forgot to mention, the algorithm in the MS lib is what is faulty. It
overruns the buffer at times.
Billy Rose
[EMAIL PROTECTED]
-Original Message-
From: Joseph Tate [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 09, 2002 1:41 PM
To: Php-Dev List
Subject: [PHP-DEV] zend questions
Subject: [PHP-DEV] zend questions and bug #15333
http://bugs.php.net/15333
I've narrowed down the problem, but can't seem to get
anywhere with it.
The state of the server when the problem occurrs:
All serviceable threads have been killed or have timed out.
A request
]]
Sent: Tuesday, April 09, 2002 2:05 PM
To: Rose, Billy; Php-Dev List
Subject: RE: [PHP-DEV] zend questions and bug #15333
zend_strndup is a php implementation. It does not use the
strndup function
available through MS's library. The problem occurs because a
length of
100 or more
PM
To: 'Joseph Tate'; Rose, Billy; Php-Dev List
Subject: RE: [PHP-DEV] zend questions and bug #15333
In your stack dump, the function call that bombed was memcpy in
the MS lib.
Looking at the source in zend_alloc.c, I find that the lib's
memcpy function
is used. The way I finally tracked
