Re: Debugging memory allocation

[prev] [thread] [next] [Date index for 2005/05/10]

I have a lot of code in a lot of places, and something
like 2-3 hits per second. It is a relatively busy
website. I cannot afford doing what was just
suggested, I would prefer some indirect perl
invocation at the appropriate place. LogHandler seems
like such a place.


i

--- David Nicol <davidnicol@xxxxx.xxx> wrote:

> how about declaring something like 
> 
> sub LogMemoryUsage(){
>    open PIDLOG, ">>pidlog";
>    flock PIDLOG, LOCK_EX;
>    print PIDLOG, "$$ $ENV{SCRIPT_NAME} ",`ps -p $$
> -os`
>    close PIDLOG;
> };
> 
> and then calling LogMemoryUsage() at the beginning
> (and end) of
> every routine that you suspect might have the leak? 
> Examining the
> resulting log would provide clues.
> 
> On 5/10/05, Igor Chudov <ichudov@xxxxx.xxx> wrote:
> > --- Sam Tregar <sam@xxxxxx.xxx> wrote:
> > 
> > > On Mon, 9 May 2005, Igor Chudov wrote:
> > >
> > > > I would like to at least have a log that lists
> > > pid,
> > > > page requested, parameters, starting memory
> and
> > > memory
> > > > after the request was processed. O rsome other
> > > ideas
> > > > like that. Any thoughts?
> 
> 
> -- 
> David L Nicol
> Ask not, "who are you?", but rather, "are you
> allowed?"
> This was always the crucial question anyway.
> (from Marc Stiegler's SecurityPictureBook:
>
http://www.skyhunter.com/marcs/SecurityPictureBook.ppt)
> 


- Igor



		
__________________________________ 
Do you Yahoo!? 
Make Yahoo! your home page 
http://www.yahoo.com/r/hs