Path: utzoo!attcan!uunet!lll-winken!ames!ncar!unmvax!tut.cis.ohio-state.edu!bloom-beacon!THINK.COM!rlk
From: rlk@THINK.COM (Robert L. Krawitz)
Newsgroups: comp.windows.x
Subject: twm vs. gcc
Message-ID: <8904051349.AA12595@regin.think.com>
Date: 5 Apr 89 13:49:00 GMT
References: <8904050608.AA14064@Sun.COM>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 14

I recall reading somewhere (the gcc documentation?) that the scanf
family of functions is broken; it does try to write its format string.
It doesn't "need" to do this, probably; most likely, it does so anyway
because someone found that they could get some more speed out of it
that way.  The other case that's likely to come up is
mktemp("stringXXXXXX").

The patch (I don't have the source code, but it's easy enough to
figure out) is to declare a variable somewhere that's initialized to
the format string of sscanf, and pass it to sscanf.

ames >>>>>>>>>  |	Robert Krawitz <rlk@think.com>	245 First St.
bloom-beacon >  |think!rlk	(postmaster)		Cambridge, MA  02142
harvard >>>>>>  .	Thinking Machines Corp.		(617)876-1111