delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2002/11/05/00:07:23

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Tue, 5 Nov 2002 00:09:17 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Anyone interested in checking out dgram socket problem (Conrad you still here?)
Message-ID: <20021105050917.GA19118@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
Mime-Version: 1.0
User-Agent: Mutt/1.5.1i

There is a thread in cygwin at cygwin entitled:

"1.3.13-2 & 1.3.14-1 problem on read() from dgram socket"

Is anyone willing to debug the problem and, if it is a cygwin problem,
provide a fix?

cgf

http://cygwin.com/ml/cygwin/2002-10/msg01974.html

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019