From owner-freebsd-current@FreeBSD.ORG  Thu Feb 19 02:36:07 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 25B2C16A4CE
	for <current@freebsd.org>; Thu, 19 Feb 2004 02:36:07 -0800 (PST)
Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9E89743D1F
	for <current@freebsd.org>; Thu, 19 Feb 2004 02:36:06 -0800 (PST)
	(envelope-from bde@zeta.org.au)
Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au
	[61.8.0.86])i1JAa1LE011587;	Thu, 19 Feb 2004 21:36:01 +1100
Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246])
	i1JAZw0I019752;	Thu, 19 Feb 2004 21:36:00 +1100
Date: Thu, 19 Feb 2004 21:35:58 +1100 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
In-Reply-To: <24950.1077179049@critter.freebsd.dk>
Message-ID: <20040219211350.H1230@gamplex.bde.org>
References: <24950.1077179049@critter.freebsd.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
cc: kientzle@acm.org
Subject: Re: standard error handling for malloc() broken for user root and
 group wheel 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Feb 2004 10:36:07 -0000

On Thu, 19 Feb 2004, Poul-Henning Kamp wrote:

[The problem turned out to be mainly controlling both undefined behaviour
and standard behaviour with the same flag.]

> Think if the 'A' option as userland SIGSEGV.  (peter@ actually suggested
> that I make it kill(getpid(), SIGSEGV) before calling abort in order
> to let a process install a handler for it.

Programs can already catch SIGABRT, and they probably need to be familiar
with malloc's internals to trap its errors sort of safely, so it is
reasonable to expect them to know what to trap.

> I'm currently testing this patch:

This would fix the original problem and some others.

Bruce