Stas Bekman wrote:
May be we just drop safemalloc, and use the plain old malloc, or now that we are more educated with apache internals the right solution seems to be to create a sub-pool and use it to allocate memory. Let me try to work on that first.

OK, Steve and/or Markus, please try with the current cvs, I've now replaced perl's safemalloc with a subpool, that should get rid of the issue.

It does, thanks.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to