Date: Tue, 29 Apr 1997 17:23:59 +0000 (GMT) From: John Birrell <jb@cimlogic.com.au> To: nw1@cs.wustl.edu (Nanbor Wang) Cc: jb@cimlogic.com.au, freebsd-hackers@freebsd.org Subject: Re: Possible broken libc_r Message-ID: <199704291724.RAA01981@freebsd1.cimlogic.com.au> In-Reply-To: <199704250440.XAA12399@siesta.cs.wustl.edu> from Nanbor Wang at "Apr 24, 97 11:40:54 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
Nanbor Wang wrote: > > > 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? Hmmm. I'll try to get rid of the virus that has infected the machine that I run -current on, and take a look stay tuned... > > nw > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704291724.RAA01981>