From owner-freebsd-bugs@FreeBSD.ORG  Mon Dec 17 07:18:57 2007
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7C45916A41B;
	Mon, 17 Dec 2007 07:18:57 +0000 (UTC) (envelope-from das@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 6036D13C467;
	Mon, 17 Dec 2007 07:18:57 +0000 (UTC) (envelope-from das@FreeBSD.org)
Received: from freefall.freebsd.org (das@localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id lBH7IvQK026354;
	Mon, 17 Dec 2007 07:18:57 GMT
	(envelope-from das@freefall.freebsd.org)
Received: (from das@localhost)
	by freefall.freebsd.org (8.14.2/8.14.1/Submit) id lBH7Iuoa026349;
	Mon, 17 Dec 2007 07:18:56 GMT (envelope-from das)
Date: Mon, 17 Dec 2007 07:18:56 GMT
Message-Id: <200712170718.lBH7Iuoa026349@freefall.freebsd.org>
To: dan@obluda.cz, das@FreeBSD.org, freebsd-bugs@FreeBSD.org
From: das@FreeBSD.org
Cc: 
Subject: Re: bin/83347: [patch] improper handling of malloc failures within
	libc's vfprintf
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Dec 2007 07:18:57 -0000

Synopsis: [patch] improper handling of malloc failures within libc's vfprintf

State-Changed-From-To: open->closed
State-Changed-By: das
State-Changed-When: Mon Dec 17 07:14:28 UTC 2007
State-Changed-Why: 
If malloc fails, the program will SIGBUS on the next line anyway, so
there's no need to call abort(). This situation can only arise if the
programmer has asked printf() to handle a very long and bizarre series
of positional arguments after exhausting all available virtual memory,
so hopefully this won't be a big deal.

http://www.freebsd.org/cgi/query-pr.cgi?pr=83347