From owner-freebsd-current@FreeBSD.ORG Sun Feb 8 18:20:22 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 864201065672 for ; Sun, 8 Feb 2009 18:20:22 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from springbank.echomania.com (springbank.echomania.com [82.94.255.114]) by mx1.freebsd.org (Postfix) with ESMTP id 450148FC0A for ; Sun, 8 Feb 2009 18:20:22 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from localhost (localhost [127.0.0.1]) by springbank.echomania.com (Postfix) with ESMTP id C8C18A7087; Sun, 8 Feb 2009 19:20:20 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at springbank.echomania.com Received: from springbank.echomania.com ([127.0.0.1]) by localhost (springbank.echomania.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id A+F5gaWvu6nj; Sun, 8 Feb 2009 19:20:02 +0100 (CET) Received: from [87.251.56.140] (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by springbank.echomania.com (Postfix) with ESMTPSA id D130BA707C; Sun, 8 Feb 2009 19:20:02 +0100 (CET) Message-ID: <498F2253.9010204@andric.com> Date: Sun, 08 Feb 2009 19:20:03 +0100 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1b3pre) Gecko/20090207 Shredder/3.0b2pre MIME-Version: 1.0 To: barney_cordoba@yahoo.com References: <426059.88012.qm@web63906.mail.re1.yahoo.com> In-Reply-To: <426059.88012.qm@web63906.mail.re1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: is there a protected/locked printf? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2009 18:20:22 -0000 On 2009-02-08 18:31, Barney Cordoba wrote: > Its taking me all day to figure out something that should take 5 minutes > if I could get printf to not print garbage. Is there a mulitcore version > of printf that isn't completely useless for use for trace code? Add: options PRINTF_BUFR_SIZE=128 to your kernel config file, that might help.