From owner-freebsd-dtrace@FreeBSD.ORG Thu Jan 9 19:38:04 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 02D66A54 for ; Thu, 9 Jan 2014 19:38:04 +0000 (UTC) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CA50D16AB for ; Thu, 9 Jan 2014 19:38:03 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id kl14so3742600pab.27 for ; Thu, 09 Jan 2014 11:37:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+RdIaoheyGR8IdE/9ZvhtjCDSCNdoLQdXupa1ipSpDs=; b=lDziiai8CllwK9TGAngC3trZvz41C8lXWCGyIUmjkeep7h7XdRzLLeYL9sIPOzngIX KF3+OcLp/cVbmvpvakhW0KQ3nv/BfYMRpfg9pvGeOa3hrq0QtMsZ569sOkJ2Z9JuSPWJ 3mZvgT2xj5wwBY5MrSlj5P0FV9Fw6qFiSSiRa3npMxnhwmjgL969eTWDUvDfLinSFICD l34EEEnOa4Q0JC6NDn0fDLz4t6jcBMX/wC1skhEBEF5i1eNjm47FB8MGruG3myKdfwSb W+OoA63i6FCllvv2z8PQMri0390ujR7gBb4co+xgA0pWzcC+LajY1roorBswQ0NCf1RR wiow== X-Gm-Message-State: ALoCoQkh2nHBxjNMMVmZriwpYJyoZkchRWrwgJX7vyPZm3IYeaNqwbz1+5cEQReqDjzOzeGpc/lK X-Received: by 10.68.163.193 with SMTP id yk1mr5845071pbb.138.1389296277257; Thu, 09 Jan 2014 11:37:57 -0800 (PST) Received: from zanarkand.local ([38.104.194.102]) by mx.google.com with ESMTPSA id da3sm11867383pbc.30.2014.01.09.11.37.54 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Jan 2014 11:37:55 -0800 (PST) Message-ID: <52CEFA91.3090301@joyent.com> Date: Thu, 09 Jan 2014 11:37:53 -0800 From: Robert Mustacchi User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-dtrace@freebsd.org Subject: Re: CTF vs dwarf4 References: <52CEEE3B.7010400@FreeBSD.org> In-Reply-To: <52CEEE3B.7010400@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.17 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: Thu, 09 Jan 2014 19:38:04 -0000 On 1/9/14 10:45 , Pedro Giffuni wrote: > Hello; > > Just thought I'd point out, for those not following toolchain@, that > there are issues with newer compilers using dwarf4 by default[1]. > > It looks like instead of waiting for the elftoolchain project to catch > up with the dwarf standard we could be using dwarf support from LLVM > instead though [2]. > > Apparently the linux dtrace port is having similar issues. Another task > for the Dtrace TODO list I guess, but perhaps the Illumos guys following > the list may have some input. As one of the illumos folk following the list, I can kind of describe what at least some of us would like to do with CTF. It's worth mentioning that we're still using gcc4.4 so we're not in a realm where DWARF4 is a concern for us yet. I'm not familiar with all the differences yet, so I'm not sure how useful the rest of this e-mail will be. Currently I've been retooling ctfconvert + ctfmerge to be actually implemented in terms of libctf to make it easier for other things to actually consume, such as more long term illumos ld(1) and ideally the compilers themselves. None of this code is finished or in illumos yet. That really means that I have a slightly more useful merge (and as a result diff) written, and convert is kind of a work in progress. Probably the simplest way forward that we can all leverage is writing a new ctfconvert in terms of DWARF4 that can exist side by side the old one. eg. if you have an older compiler with dwarf2 (or you're still stuck with stabs or some other language has its own exquisite format), that'll still work. illumos last updated libdwarf in 2011. If there's a newer libdwarf that has better DWARF4 support or we need to come up with something else, let's make sure not to duplicate effort. Robert