Received: (qmail 45891 invoked by uid 501); 13 Dec 2000 20:21:51 -0000
Message-Id: <20001213202151.45890.qmail@locus.apache.org>
Date: 13 Dec 2000 20:21:51 -0000
From: Nick Caruso <ncaruso@gamesville.com>
Reply-To: ncaruso@gamesville.com
To: submit@bugz.apache.org
Subject: coding error (?) in unix/poll.c
X-Send-Pr-Version: 3.110

>Number:         6977
>Category:       general
>Synopsis:       coding error (?) in unix/poll.c
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed Dec 13 12:30:00 PST 2000
>Closed-Date:    Tue Feb 06 15:10:06 PST 2001
>Last-Modified:  Tue Feb 06 15:10:06 PST 2001
>Originator:     ncaruso@gamesville.com
>Release:        2.0 alpha 9
>Organization:
>Environment:
uname -a                                                                                                                                                               ~/apache2.0(2)
IRIX64 gamey 6.5 07151432 IP27 mips
>Description:
In several places, it looks like there was a failure to modify cut-and-pasted code,
viz.,

apr_status_t apr_remove_poll_socket(apr_pollfd_t *aprset, apr_socket_t *sock)
{
    FD_CLR(sock->socketdes, aprset->read);
    FD_CLR(sock->socketdes, aprset->read);
    FD_CLR(sock->socketdes, aprset->write);
    return APR_SUCCESS;
}

Shouldn't one of those "read" lines be "except"?  There are several occurrences
of this type of error in this file.
>How-To-Repeat:

>Fix:
see full description
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open-closed
State-Changed-By: abagchi
State-Changed-When: Tue Feb  6 15:10:04 PST 2001
State-Changed-Why:
This has been fixed in the CVS repository, and will be available
in the next version of Apache 2.0.

Thank you for the bug report, and for using Apache.
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@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!     ]