On Thu, 16 Aug 2001, Alan Burlison wrote:
Stas Bekman wrote:
No need for an apology :-) The trick is to build perl using the
Solaris malloc (-Dusemymalloc as a flag to Configure), then apache,
mod_perl and perl all agree on who manages memory.
Might I suggest that this golden
On Thu, 16 Aug 2001, Stas Bekman wrote:
Currently what I've is:
* How do I build on Solaris with DSO?
= Build perl and mod_perl using the system malloc
that should be any platform where perl defaults to using its own malloc,
that is, if:
% perl -V:usemymalloc
reports:
usemymalloc='y'
On Thu, Aug 16, 2001 at 09:35:43AM -0700, Doug MacEachern wrote:
that should be any platform where perl defaults to using its own malloc,
that is, if:
% perl -V:usemymalloc
reports:
usemymalloc='y'
which is fine if:
% perl -V:bincompat5005
reports:
bincompat5005='undef';
but the
On Thu, 16 Aug 2001, Alex Povolotsky wrote:
This is perl, v5.6.1 built for sun4-solaris
# perl -V:usemymalloc
usemymalloc='n';
that's fine.
Seems like I'm suffering from dying children problem... My main apache
dies sometimes, bringing neraly everything (well, except
server-status)
