Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!bloom-beacon!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: FFlush problem in LSC Debugger
Message-ID: <2063@husc6.harvard.edu>
Date: 16 Jun 89 13:04:33 GMT
References: <113@orchid.waterloo.edu>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec/THINK Technologies, Bedford, MA
Lines: 31

In article <113@orchid.waterloo.edu> jlee4@orchid.waterloo.edu () writes:
>
>Hi people.  I just got my 4 Megs of RAM, so I started hacking
>away on nethack. When suddenly, the LSC Debugger started barfing
>(i.e. Bus Error) when fflush(stdout) was invoked.  This was the

	This isa known problem in stdio, and will be fixed in the
next release of the libraries. If you want to fix it yourself now,
check that the stream getting flushed is not a standard stream.

	The woraround is to not call fflush for stdin, stdout, or
any other stream that might originate in a window. (use this
approach if you don't want to muck with the libraries.)

		--Rich





~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

 I classify myself as a real developer because my desk is hip-deep in
 assembly-language listings and I spend more than 50% of my time in TMON.

~~~~~~~~~~~~~~~