From owner-freebsd-arm@FreeBSD.ORG Sat Jan 18 14:18:23 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 90D4A6D2 for ; Sat, 18 Jan 2014 14:18:23 +0000 (UTC) Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 63F17149B for ; Sat, 18 Jan 2014 14:18:23 +0000 (UTC) Received: from 63-234-219-145.dia.static.qwest.net ([63.234.219.145]:41466 helo=[172.26.54.242]) by vps.hungerhost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from ) id 1W4Wj7-0001Jl-F2; Sat, 18 Jan 2014 09:18:21 -0500 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: dtrace From: George Neville-Neil In-Reply-To: <201401172358.s0HNwlM2008622@kithrup.com> Date: Sat, 18 Jan 2014 09:18:21 -0500 Content-Transfer-Encoding: 7bit Message-Id: <37F5A376-4A86-4675-9319-9C6D0B11CB7E@neville-neil.com> References: <201401172358.s0HNwlM2008622@kithrup.com> To: Sean Eric Fagan X-Mailer: Apple Mail (2.1827) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - neville-neil.com X-Get-Message-Sender-Via: vps.hungerhost.com: authenticated_id: gnn@neville-neil.com Cc: freebsd-arm@FreeBSD.org X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Jan 2014 14:18:23 -0000 On Jan 17, 2014, at 18:58 , Sean Eric Fagan wrote: > I'm dumb, I guess. I can't figure out what's needed for dtrace to > work. > > I've got the various modules compiled, and the libraries and utilities, > and "dtrace -l" shows lots of trace points, but if I try to actually > trace anything, it sadly hangs the pi. > > Suggestions? Panic the box and get us a back trace. Best, George