Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uwvax!astroatc!prairie!dan
From: dan@prairie.UUCP (Daniel M. Frank)
Newsgroups: net.unix,net.micro.pc
Subject: Re: Bug in Microport stdio
Message-ID: <272@prairie.UUCP>
Date: Fri, 31-Oct-86 17:21:07 EST
Article-I.D.: prairie.272
Posted: Fri Oct 31 17:21:07 1986
Date-Received: Sun, 2-Nov-86 23:55:23 EST
References: <123@gaia.UUCP>
Reply-To: dan@prairie.UUCP (Daniel M. Frank)
Organization: Prairie Computing, Madison, Wisconsin
Lines: 22
Xref: mnetor net.unix:6095 net.micro.pc:7455

In article <123@gaia.UUCP> jon@gaia.UUCP (Jonathan Corbet) writes:
>I have found what appears to be an obnoxious bug in the standard I/O
>library for Microport unix.  Rather than let other folks out there track
>it down themselves, I thought I would pass it on:

   A couple clarifications:  this bug appears in most SVR2 releases.  This
should be no suprise, since Microport is an AT&T licensee.  It appears
in printf, fprintf, vprintf, and vfprintf.  Microport is aware of the 
problem, and it is being repaired.

   The best, and least cost workaround, is to do the following after
any call to these routines (assume your file pointer is called fp):

   fp->flag |= _IOWRT ;

You don't have to close the file, or anything.  Do this only if the
file is opened for "r+" mode.

-- 
    Dan Frank
    uucp: ... uwvax!prairie!dan
    arpa: dan%caseus@spool.wisc.edu