From owner-freebsd-bugs@FreeBSD.ORG Fri Aug 29 20:34:44 2014 Return-Path: Delivered-To: freebsd-bugs@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 96EBB7F6 for ; Fri, 29 Aug 2014 20:34:44 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 63E1C1392 for ; Fri, 29 Aug 2014 20:34:44 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7TKYiVZ005208 for ; Fri, 29 Aug 2014 20:34:44 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 193109] [dtrace] cannot compile psinfo.d: line 37: syntax error near "uid_t" Date: Fri, 29 Aug 2014 20:34:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ngie@FreeBSD.org X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Aug 2014 20:34:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193109 --- Comment #3 from Garrett Cooper --- (In reply to Mark Johnston from comment #2) > (In reply to Mark Johnston from comment #1) > > This type of error is almost always the result of some sort of > > misconfiguration. A couple of things to check: > > > > 1. Is kern.bootfile set to the correct path for the running kernel? > > 2. Is there CTF data present in the kernel? > > The latter can be checked with something like 'ctfdump /boot/kernel/kernel'. Yup, that's ok: % [ -n "$(ctfdump $(kenv kernelname))" ] && echo "I have CTF in the kernel" I have CTF in the kernel > If nothing interesting turns up, try running a dtrace command manually on > the system in question, e.g. "dtrace -n 'fbt::kern_ioctl:entry'" or so. If > it fails with the same error, try running it again with the DTRACE_DEBUG > environment variable set to 1 and paste the output. That command works (and prints out info) $ sudo dtrace -n 'fbt::kern_ioctl:entry' dtrace: description 'fbt::kern_ioctl:entry' matched 1 probe CPU ID FUNCTION:NAME 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 1 34641 kern_ioctl:entry 0 34641 kern_ioctl:entry 1 34641 kern_ioctl:entry ^C $ I don't know how the preprocessing and resolution of C typedefs is handled with dtrace, but it seems like the issue is there and not in the actual dtrace runtime... -- You are receiving this mail because: You are the assignee for the bug.