From owner-freebsd-ports@FreeBSD.ORG Tue Jun 3 12:05:06 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0851B37B401 for ; Tue, 3 Jun 2003 12:05:06 -0700 (PDT) Received: from mta1.srv.hcvlny.cv.net (mta1.srv.hcvlny.cv.net [167.206.5.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69D0343FA3 for ; Tue, 3 Jun 2003 12:05:05 -0700 (PDT) (envelope-from ehr3@ehr3.com) Received: from asv6.srv.hcvlny.cv.net (asv6.srv.hcvlny.cv.net [167.206.5.61]) by mta1.srv.hcvlny.cv.net (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0HFX00A6G6CIYZ@mta1.srv.hcvlny.cv.net> for freebsd-ports@freebsd.org; Tue, 03 Jun 2003 15:05:07 -0400 (EDT) Received: from fred.ehr3.net (ool-44c141bc.dyn.optonline.net [68.193.65.188]) h53J54WO006336 for ; Tue, 03 Jun 2003 15:05:05 -0400 (EDT) Date: Tue, 03 Jun 2003 15:04:41 -0400 From: "Ernest H. Rice, III" To: freebsd-ports@freebsd.org Message-id: <200306031504.41614.ehr3@ehr3.com> Organization: ehr3 & Associates, Inc. MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: KMail/1.5 Subject: EDEADLK and recvfrom(2), connect(2), and/or socket(2) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ehr3@ehr3.com List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2003 19:05:06 -0000 I have a network application which has been ported to several Unixes, including SVR4, UW711, AIX, HP-UX, SunOs, Linux, etc. When ported to FreeBSD, it dies periodically with EDEADLK (errno 11). I have attempted to isolate the problem. So far it has eluded me since the application may run for days - even weeks - before failing. The application runs for months under other Unixes, and has never died with EDEADLK (or the old EAGAIN). The program in question opens sockets, connects to services, etc. Much like a ping would. If anyone can shed some light on how to approach debugging this it would be greatly appreciated! Ernie Rice