I have a rather large script I run through mod_perl.... and occasionally, I have
notice some users with "stuck" processes. It seems
like they are in some sort of infinite loop.
The CPU that the child is using is high, and the memory gradually grows until my
server would eventually start to thrash (however, I
built a script to kill the child before this occurs)....
Does anyone know of a way (even if it costs more memory/cpu) that I could load an
ability into modperl and view where in the perl
code a mod_perl process is atually at? Would "Apache::Status" or "B::TerseSize" or
something else make this possible?
I know that "B::TerseSize" will allow me to view the code loaded into memory, but I
havent' found a way to actually analyze a child
to find out what it is CURRENTLY runnning.
