From: Bill Reynolds (bill@yossarian.ucsd.edu)
Date: 05/31/93


From: bill@yossarian.ucsd.edu (Bill Reynolds)
Subject: Re: BUG in libc?
Date: 31 May 1993 18:07:40

In article <BILL.93May28223755@yossarian.ucsd.edu> bill@yossarian.ucsd.edu (Bill Reynolds) writes:

   I've been tripped up by what looks like a bug in the C-library printf
   function. I'm running linux 0.99pl6 with gcc version 2.3.3. I've got
   both libc.so.4.1 and libc.so.4.3 in /lib.

   The bug manifests itself when I run some code that does some numerical
   integration using fortran libraries from netlib translated with f2c,
   (VERSION 22 July 1992 22:54:52) and linked with the f2c library. The
   code is somewhat large, so I'll wait to send it if anyone is
   interested. Basically, if I put a printf statement in the program,
   variables that have nothing to do with the printf get corrupted.

The bug, as it turns out, was a coding error on my part (blush). Libc
works fine, and I apologize for any aspersions that might have been
cast in it's direction.