Forwarded message 1
- From: Henrik Frystyk Nielsen <frystyk@w3.org>
- Date: 1999年5月20日 15:19:18 -0400
- Subject: Re: LoadToFile demonstrates libwww bug?
- To: Michael Saunders <michael@amtec.com>
- Message-ID: <37446036.E76D7732@w3.org>
Michael Saunders wrote: > I discovered that libwww gets stuck because it somehow gets through to > the socket() call with a NULL pointer passed as the wait time. I also > noticed that maxfds is zero. Is it possible that timers were cleaned > up as a result of the target file name error which causes the socket > to start blocking? Following is the output from the trace of the second > attempt with the invalid base directory (I have substituted the real > directory names with the ones shown above). Most of the interesting > information is in the last five or six lines. > > Does anyone know what is going wrong here (Henrik does this sound > like a bug?) Yes, you are right - I forgot to check the return code of HTLoadToFile so it jumped into the event loop even though a request wasn't started. This is fixed now, see http://dev.w3.org/cgi-bin/cvsweb/libwww/Library/Examples/LoadToFile.c#rev1.6 -- Henrik Frystyk Nielsen, <frystyk@w3.org> World Wide Web Consortium, MIT/LCS NE43-356 545 Technology Square, Cambridge MA 02139, USA