Date: Wed, 04 Jun 2003 13:18:03 +0200 From: Gary Jennejohn <garyj@jennejohn.org> To: ehr3@ehr3.com Cc: freebsd-ports@freebsd.org Subject: Re: EDEADLK and recvfrom(2), connect(2), and/or socket(2) Message-ID: <200306041118.h54BI3Ov003586@peedub.jennejohn.org> In-Reply-To: Message from "Ernest H. Rice, III" <ehr3@ehr3.com> of "Tue, 03 Jun 2003 15:04:41 EDT." <200306031504.41614.ehr3@ehr3.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Ernest H. Rice, III" writes: > 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! > IMO the first step would be to grep over /usr/src to determine where EDEADLK is returned (not that many places) and then figure out which of those places your code may be invoking. It's probable that 5.x and 4.x are different. --- Gary Jennejohn / garyj@jennejohn.org gj@freebsd.org gj@denx.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200306041118.h54BI3Ov003586>