RE: os-windows/5171: Apache server goes into an infinite loop aft er CGI error

["Patterson, Jim" <Ji...@Cognos.COM>]

Yes, when I was debugging the loop I checked that errno was indeed EINTR.

I don't think the Win32 C RTL actually uses EINTR. It was likely set by
Apache itself
e.g. here in main\buff.c (sendwithtimeout):
			WSASetLastError(EINTR);	/* Simulate an alarm() */

There are several places where errno is set to WSAGetLastError, so this call
could
have the indirect effect of setting errno to EINTR.

At least, that is my conjecture. I didn't actually observe EINTR being set
on; it was
already set by the time I broke into the process to debug it.

Scanning through the code, there are quite a few loops that check EINTR.
Maybe the loop
you are still observing is happening somewhere else besides the one stuck
loop that I encountered.

-----Original Message-----
From: stoddard@apache.org [mailto:stoddard@apache.org]
Sent: Wednesday, December 01, 1999 12:23 PM
To: apache-bugdb@apache.org; jim.patterson@cognos.com;
stoddard@apache.org
Subject: Re: os-windows/5171: Apache server goes into an infinite loop
after CGI error


[In order for any reply to be added to the PR database, you need]
[to include <ap...@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]


Synopsis: Apache server goes into an infinite loop after CGI error

State-Changed-From-To: open-feedback
State-Changed-By: stoddard
State-Changed-When: Wed Dec  1 09:22:46 PST 1999
State-Changed-Why:
Jim, thanks for the info. Did you verify that errno 
was indeed set to EINTR? I have a fix for this in the 
current development tree, but one tester is still reporting the infinite
loop problem. 

If you are interested, you can download the latest development code for
Apache 1.3 from http://dev.apache.org/from-cvs and give it a spin. 
I'd be interested to know if you still see the same problem.