From owner-freebsd-stable@FreeBSD.ORG Mon Mar 31 14:15:19 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 60B97B44; Mon, 31 Mar 2014 14:15:19 +0000 (UTC) Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com [IPv6:2607:f8b0:400c:c03::22a]) (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 ED61B29F; Mon, 31 Mar 2014 14:15:18 +0000 (UTC) Received: by mail-vc0-f170.google.com with SMTP id hu19so8433760vcb.15 for ; Mon, 31 Mar 2014 07:15:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=DvpKQlc9SW4OsYs2f3gLtiubhGjOz6vUuqaxoGqedmw=; b=usMNpPMDZm8UhFTJy8ebZZ3YJl7i7ovPaZ80Lo6xGeNwLLaw2lyuuJO2qm2t2QPgKZ vZxuz+z8JUStBAKiyvJhs4lOmPbsrq+NbTHJPb5Au3lFMT6xYMzccggFqRc7uA317Fhv HsVeTdeh/mSAp23SyASVp3eol5QwGhzeKYRgOCoyNhW72R6pZFjRXVpLMz6dE8bgfSWd DbeCyBD5ddm0Iov1Iwcz76ExtabplHVFoDQ6KosAQ2uwO/FLGU1JXSNh8UL3oJiFk138 XpUdr2TVpdXlu6AsQ4HcLBH+X1lo6ZavSunAv2vWaqMA9mtZaz7aLwG2jGvQVXq8x6bb zpRA== MIME-Version: 1.0 X-Received: by 10.58.154.10 with SMTP id vk10mr3478446veb.18.1396275318073; Mon, 31 Mar 2014 07:15:18 -0700 (PDT) Sender: markjdb@gmail.com Received: by 10.220.162.68 with HTTP; Mon, 31 Mar 2014 07:15:17 -0700 (PDT) In-Reply-To: <16CDBEB1-3900-4EE4-B643-C95BA58F4C4E@FreeBSD.org> References: <0E7E81A1-54E9-4920-A360-005A1C0C4D47@FreeBSD.org> <20140327002240.GC49672@raichu> <20140328225902.GA7417@soulhacker> <16CDBEB1-3900-4EE4-B643-C95BA58F4C4E@FreeBSD.org> Date: Mon, 31 Mar 2014 10:15:17 -0400 X-Google-Sender-Auth: kT7DrZvFvGtUC9gQiyp4iciLyEI Message-ID: Subject: Re: HEADS UP: merged llvm/clang 3.4 From: Mark Johnston To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-stable stable , Kai Wang X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Mar 2014 14:15:19 -0000 On Sat, Mar 29, 2014 at 1:25 PM, Dimitry Andric wrote: > On 28 Mar 2014, at 23:59, Kai Wang wrote: >> On Thu, Mar 27, 2014 at 11:03:11PM -0400, Mark Johnston wrote: >>> On Thu, Mar 27, 2014 at 6:32 PM, Dimitry Andric wrote: >>>> On 27 Mar 2014, at 01:22, Mark Johnston wrote: > ... >>>>> DTrace seems to no longer work properly on stable/10; I get errors like >>>>> the following >>>>> >>>>> dtrace: invalid probe specifier pid$target::malloc:entry{ }: >>>>> "/usr/lib/dtrace/io.d", line 49: cannot find type: struct devstat*: Type >>>>> information is in parent and unavailable > ... >> I extracted a patch for ctfconvert from -head and adapted it to the >> old libdwarf in stable/10. The patch fixes some type parsing bugs for >> ctfconvert with Clang 3.4 objects, which might be related to your >> DTrace issue, but I'm not sure... >> >> The patch is here: >> >> http://people.freebsd.org/~kaiw/ctfconvert-stable10.patch >> >> (It should apply to stable/10. Both world and kernel needs recompile) > > Thanks! I have merged this to stable/10, and (slightly modified) to > stable/9, in r263915. I have verified that on both branches, simple > dtrace commands like: > > dtrace -n 'syscall:::entry { @num[execname] = count(); }' > > work as expected. I assume DTrace will now work OK, but any other more > extensive verification by somebody familiar with DTrace is welcome. Thank you both! I'll do some testing in the next couple of days and report back if I run into any new problems. > > Note that you *must* first build and install at least the CTF tools, > before building a kernel, otherwise the broken versions from /usr/bin > will still be used. This is actually a problem in our kernel build > tools stage, but a solution for that is still missing. > > -Dimitry >