From owner-freebsd-hackers Wed Jan 18 12:21:26 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id MAA16997 for hackers-outgoing; Wed, 18 Jan 1995 12:21:26 -0800 Received: from snoopy.mv.com (snoopy.mv.com [199.125.64.182]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id MAA16985 for ; Wed, 18 Jan 1995 12:21:22 -0800 Received: (from pw@localhost) by snoopy.mv.com (8.6.9/8.6.6) id PAA00921; Wed, 18 Jan 1995 15:20:20 -0500 Date: Wed, 18 Jan 1995 15:20:20 -0500 From: "Paul F. Werkowski" Message-Id: <199501182020.PAA00921@snoopy.mv.com> To: dfr@render.com CC: freebsd-hackers@freefall.cdrom.com In-reply-to: (message from Doug Rabson on Wed, 18 Jan 1995 11:06:59 +0000 (GMT)) Subject: Re: old vfprintf bug back again in 2.x Sender: hackers-owner@FreeBSD.org Precedence: bulk >>>>> "Doug" == Doug Rabson writes: Doug> On Sun, 15 Jan 1995, Paul F. Werkowski wrote: >> >> >> A bug that was lurking in lib/libc/stdio/vfprintf.c prior to >> FreeBSD 1.1 is now again hiding in the 2.0 and -current >> source. The bug is demonstrated by this code: >> previous fixes. At least the modified version passes the GCL >> test. Perhaps some official bug fixer can look at this and >> commit to current /usr/src/lib/libc/stdio/? >> >> Paul >> >> [patch deleted] Doug> I looked into this and I believe that this patch does the Doug> same job: Doug> It certainly helps GCL anyway. Unless you have any Doug> objections, I will commit this smaller patch as it seems to Doug> be a bit less intrusive. I have no objections or any claims to the patch I posted. It was the result of diffs with 1.1. Let the best fix go forward! Paul