From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 18 19:33:16 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 681F516A421 for ; Mon, 18 Jun 2007 19:33:16 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.freebsd.org (Postfix) with ESMTP id 4918813C465 for ; Mon, 18 Jun 2007 19:33:16 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from hymn01.u.washington.edu (hymn01.u.washington.edu [140.142.8.55]) by mxout3.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l5IJXFti001054 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 18 Jun 2007 12:33:16 -0700 Received: from localhost (localhost [127.0.0.1]) by hymn01.u.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l5IJXFJk026759 for ; Mon, 18 Jun 2007 12:33:15 -0700 X-Auth-Received: from [192.55.52.1] by hymn01.u.washington.edu via HTTP; Mon, 18 Jun 2007 12:33:15 PDT Date: Mon, 18 Jun 2007 12:33:15 -0700 (PDT) From: youshi10@u.washington.edu To: hackers@freebsd.org In-Reply-To: <20070618185135.GA13076@freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.18.121634 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Cc: Subject: Re: Making sense of ktrace(1) output X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2007 19:33:16 -0000 On Mon, 18 Jun 2007, Roman Divacky wrote: >> Unfortunately I have to profile all of the source up the tree to >> create profiled symbols, and I'm running into some issues profiling >> liblegacy. >> Does anyone have any hints for getting around that, or just >> profiling all of the relevant libs? > > I think you can build fbsd with profiling of all libraries (in base) and > run it like that... > Hmm.. I think I'll actually try the -static gcc flag and see where it gets me. -Garrett