[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
lynx-dev HTDoRead() HTTCP.c possible bug - retry limit set too high?
From: |
jtnews |
Subject: |
lynx-dev HTDoRead() HTTCP.c possible bug - retry limit set too high? |
Date: |
Thu, 06 Jul 2000 21:51:02 -0400 |
I use lynx to dump URL text pages using lynx -dump and
occasionally, lynx hangs in the following section of code...
HTTCP.c:
while (!ready) {
/*
** Protect against an infinite loop.
*/
=> if (tries++ >= 180000) {
HTAlert(gettext("Socket read failed for 180,000 tries."));
I'm using lynx 2.8.4dev4.
I also ran into a similar situation using 2.8.3 also.
With the timeout in select set to 100000 microseconds The call will
only timeout
after 180000 * 100000 / 1000000 = 18000 seconds or 5 hours.
/*
** If we suspend, then it is possible that select will be
** interrupted. Allow for this possibility. - JED
*/
do {
timeout.tv_sec = 0;
timeout.tv_usec = 100000;
FD_ZERO(&readfds);
FD_SET((unsigned)fildes, &readfds);
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden
- lynx-dev HTDoRead() HTTCP.c possible bug - retry limit set too high?,
jtnews <=
- Re: lynx-dev HTDoRead() HTTCP.c possible bug - retry limit set too high?, Vlad Harchev, 2000/07/07
- Re: lynx-dev HTDoRead() HTTCP.c possible bug - retry limit set too high?, Klaus Weide, 2000/07/07
- Re: lynx-dev HTDoRead() HTTCP.c possible bug - retry limit set too high?, Vlad Harchev, 2000/07/07
- Re: lynx-dev HTDoRead() HTTCP.c possible bug - retry limit set too high?, Klaus Weide, 2000/07/07
- Re: lynx-dev HTDoRead() HTTCP.c possible bug - retry limit set too high?, Vlad Harchev, 2000/07/08
- Re: lynx-dev HTDoRead() HTTCP.c possible bug - retry limit set too high?, Klaus Weide, 2000/07/09
- Re: lynx-dev HTDoRead() HTTCP.c possible bug - retry limit set too high?, Vlad Harchev, 2000/07/10