This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: recv(..., MSG_PEEK) (was Re: fetchmail 5.9.8 and maildrop 1.3.7)


On Mon, Mar 04, 2002 at 10:56:50AM -0500, Jason Tishler wrote:
> Corinna,
> 
> On Sun, Mar 03, 2002 at 03:58:18PM +0000, Rui Carmo wrote:
> > On Sat, Mar 02, 2002 at 09:47:19PM -0500, Jason Tishler wrote:
> > > > I was under the impression that recv() bugs had been twiddled in
> > > > 1.3.10... Or did the changes in recv() not address MSG_PEEK?
> > > 
> > > Hmm, I will look into this.  It would be great if my patch just became
> > > obsolete.
> > 
> > The release notes (post by Cristopher:
> > http://sources.redhat.com/ml/cygwin/2002-02/msg01350.html) mention recv()
> > explicitly:
> > 
> > > - Implement socket read/write using recv/send. (corinna)
> > 
> > Bit vague, though, so I don't know if Corinna tackled the MSG_PEEK
> > issue.
> 
> Could you comment as to whether or not the above changes would have any
> positive affects on the following?
> 
>     http://sources.redhat.com/ml/cygwin/2001-08/msg00628.html

No.  The above change is sort of a code cleanup.  I don't know how
we could workaround that Winsock problem in Cygwin.  It doesn't know
from where you got the `n' parameter and it's perfectly legal for
a read() call to return a number of bytes < n.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin@cygwin.com
Red Hat, Inc.

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]