On Mon, May 6, 2013 at 6:30 AM, Rainer Jung rainer.j...@kippdata.de wrote:
Waiting with my vote for Mladen's reply, but so far the test results on
my systems look very good. Note that though Eric reports a problem for
Solaris, I'm testing on Solaris Sparc doing 32 Bit builds and I think
he's
On 29.05.2013 18:23, Eric Covener wrote:
On Mon, May 6, 2013 at 6:30 AM, Rainer Jung rainer.j...@kippdata.de wrote:
Waiting with my vote for Mladen's reply, but so far the test results on
my systems look very good. Note that though Eric reports a problem for
Solaris, I'm testing on Solaris
Hi Ben,
this is my code snippet and if I enable the commented line then I get an
Apache error
AH00052: child pid 24982 exit signal Segmentation fault (11)
The snippet:
static apr_status_t do_client_task(apr_socket_t *sock, const char
*filepath, request_rec *r)
{
apr_status_t rv;
On Thu, 2013-05-30 at 00:06 +0200, Graf László wrote:
bufp = apr_palloc(r-pool, len);
bufp = buf;
What is the point of the above code? First some memory is allocated for
bufp, then it is ignored, as bufp actually becomes a pointer to the buf
array...
As for the
Just a wild guess, but you may be accessing beyond the end of the buffer...
You do: apr_status_t rv = apr_socket_recv(sock, buf, len);
which requests len number of bytes, being placed into buf.
What happens if you get len then try to format it using
apr_psprintf(r-pool, ---%s---, bufp)
Dear all,
In our practice, we found two threads get same address returned by
apr_palloc. It will happen about one hour later after our server starts.
We are using apr 1.4.5, the issue still exists in the latest subversion.
APR_DECLARE(void *) apr_palloc(apr_pool_t *pool, apr_size_t
On Thu, May 30, 2013 at 9:44 AM, TROY.LIU 劉春偉 troy@deltaww.com.cn wrote:
Dear all,
In our practice, we found two threads get same address returned by
apr_palloc. It will happen about one hour later after our server starts.
Please check whether you compile apr with thread support.
