From owner-freebsd-dtrace@FreeBSD.ORG Wed Sep 10 17:24:19 2014 Return-Path: Delivered-To: freebsd-dtrace@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 B8737F57; Wed, 10 Sep 2014 17:24:19 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id BBFF31D3; Wed, 10 Sep 2014 17:24:18 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA22498; Wed, 10 Sep 2014 20:24:17 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1XRlcu-000N2y-Tz; Wed, 10 Sep 2014 20:24:16 +0300 Message-ID: <54108909.7050908@FreeBSD.org> Date: Wed, 10 Sep 2014 20:23:21 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.0 MIME-Version: 1.0 To: freebsd-toolchain@FreeBSD.org, freebsd-dtrace@FreeBSD.org Subject: WITH_CTF vs -g Content-Type: text/plain; charset=X-VIET-VPS Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.18-1 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: Wed, 10 Sep 2014 17:24:19 -0000 In my opinion WITH_CTF should imply -g in CFLAGS otherwise, as far as I can see, there is nothing to generate CTF data from. Forcing an end-user to remember to additionally pass -g is not nice. Also, I think that we can always have -g in CTFFLAGS, because the stripping step takes care of the original DWARF data in any case. But I am not 100% sure about this. What do you think? Thanks! -- Andriy Gapon From owner-freebsd-dtrace@FreeBSD.ORG Wed Sep 10 18:45:29 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 EA5BA285 for ; Wed, 10 Sep 2014 18:45:28 +0000 (UTC) Received: from nm29-vm1.bullet.mail.bf1.yahoo.com (nm29-vm1.bullet.mail.bf1.yahoo.com [98.139.213.144]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8EE9CC38 for ; Wed, 10 Sep 2014 18:45:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1410374721; bh=8XRgJXsDjD39jNM1PffhNvIoW16sSD6tB6ttviSdrG0=; h=Received:Received:Received:X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding:Message-Id:References:To:X-Mailer:From:Subject; b=ZPaM1wwnXuEyZf+v3ZNGOnP9f3MsFbOxlenaDxN5zXFDkCL2t8S0RN6JtIySZnsEqzSw1HXQWELlOjMf6CFoT2YpfSNXRHK0MJECLt8EuOIuNz5vwEYFNhnaX+5+d9bE0/U67lHQfpuXIJ841ehct7SVImzcyVFuJmeN3o2tIxN89uhQImrf70d1M1WWOCJ/07K6+PM/x8oMRDYYw2Mc7MZyZBBmzS7IbFsI/c3wNFeYnaMHy1xydsbUHWe0Mq4NvB5XVrgtds6CTIgl9FEUc1ZecJBzIzA2/xfoSNimSoUFj1tM3AoEX+F74EQgGbIucTJMk6d9etiQPL7gwYpdTA== DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s2048; d=yahoo.com; b=cuGMXOgnF/pKZCsKztXapRZGt/UpasbbDNZm0FrUeietJ7OWdgMbU4efT3i7yyi5HfxR6WNu6Wia94fhgvDjO1a+tc0HJDlGaxZfUbedscMuwWGv6n/ckNH5DPXq8US63b+kYMZXwDTfc7h24zlxPmESDqH2QPaDKeqIwItI5Kv6RNpFYRHVDU7cPFFMOvSBbwyIXl+4T3c+ce8SS2X8/BE79rx14a4z1qxJiSEx/hB1NKYf51pshrPlAZjCcdywCUURGcVgdqhA3PX7V1h8hsslWfURmlghXo/5oEVod4/AaDJY8czkCQSqDctG4qnqunhwGGQ0+if2MpxMH23L9g==; Received: from [98.139.215.141] by nm29.bullet.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 18:45:21 -0000 Received: from [68.142.230.64] by tm12.bullet.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 18:45:21 -0000 Received: from [127.0.0.1] by smtp221.mail.bf1.yahoo.com with NNFMP; 10 Sep 2014 18:45:21 -0000 X-Yahoo-Newman-Id: 424371.14573.bm@smtp221.mail.bf1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: RMAmT0MVM1l..R3RtV28yHpgevXpP_shWb5rV8TMBOtyEBs _7Pyjp4kV3vC6vwt5642frWj31._6aEjexih4OPKMPNfawA3u0eb0VtZ9x7s jv1lnCGl7SY6a0DTMagSVvT7L.1eL3FuHBECzOm9KR0ULwULpsAJSj7KEu_s 9FBInzrwRK4awQ_Akcc8MZ7V3EfGVKxxfoRXV45Cm7ao3k180kbJqVskRWOg 152VXiA1.AHkkRfPA4eR4OsNRbUVlzwHtGLrGo_etE.Ly_296hiYydErznLi 3yPocUBd0X.8Z1VHPq3gUQcM55a0X8UfwvsCd.spBwc7ICFOkAjRAwaQyIqx OjPbyTt8spzPujqs7iMMZOi.GvPoY037GQk9lmoAV.tAFsQ0PJxc8C70O_R_ 6pr78AyAIVAk3jZlkEJOXI0ZDgb9tPMtyE5wLCpLNcLXLxyZjxAzuqZOJXQA M794jb2scVBGAZivCODm04QqCN62lmL6Ym4FXmzqB_f5vlnmjAR1jzl.cmxS 0muYT7lXeBS9MV1Vj2BvvFNDRjEHfPzcZgQBIYTME6I3rxsTtns7.bhMhXrJ Mo2gb1QMAUbchqKdpD_8i3j6L3mRInFHxT9kBC6Y4X7XijT.iAaGu1c1T1UN PwJXeMGIcF1EZ_WnO X-Yahoo-SMTP: xcjD0guswBAZaPPIbxpWwLcp9Unf Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: WITH_CTF vs -g From: Pedro Giffuni In-Reply-To: <54108909.7050908@FreeBSD.org> Date: Wed, 10 Sep 2014 13:45:17 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: <58B30723-19D6-40FA-97F7-206401C5D2A2@freebsd.org> References: <54108909.7050908@FreeBSD.org> To: Andriy Gapon X-Mailer: Apple Mail (2.1878.6) Cc: freebsd-toolchain@FreeBSD.org, freebsd-dtrace@FreeBSD.org X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.18-1 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: Wed, 10 Sep 2014 18:45:29 -0000 Hi Andriy; Il giorno 10/set/2014, alle ore 12:23, Andriy Gapon ha = scritto: >=20 > In my opinion WITH_CTF should imply -g in CFLAGS otherwise, as far as = I can see, > there is nothing to generate CTF data from. Forcing an end-user to = remember to > additionally pass -g is not nice. >=20 My understanding is that CTF is meant to be a debugging format = independent of DWARF, so it should be especially useful for the cases where there is no = debugging information. Just like Illumos, we haven=92t really made much (or any) use of CTF = outside the kernel but now that is an option: http://dtrace.org/blogs/rm/2013/11/14/userland-ctf-in-dtrace/=20 > Also, I think that we can always have -g in CTFFLAGS, because the = stripping step > takes care of the original DWARF data in any case. But I am not 100% = sure about > this. >=20 > What do you think? BTW, it would be nice to see what we can take from the CTF/DDB GSoC [1]. = I understand the BSD-licensed CTF library has advanced greatly but still needs more = work. Pedro. =1B[1] = http://lists.freebsd.org/pipermail/soc-status/2014-August/000870.html From owner-freebsd-dtrace@FreeBSD.ORG Wed Sep 10 19:31:29 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 A985B8BF; Wed, 10 Sep 2014 19:31:29 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "funkthat.com", Issuer "funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 62B3C1B8; Wed, 10 Sep 2014 19:31:28 +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 s8AJVKfu040365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 10 Sep 2014 12:31:21 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id s8AJVKC2040364; Wed, 10 Sep 2014 12:31:20 -0700 (PDT) (envelope-from jmg) Date: Wed, 10 Sep 2014 12:31:20 -0700 From: John-Mark Gurney To: Pedro Giffuni Subject: Re: WITH_CTF vs -g Message-ID: <20140910193120.GA82175@funkthat.com> References: <54108909.7050908@FreeBSD.org> <58B30723-19D6-40FA-97F7-206401C5D2A2@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <58B30723-19D6-40FA-97F7-206401C5D2A2@freebsd.org> 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-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Wed, 10 Sep 2014 12:31:21 -0700 (PDT) Cc: freebsd-toolchain@freebsd.org, freebsd-dtrace@freebsd.org, Andriy Gapon X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.18-1 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: Wed, 10 Sep 2014 19:31:29 -0000 Pedro Giffuni wrote this message on Wed, Sep 10, 2014 at 13:45 -0500: > Hi Andriy; > > Il giorno 10/set/2014, alle ore 12:23, Andriy Gapon ha scritto: > > > > > In my opinion WITH_CTF should imply -g in CFLAGS otherwise, as far as I can see, > > there is nothing to generate CTF data from. Forcing an end-user to remember to > > additionally pass -g is not nice. > > > > My understanding is that CTF is meant to be a debugging format independent of DWARF, > so it should be especially useful for the cases where there is no debugging information. Except that the CTF data is generated from the DWARF data... Hence why you need to compile w/ -g... ctfconvert uses the DWARF data to make the CTF data... > Just like Illumos, we haven?t really made much (or any) use of CTF outside the kernel > but now that is an option: > > http://dtrace.org/blogs/rm/2013/11/14/userland-ctf-in-dtrace/ > > > > Also, I think that we can always have -g in CTFFLAGS, because the stripping step > > takes care of the original DWARF data in any case. But I am not 100% sure about > > this. > > > > > What do you think? > > > BTW, it would be nice to see what we can take from the CTF/DDB GSoC [1]. I understand > the BSD-licensed CTF library has advanced greatly but still needs more work. Yeh, I need to look at this more too as there are somethings I would like to do w/ CTF that I can't because the library we have doesn't export all the data.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-dtrace@FreeBSD.ORG Thu Sep 11 13:46:47 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 715B99E3 for ; Thu, 11 Sep 2014 13:46:47 +0000 (UTC) Received: from ost.citrin.ru (ost.citrin.ru [193.169.234.215]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 28AF8DBE for ; Thu, 11 Sep 2014 13:46:47 +0000 (UTC) Received: from citrin.office.vega.ru (office-nat.spylog.net [193.169.234.6]) (Authenticated sender: citrin@citrin.ru) by ost.citrin.ru (Postfix) with ESMTPSA id BA323CEB6E7 for ; Thu, 11 Sep 2014 13:46:37 +0000 (UTC) Message-ID: <5411A7BD.7020705@citrin.ru> Date: Thu, 11 Sep 2014 17:46:37 +0400 From: Anton Yuzhaninov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130516 Thunderbird/17.0.6 MIME-Version: 1.0 To: freebsd-dtrace@freebsd.org Subject: Pid provider Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=citrin.ru; s=s0; t=1410443197; bh=WSG/ucy5FuQAQ8LqN6QY7UKfk3uWXvXn5MMC8FqOGms=; h=Message-ID:Date:From:MIME-Version:To:Subject:Content-Type: Content-Transfer-Encoding; b=fdN4d/CEr4DbL5DovGHRsfiqNdFDjIsU6pBqRaf4YpwcAcFstJbUYS602YXxZYqDg pJZi5/PckGdL8ZQQuc+MXB7ESxrdzI9u5OC2YchWAAK3gi2IEQHXbWIvrG86uKYeVH WXor7913/PwLsTmrd9TAc67YHRxFHkJ9/wdkm1WM= X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Sep 2014 13:46:47 -0000 Is PID provider is usable in FreeBSD? I try to list probes with dtrace -ln 'pid$target:::entry' -p NNN And for most processes no function from main binary shown (only functions from shared libraries are listed). For some only some functions are shown, e. g. for tcsh only two functions shown: ID PROVIDER MODULE FUNCTION NAME 61372 pid57232 tcsh glob entry 61373 pid57232 tcsh globfree entry Also there is bug_or_feature: examined process terminated if dtrace command terminated, e. g. run: dtrace -ln 'pid$target:::entry' -p XX | less then type q to quit from less - process with pid XX will be terminated. From owner-freebsd-dtrace@FreeBSD.ORG Thu Sep 11 15:01:30 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 9BAAF5A9 for ; Thu, 11 Sep 2014 15:01:30 +0000 (UTC) Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) (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 7005A8FE for ; Thu, 11 Sep 2014 15:01:30 +0000 (UTC) Received: by mail-pa0-f52.google.com with SMTP id kq14so6974014pab.25 for ; Thu, 11 Sep 2014 08:01:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=aCUUeALa/ZzJOLqV/rkPsNcjO3K1qTjOIxGU70tHQ8g=; b=izmELcd6yj+FbCdTGcOfu9gSfgAfIyf6SRVf3k89Vmqi75CxcYa5Wa/lafFsxIuZ0r IumNYe0cngnd3txhO/E9ZLcCqbfGpNb1qjQP1O5Syersfy32RIXnZ9D6VCV0+8oGAqz0 T55iAkMswHSjHh/j4WVdQzw/R6m9R+53tr2U6TMJVYR8gWW54f9L1auLGs5ISDXloKtK cy5VuWZuP2q4pxe/keA4FTDFsCwjO7V+/su+SB5Cu1PaODR9zrVkw/ioRNOOt2VJoBWY fpKcZv4IMzy/GNiHoty9LoWEeFI+C7FAac0cNJHuu4PCZLb0/hHRZfCrz2xTcFCcPVNc 7qPw== X-Received: by 10.68.69.97 with SMTP id d1mr2331061pbu.49.1410447689484; Thu, 11 Sep 2014 08:01:29 -0700 (PDT) Received: from charmander.Belkin (c-66-235-3-150.sea.wa.customer.broadstripe.net. [66.235.3.150]) by mx.google.com with ESMTPSA id dg5sm1437162pac.12.2014.09.11.08.01.28 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 11 Sep 2014 08:01:28 -0700 (PDT) Sender: Mark Johnston Date: Thu, 11 Sep 2014 08:01:11 -0700 From: Mark Johnston To: Anton Yuzhaninov Subject: Re: Pid provider Message-ID: <20140911150111.GA71246@charmander.Belkin> References: <5411A7BD.7020705@citrin.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5411A7BD.7020705@citrin.ru> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-dtrace@freebsd.org X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Sep 2014 15:01:30 -0000 On Thu, Sep 11, 2014 at 05:46:37PM +0400, Anton Yuzhaninov wrote: > Is PID provider is usable in FreeBSD? > > I try to list probes with > > dtrace -ln 'pid$target:::entry' -p NNN > > And for most processes no function from main binary shown (only functions from > shared libraries are listed). For some only some functions are shown, e. g. for > tcsh only two functions shown: > ID PROVIDER MODULE FUNCTION NAME > 61372 pid57232 tcsh glob entry > 61373 pid57232 tcsh globfree entry Is the tcsh binary stripped? The pid provider can't reliably do symbol lookups in this case, so most of the probes will be missing. Try rebuilding with cd /usr/src/bin/csh && make && make install STRIP= On my system this results in many more probes from the tcsh executable. > > Also there is bug_or_feature: examined process terminated if dtrace command > terminated, e. g. run: > dtrace -ln 'pid$target:::entry' -p XX | less > then type q to quit from less - process with pid XX will be terminated. Seems like a bug to me. :) I suspect that dtrace(1) is exiting without detaching from the child process first. Could you submit a PR for this? Thanks, -Mark From owner-freebsd-dtrace@FreeBSD.ORG Thu Sep 11 15:07:33 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 2618CD0D; Thu, 11 Sep 2014 15:07:33 +0000 (UTC) Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176]) (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 EC6A59AC; Thu, 11 Sep 2014 15:07:32 +0000 (UTC) Received: from [96.232.17.88] (port=62402 helo=[10.189.221.171]) by vps.hungerhost.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1XS5y6-0007oL-V1; Thu, 11 Sep 2014 11:07:31 -0400 From: "George Neville-Neil" To: "John-Mark Gurney" Subject: Re: WITH_CTF vs -g Date: Thu, 11 Sep 2014 11:07:16 -0400 Message-ID: <4227AECE-CD12-4C1E-B610-8BE81E6DBF0D@neville-neil.com> In-Reply-To: <20140910193120.GA82175@funkthat.com> References: <54108909.7050908@FreeBSD.org> <58B30723-19D6-40FA-97F7-206401C5D2A2@freebsd.org> <20140910193120.GA82175@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; format=flowed X-Mailer: MailMate (1.8r4469) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - neville-neil.com X-Get-Message-Sender-Via: vps.hungerhost.com: authenticated_id: gnn@neville-neil.com Cc: Andriy Gapon , freebsd-dtrace@freebsd.org, freebsd-toolchain@freebsd.org X-BeenThere: freebsd-dtrace@freebsd.org X-Mailman-Version: 2.1.18-1 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, 11 Sep 2014 15:07:33 -0000 On 10 Sep 2014, at 15:31, John-Mark Gurney wrote: > Pedro Giffuni wrote this message on Wed, Sep 10, 2014 at 13:45 -0500: >> Hi Andriy; >> >> Il giorno 10/set/2014, alle ore 12:23, Andriy Gapon >> ha scritto: >> >>> >>> In my opinion WITH_CTF should imply -g in CFLAGS otherwise, as far >>> as I can see, >>> there is nothing to generate CTF data from. Forcing an end-user to >>> remember to >>> additionally pass -g is not nice. >>> >> >> My understanding is that CTF is meant to be a debugging format >> independent of DWARF, >> so it should be especially useful for the cases where there is no >> debugging information. > > Except that the CTF data is generated from the DWARF data... Hence > why you need to compile w/ -g... ctfconvert uses the DWARF data to > make the CTF data... > >> Just like Illumos, we haven?t really made much (or any) use of CTF >> outside the kernel >> but now that is an option: >> >> http://dtrace.org/blogs/rm/2013/11/14/userland-ctf-in-dtrace/ >> >> >>> Also, I think that we can always have -g in CTFFLAGS, because the >>> stripping step >>> takes care of the original DWARF data in any case. But I am not >>> 100% sure about >>> this. >>> >> >>> What do you think? >> >> >> BTW, it would be nice to see what we can take from the CTF/DDB GSoC >> [1]. I understand >> the BSD-licensed CTF library has advanced greatly but still needs >> more work. > > Yeh, I need to look at this more too as there are somethings I would > like to do w/ CTF that I can't because the library we have doesn't > export all the data.. > And on the main topic, yes, one should imply the other. Go for it. Best, George