From owner-freebsd-arch@FreeBSD.ORG Mon Sep 13 00:09:40 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D194816A4CE for ; Mon, 13 Sep 2004 00:09:40 +0000 (GMT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4BB643D41 for ; Mon, 13 Sep 2004 00:09:40 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) i8D09dvA093305; Sun, 12 Sep 2004 17:09:39 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id i8D09cup093302; Sun, 12 Sep 2004 17:09:38 -0700 (PDT) (envelope-from dillon) Date: Sun, 12 Sep 2004 17:09:38 -0700 (PDT) From: Matthew Dillon Message-Id: <200409130009.i8D09cup093302@apollo.backplane.com> To: "M. Warner Losh" References: <20040912.152047.16265436.imp@bsdimp.com> <20040912.153323.115746063.imp@bsdimp.com> cc: arch@freebsd.org cc: phk@phk.freebsd.dk Subject: Re: [BIKESHED] Giving abort(2) a reason X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Sep 2004 00:09:40 -0000 :... :: >: :: >: syslog() or anything else using varargs is not going to work... :: > :: >Wouldn't it be better to have a more generic 'Put this into dmesg' :: >thing that doesn't require malloc to work? It seems silly to bloat :: >the kernel for only a malloc failure case... :: :: That is what I thought I proposed... : :You proposed 'put this into dmesg, with a lot of other stuff and then :abort the program.' I was wanting 'put this into dmesg' and nothing :else... : :Warner I like the idea of an abort2() [though I wish it were named something else] but I see no need for it to be made a system call. It simply would not be appropriate... abort2() does not do anything that couldn't be done in userland (even if malloc is non-operational at the time). A system call would be a hack to avoid having to clean up the related libc functions and/or provide a path through libc to implement the feature (perhaps a special syslogx() call). -Matt Matthew Dillon