From owner-freebsd-dtrace@FreeBSD.ORG Tue Oct 15 23:32:23 2013 Return-Path: Delivered-To: freebsd-dtrace@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 ESMTP id CF53463B for ; Tue, 15 Oct 2013 23:32:23 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B236C2053 for ; Tue, 15 Oct 2013 23:32:20 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r9FNWJcS044587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 15 Oct 2013 16:32:19 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r9FNWJWH044586 for freebsd-dtrace@FreeBSD.org; Tue, 15 Oct 2013 16:32:19 -0700 (PDT) (envelope-from jmg) Date: Tue, 15 Oct 2013 16:32:19 -0700 From: John-Mark Gurney To: freebsd-dtrace@FreeBSD.org Subject: dtrace -c doesn't work? Message-ID: <20131015233219.GZ56872@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Tue, 15 Oct 2013 16:32:19 -0700 (PDT) X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "A discussion list for developers working on DTrace in FreeBSD." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Oct 2013 23:32:23 -0000 Well, I've decided to try to learn dtrace to do some benchmarking, and so I tried to use -c to measure what the command does... except it seems to fail... even the simple: dtrace -n 'syscall:::entry { @num[execname] = count(); }' -c 'echo foo' doesn't work... it gives me: # dtrace -n 'syscall:::entry { @num[execname] = count(); }' -c 'echo foo' foo dtrace: failed to control pid 3766: process exited with status 0 ktrace shows it execing /bin/echo and it running fine, but for some reason dtrace can't handle it... P.S. Why are dtrace and dtraceall seperate? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."