From owner-freebsd-hackers Wed Jun 17 21:35:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14706 for freebsd-hackers-outgoing; Wed, 17 Jun 1998 21:35:45 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp1.erols.com (smtp1.erols.com [207.172.3.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14695 for ; Wed, 17 Jun 1998 21:35:41 -0700 (PDT) (envelope-from krewat@erols.com) Received: from kilonet.net (krewat.erols.com [209.122.47.140]) by smtp1.erols.com (8.8.8/8.8.5) with SMTP id AAA07751 for ; Thu, 18 Jun 1998 00:35:40 -0400 (EDT) Received: from kilowatt(really [199.89.231.227]) by kilonet.net via sendmail with smtp id for ; Thu, 18 Jun 1998 00:35:33 -0400 (EDT) (Smail-3.2 1996-Jul-4 #3 built 1998-May-10) Message-ID: <35889915.15FB7483@erols.com> Date: Thu, 18 Jun 1998 00:35:33 -0400 From: Arthur Krewat X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 2.2.6-STABLE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: stuck in a recv/read call? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a multi-threaded TCP application that runs great under Solaris 2.6. It uses POSIX multi-threads and works as predicted. I have it running under FreeBSD, and after a few problems, got it working. However, after three (yes three and ALWAYS three!) it'll get stuck in a recv or read (tried both!), sucking up CPU time. With or without other FD's open, etc. etc. When it hits the third socket, it always dies with this. I know this can be my own code that's killing me and it's something with the cross-platform thing, but WHAT can cause a read/recv to spin it's wheels? I am compiling with -lc_r and -D_THREAD_SAFE ... am I missing something here? I like FreeBSD - been running it for years now... this is the first time I've come up against something that wasn't a standard thing. -- Art Krewat krewat*NoSpAm*@erols.com Remove obvious anti-spam string from email address when replying. SPAM (unsolicitied email) FORBIDDEN. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message