From owner-freebsd-dtrace@FreeBSD.ORG Mon Jun 9 18:40:09 2014 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 ESMTPS id 2CC186CD; Mon, 9 Jun 2014 18:40:09 +0000 (UTC) Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DE8312498; Mon, 9 Jun 2014 18:40:08 +0000 (UTC) Received: by mail-oa0-f54.google.com with SMTP id eb12so3825753oac.27 for ; Mon, 09 Jun 2014 11:40:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9k6ON37fFv0MSGPnCHLrO5SKyVHne4C2sSWGjZd+jfU=; b=kMCv5lxxuccoXfrZ/dlvM7cjV9kKCMeT9z55UzgE9XmnxAzWSLli8tAhapYBEI3agP NRQkfvO46ehtJfrE7rMNeA8bsAtIy9o+U0dqwdB7Y4wnLq5/ctZNEsptKgzKw7Yk8Aj5 D8u8UWJ4742JhSMZ0OFE9qP7bfiu2e0eaeT3vrHR4DlZ+/Du7D6KNZ8RllzMCMoQ6uWS oCM0BGRzH39wWoVTgSGBpfWUS0L7RQR26z1c1Kg3FubibDQd67WnqOtp0Q9vgfchKixI sRfJoAiLVIjnin7SxOpoLjlz1kZCgpNMtD8HelLQsvJ9Mk5ijpc0UhEF8WfZSqfGEGv5 G+Dg== MIME-Version: 1.0 X-Received: by 10.60.52.207 with SMTP id v15mr28023588oeo.19.1402339208034; Mon, 09 Jun 2014 11:40:08 -0700 (PDT) Received: by 10.76.18.114 with HTTP; Mon, 9 Jun 2014 11:40:07 -0700 (PDT) In-Reply-To: References: Date: Mon, 9 Jun 2014 19:40:07 +0100 Message-ID: Subject: Re: DTrace probes for python 2.7.7 From: "Sevan / Venture37" To: Mark Johnston Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-dtrace@freebsd.org" X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.18 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: Mon, 09 Jun 2014 18:40:09 -0000 On 9 June 2014 19:28, Mark Johnston wrote: > This is probably because the build is running dtrace -G without the > dtrace kernel modules loaded. This shouldn't be a problem, but > currently is because dtrace(1) parses the scripts in /usr/lib/dtrace > and errors out if dtrace isn't available in the kernel. Things like > "#pragma depends_on" don't work, and there seem to be bugs in the > error reporting of libdtrace; one ends up with the error messages > above. > > I'd like to fix this by changing dtrace -G to not process scripts in > the libdir, but I'm not yet sure what the implications of this are. I > will ask on the dtrace-discuss list soon. > > In the meantime, a somewhat unsatisfactory workaround would be to just > kldload dtraceall before starting the build. > > -Mark Indeed, that was it, with dtraceall module loaded on r266655 VM's, everything fails with the same error now. "dtrace: failed to compile script Include/pydtrace.d: line 26: typedef redeclared: __uint8_t" Sevan