Re: Debugging Out of Memory Errors

[prev] [thread] [next] [Date index for 2005/01/27]

Ken Simpson wrote:
> A module I wrote is somehow running out of memory and I need to find
> out why and where the problem is occurring.  Searching through the
> archives, I discovered that in mod_perl 1.0 you could set the
> Apache::Debug level to 4:
> 
>  use Apache::Debug level => 4;
>  (see the mod_perl book: http://modperlbook.org/html/ch22_03.html)
> 
> Doing this would cause a special memory allocator to be used so that
> Carp could print out a stack trace in the event of an out of memory
> error.
> 
> Is there an equivalent in mod_perl 2?

I guess it wasn't on the todo list, so we have missed it while porting mp1 
core modules to mp2. It looks like it's trivial to port it to mp2. Feel 
free to port that and post a patch to include it in the mp2 core, or 
someone will do that later.

p.s. if there some other forgotten core bits that weren't ported please 
don't hesitate to mention those here.

Thanks.



        -- 
        __________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@xxxxxx.xxx http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com