Date: Thu, 18 Jun 1998 00:35:33 -0400 From: Arthur Krewat <krewat@erols.com> To: hackers@FreeBSD.ORG Subject: stuck in a recv/read call? Message-ID: <35889915.15FB7483@erols.com>
next in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35889915.15FB7483>