From owner-freebsd-hackers  Thu Apr 24 21:41:14 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA23222
          for hackers-outgoing; Thu, 24 Apr 1997 21:41:14 -0700 (PDT)
Received: from siesta.cs.wustl.edu (nw1@siesta.cs.wustl.edu [128.252.165.3])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA23216
          for <freebsd-hackers@freebsd.org>; Thu, 24 Apr 1997 21:41:12 -0700 (PDT)
Received: from localhost by siesta.cs.wustl.edu (SMI-8.6/ECL-J1.00)
	id XAA12399; Thu, 24 Apr 1997 23:40:57 -0500
Message-Id: <199704250440.XAA12399@siesta.cs.wustl.edu>
To: John Birrell <jb@cimlogic.com.au>
cc: freebsd-hackers@freebsd.org
Subject: Re: Possible broken libc_r 
In-reply-to: Your message of "Fri, 25 Apr 1997 08:23:04 +1000."
             <199704242223.IAA01998@freebsd1.cimlogic.com.au> 
Date: Thu, 24 Apr 1997 23:40:54 -0500
From: Nanbor Wang <nw1@cs.wustl.edu>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > I found a possible bug in libc_r.  Below is a very simple test
> > program.  What I did was I opened a socket in the localhost between
> > client and server program.  When I compiled the program with
> > non-threaded library, everything worked just fine.  However, when I
> > compiled it using libc_r, the recv() system call seemed to be broken.
> > Without any specific manipulation, it acted as if I had turn on the
> > non-blocking flag.  Is this a bug or I did something terribly wrong?
> 
> What version is this? Current or 2.2?
> See what happens if you avoid stdin and stdout.
> 

No luck.  I removed all stdio related stuff but the recv() call on
server side still won't block.  I tried using recvfrom() also.  Still
the same.  Any clue?

nw


> > 
> > TIA.
> > 
> > Nanbor
> [...]
> 
> Regards,
> 
> -- 
> John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org
> CIMlogic Pty Ltd, 119 Cecil Street, South Melbourne Vic 3205, Australia
> Tel +61 3 9690 6900 Fax +61 3 9690 6650 Mob +61 418 353 137