From owner-freebsd-gecko@freebsd.org Mon Apr 17 20:28:08 2017 Return-Path: Delivered-To: freebsd-gecko@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1CF7D42F97; Mon, 17 Apr 2017 20:28:08 +0000 (UTC) (envelope-from venture37@gmail.com) Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 911FB18EC; Mon, 17 Apr 2017 20:28:08 +0000 (UTC) (envelope-from venture37@gmail.com) Received: by mail-qk0-x22d.google.com with SMTP id p68so114204408qke.1; Mon, 17 Apr 2017 13:28:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AW8F6YF7juFfz8y0RMMsOFfMlRA2aZzs15IX70WVDEM=; b=X4OV05mqiwjnWQ44/Ef8OjG6bRtxdsZgCx0m9MowJlv78hShvfFQWNOI80mEzM4lS4 Vx+W47KryqVgQSgQkuLnBSgqSY/EuIjDmSPI+6hm+OudoFcMWWC2yVqhUkdDS1v38fJd V+Q8dG8EJrGWF9i0ML6LarRhQZgn7vMW3UhnIS1CNiarl+7e3Fn8zMWO05CwSkek+oUt 8ypyXU1DYhSgzZKdQ/KskaOkw7tpu3torPtOemEFPnsLY4/I4Hf/hKzfTgiEqdMewjLm /pI4FpHD+R4SFeQmsPAj+ltP1GjlppJTZEpoJhTEab1P80pw55kcsM4MbVD5JD2zAqCp 88jA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AW8F6YF7juFfz8y0RMMsOFfMlRA2aZzs15IX70WVDEM=; b=dA05d2hcscmco2wEW+yF3LP7t8pVncP7N13vSsR0oEcJZj7yULW0vWuM+7PovhhBkW 3yCQfTGFW/eyrcUosjcAxVv2EL5em2x4r3f071bX8aD0W4Bntv/KOXsG5d2L1LQTzNDu yUZXwbncd2sIpDkedxsPFkndzCO0315m5iooYzohFe1oMH9hj2ptLNkuoRVEZmnaryEm 0Tk/ws8wTF3Ww+2umq4zd2Xx7i8CGVneEXj9O2mgn9BNqCjDmAcToa6MJ0zd/927JqSm JWuBNVEQvb8bX5HqORmiXAzaZPUmXwGa+krinNhwDgzls83VwZyWopVYmzh9XIrWlTwu QBuw== X-Gm-Message-State: AN3rC/4VqsJGTshR0p5vmwGePbY795b4+nJ+3ZLDSgGNw87icDBURkJB zo4zgR+mbxrU+gZaKk48Yynd/L8IHg== X-Received: by 10.55.54.144 with SMTP id d138mr9798055qka.207.1492460887714; Mon, 17 Apr 2017 13:28:07 -0700 (PDT) MIME-Version: 1.0 Received: by 10.55.91.68 with HTTP; Mon, 17 Apr 2017 13:28:07 -0700 (PDT) In-Reply-To: References: <3CEE1970-719B-42D1-A95A-FEAD3F375A30@neville-neil.com> <20170212191826.5599A45EA@freefall.freebsd.org> <77416dea-1e9d-4911-b5d0-2ebac227af7e@Spark> <76897620-E958-4AE2-9B6C-062C59526614@neville-neil.com> From: "Sevan / Venture37" Date: Mon, 17 Apr 2017 21:28:07 +0100 Message-ID: Subject: Re: DTrace issues? To: Ryan Stone Cc: George Neville-Neil , freebsd-gecko@freebsd.org, Jan Beich , "freebsd-dtrace@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-gecko@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Gecko Rendering Engine issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2017 20:28:09 -0000 On 17 April 2017 at 20:54, Ryan Stone wrote: > On Sat, Apr 15, 2017 at 10:50 AM, George Neville-Neil > wrote: > >> >> Can you explain this grief? What is the problem? >> >> Best, >> George >> > > dtrace -G requires the ability to modify the object files in-place before > linking. This causes havoc if the objects are in .a archives (dtrace can't > read those) or if the objects need to be linked into multiple binaries. It > also destroys the ability to do an incremental build, as dtrace -G can't be > run on the same object twice. > > The whole process is really a hack. The build actions done by dtrace > should be done by the compiler and linker instead. Getting the linker to > support the process would go a long way, as then dtrace -G could be run on > individual objects and most of my complaints go away. Not to detract from the issue with the -G flag, I just wanted to highlight that it's used for ELF binaries, until Apple switches away from Mach-o, this wont be an issue there (dtrace on OS X does not feature the -G flag). Sevan