beatrous+@pitt.edu wrote:
>
> I've looked a little more closely at this. Gcache runs for a while and
> then dies with a segmentation fault. If anyone can tell me how to crash it
> on demand, I'll try to debug it.
The formula I've been given is this (thanks to Matthias Suencks):
procedure (two browser instances needed):
* step 1: load a page (CGI-generated,if that matters) with a picture
(static) in it
with browser 1
* important: now access the page with browser 2
* now wait after the timeout, i.e. 6 minutes
* reload the page with browser 1: the HTML page is re-loaded, but the
image isnt't !!
* gcache is crashed with the following message:
EOF in saferead after 0 bytes
httpsd: gcachecommon.c:54: ReadThing: Assertion `nRead == sizeof
usLength' failed.
connect: Connection refused
httpsd: gcacheclient.c:37: OpenServer: Assertion `0' failed.
final note: when I set the the gcache timeout to 10 seconds or so,
it won't crash.
My comments:
1. The fact it is CGI generated is almost certainly irrelevant, IMO.
2. I've just noticed that the timeout in the config file is completely
ignored (it is hard coded to 15 seconds)! So the timings must be more
important than the config settings. Yes, this will be fixed in 1.17.
3. I haven't tried this, I have no idea if it works at all.
Cheers,
Ben.
--
Ben Laurie |Phone: +44 (181) 735 0686| Apache Group member
Freelance Consultant |Fax: +44 (181) 735 0689|http://www.apache.org
and Technical Director|Email: ben@algroup.co.uk |
A.L. Digital Ltd, |Apache-SSL author http://www.apache-ssl.org/
London, England. |"Apache: TDG" http://www.ora.com/catalog/apache