From owner-freebsd-arm@FreeBSD.ORG Sat Jan 18 00:24:58 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 C9C1A3A8 for ; Sat, 18 Jan 2014 00:24:58 +0000 (UTC) Received: from kithrup.com (Kithrup.COM [64.142.31.202]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 97A1E1974 for ; Sat, 18 Jan 2014 00:24:58 +0000 (UTC) Received: from kithrup.com (localhost [127.0.0.1]) by kithrup.com (8.14.4/8.14.4) with ESMTP id s0HNwlRw008623 for ; Fri, 17 Jan 2014 15:58:47 -0800 (PST) (envelope-from sef@kithrup.com) Received: (from sef@localhost) by kithrup.com (8.14.4/8.14.4/Submit) id s0HNwlM2008622 for freebsd-arm@FreeBSD.org; Fri, 17 Jan 2014 15:58:47 -0800 (PST) (envelope-from sef) Date: Fri, 17 Jan 2014 15:58:47 -0800 (PST) From: Sean Eric Fagan Message-Id: <201401172358.s0HNwlM2008622@kithrup.com> To: freebsd-arm@FreeBSD.org Subject: dtrace 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 00:24:58 -0000 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?