"John P . Looney" wrote:
> I changed the loglevel, and restarted apache. It was moaning about some
> process not finishing. I was having problems with a httpd process using
> ~99% CPU time earlier, for hours. Killed it, and it didn't occur again. It
> could have there...hmmm.
>
> The machine has 333Mhz K6, and 160MB RAM, and I'm the only one using midgard.
Ample resources.
> Smeg. Just got a segmentation fault message in the logs. I'll run it with
> httpd -X and see can I repeat it, and get a core dump...
What Midgard version are you on? I mean, when did you download it? Some
packages have seen subreleases since b7. Check out the download page.
> I've been trying to run httpd -X and it's not dumping core, even though
> ulimit -c is set to 100MB. And, I can't run it in gdb, because it gets
> sigpipes all over the place. Is there a cunning way of debugging apache ?
"Smeg" and "cunning". British?
I usually do debugging on a separate apache executable which I build
with
mod_midgard and midgard-php linked in statically. I've not seen
coredumps
from a 'regular' apache yet -- I wonder whether it's a feature of
apache.
If you're on a recent apache (post 1.3.6 I believe) you can tell gdb to
ignore the sigpipe signal. Apache gets a sigpipe when the client
terminates the connection prematurely (like by pressing 'stop' while the
page loads) but no longer uses that signal (explicitly ignores it).
I wouldn't expect sigpipes 'all over the place' though. They should only
occur as result from a client-terminated connection AFAIK.
Emile
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
