So I figured out how to get the perl debugger working with mod_perl,
thanks to
Practical mod_perl. I still don't know how to track down the scalars
being leaked.
Could they be being caused from something like the following?
sub example {
return 1;
}
example;
Because the the void context of the returned value? Maybe I'm
confused...
On the advise of someone on another list I stripped my code down to
just the handler
and I still get restart errors on my OS X box, which is the only server
of the two I have
root access on.
Another oddity, on the OSX box I only get the errors on apachectl
restart, not
stop or graceful.
Any help would be much appreciated
Boysenberry
boysenberrys.com | habitatlife.com | selfgnosis.com
On Aug 17, 2005, at 2:46 PM, Boysenberry Payne wrote:
The last set of errors are happening on my OSX box.
I get a different set of errors on our Linux server when it restarts:
[Sun Feb 13 01:00:00 2000] null: Attempt to free unreferenced scalar.
...<snip>
I get a whole mess of those, then I get:
Scalars leaked: 234
I'm not sure how to go about fixing these error on either server
Boysenberry
boysenberrys.com | habitatlife.com | selfgnosis.com
On Aug 17, 2005, at 2:05 PM, Boysenberry Payne wrote:
When I restart apache I get the following errors on child processes:
child process 424 did not exit, sending another SIGHUP
One for each child process. After the above I get:
SIGHUP received. Attempting to restart
I'm using mod_perl 1.26 and apache 1.3.33 (only happens with my
mod_perl scripts running)
I thought at first it was DBI connections not getting closed
properly, they seem to be fine though.
I'm not exactly sure how to go about tracking down what's preventing
the original SIGHUP.
Any ideas?
Boysenberry
boysenberrys.com | habitatlife.com | selfgnosis.com
