Date: Mon, 17 Apr 2017 15:54:46 -0400 From: Ryan Stone <rysto32@gmail.com> To: George Neville-Neil <gnn@neville-neil.com> Cc: Jan Beich <jbeich@freebsd.org>, freebsd-gecko@freebsd.org, "freebsd-dtrace@freebsd.org" <freebsd-dtrace@freebsd.org> Subject: Re: DTrace issues? Message-ID: <CAFMmRNwudC_bb_rqus=fqM4tdwVp58fxUByLUmT8Df1J1Pdb7A@mail.gmail.com> In-Reply-To: <76897620-E958-4AE2-9B6C-062C59526614@neville-neil.com> References: <3CEE1970-719B-42D1-A95A-FEAD3F375A30@neville-neil.com> <20170212191826.5599A45EA@freefall.freebsd.org> <shlc-anmv-wny@FreeBSD.org> <77416dea-1e9d-4911-b5d0-2ebac227af7e@Spark> <wpam-jesd-wny@FreeBSD.org> <76897620-E958-4AE2-9B6C-062C59526614@neville-neil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 15, 2017 at 10:50 AM, George Neville-Neil <gnn@neville-neil.com> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFMmRNwudC_bb_rqus=fqM4tdwVp58fxUByLUmT8Df1J1Pdb7A>