Re: DTrace issues?
On 17 Apr 2017, at 17:26, Mark Johnston wrote: On Mon, Apr 17, 2017 at 09:28:07PM +0100, Sevan / Venture37 wrote: 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). I think the more significant difference is that Apple has more control over their toolchain and have modified it to directly implement the functionality that's overwise implemented by dtrace -G. As Ryan pointed out, this functionality really belongs in the static linker; one more piece of evidence for this is the number of non-trivial modifications we've needed to make to dtrace -G to avoid relying on undocumented behaviour in the Sun link editor, and later, GNU ld 2.17. Now that FreeBSD is transitioning to lld, we have some opportunity to implement USDT support in the static linker, and at least one of the lld developers seems amenable to proposals along those lines. However, I don't know of any concrete plans or designs. Seems like something we could discuss in an RFD: https://github.com/opendtrace/rfd Best, George ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
On Mon, Apr 17, 2017 at 09:28:07PM +0100, Sevan / Venture37 wrote: > 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). I think the more significant difference is that Apple has more control over their toolchain and have modified it to directly implement the functionality that's overwise implemented by dtrace -G. As Ryan pointed out, this functionality really belongs in the static linker; one more piece of evidence for this is the number of non-trivial modifications we've needed to make to dtrace -G to avoid relying on undocumented behaviour in the Sun link editor, and later, GNU ld 2.17. Now that FreeBSD is transitioning to lld, we have some opportunity to implement USDT support in the static linker, and at least one of the lld developers seems amenable to proposals along those lines. However, I don't know of any concrete plans or designs. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
On 17 Apr 2017, at 16:28, Sevan / Venture37 wrote: 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). Well at least I now "get" the issue. Thanks. Best, George ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
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 ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
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. ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
On 15 Apr 2017, at 3:44, Jan Beich wrote: Sean Chittenden writes: On Apr 12, 2017, 22:19 -0700, Jan Beich , wrote: jbe...@freebsd.org (Jan Beich) writes: If so, please point me at active bugs in this area. Firefox is affected by a few more DTrace issues but those are old and have been worked around in the ports tree. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214556 # dtrace on aarch64 https://bugzilla.mozilla.org/show_bug.cgi?id=1041353 # dtrace vs. ld.gold https://bugzilla.mozilla.org/show_bug.cgi?id=702179 # dtrace vs. static libs https://bugzilla.mozilla.org/show_bug.cgi?id=1353558 # FF55 bustage Is there any chance FreeBSD adds compatibility with DTrace on OS X? I think you mean, "when will Apple update its DTrace to be more compatible with FreeBSD?" The version of DTrace that ships with macOS is out of date and yes, we would love it if it were more up to date in macOS. :( -sc On FreeBSD "dtrace -G" causes no end of grief with various build systems. Do you mean OS X is going to inherit it? Can you explain this grief? What is the problem? Best, George ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
Sean Chittenden writes: > On Apr 12, 2017, 22:19 -0700, Jan Beich , wrote: >> jbe...@freebsd.org (Jan Beich) writes: >> >> > > If so, please point me at active bugs in this area. >> > >> > Firefox is affected by a few more DTrace issues but those are old and >> > have been worked around in the ports tree. >> > >> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214556 # dtrace on >> > aarch64 >> > https://bugzilla.mozilla.org/show_bug.cgi?id=1041353 # dtrace vs. ld.gold >> > https://bugzilla.mozilla.org/show_bug.cgi?id=702179 # dtrace vs. static >> > libs >> >> https://bugzilla.mozilla.org/show_bug.cgi?id=1353558 # FF55 bustage >> >> Is there any chance FreeBSD adds compatibility with DTrace on OS X? > > I think you mean, "when will Apple update its DTrace to be more > compatible with FreeBSD?" The version of DTrace that ships with macOS > is out of date and yes, we would love it if it were more up to date in > macOS. :( -sc On FreeBSD "dtrace -G" causes no end of grief with various build systems. Do you mean OS X is going to inherit it? ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
Hi Sean, Can you indicate us what you are missing from DTrace on macOS ? Filing a bug report at http://bugreport.apple.com is also a good way of alerting us on issues you are facing with DTrace on macOS. Thanks, - Samuel Lepetit > On Apr 13, 2017, at 13:51, Sean Chittenden wrote: > > I think you mean, "when will Apple update its DTrace to be more compatible > with FreeBSD?" The version of DTrace that ships with macOS is out of date and > yes, we would love it if it were more up to date in macOS. :( -sc > > -sc > > -- > Sean Chittenden > >> On Apr 12, 2017, 22:19 -0700, Jan Beich , wrote: >> jbe...@freebsd.org (Jan Beich) writes: >> If so, please point me at active bugs in this area. >>> >>> Firefox is affected by a few more DTrace issues but those are old and >>> have been worked around in the ports tree. >>> >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214556 # dtrace on aarch64 >>> https://bugzilla.mozilla.org/show_bug.cgi?id=1041353 # dtrace vs. ld.gold >>> https://bugzilla.mozilla.org/show_bug.cgi?id=702179 # dtrace vs. static libs >> >> https://bugzilla.mozilla.org/show_bug.cgi?id=1353558 # FF55 bustage >> >> Is there any chance FreeBSD adds compatibility with DTrace on OS X? >> ___ >> freebsd-dtr...@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace >> To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org" > ___ > freebsd-dtr...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace > To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org" ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
Apple is pulling changes from FreeBSD into Mac OS, but, of course that schedule is not known to us outside of Apple. Best, George On 13 Apr 2017, at 1:51, Sean Chittenden wrote: I think you mean, "when will Apple update its DTrace to be more compatible with FreeBSD?" The version of DTrace that ships with macOS is out of date and yes, we would love it if it were more up to date in macOS. :( -sc -sc -- Sean Chittenden On Apr 12, 2017, 22:19 -0700, Jan Beich , wrote: jbe...@freebsd.org (Jan Beich) writes: If so, please point me at active bugs in this area. Firefox is affected by a few more DTrace issues but those are old and have been worked around in the ports tree. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214556 # dtrace on aarch64 https://bugzilla.mozilla.org/show_bug.cgi?id=1041353 # dtrace vs. ld.gold https://bugzilla.mozilla.org/show_bug.cgi?id=702179 # dtrace vs. static libs https://bugzilla.mozilla.org/show_bug.cgi?id=1353558 # FF55 bustage Is there any chance FreeBSD adds compatibility with DTrace on OS X? ___ freebsd-dtr...@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org" ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
I think you mean, "when will Apple update its DTrace to be more compatible with FreeBSD?" The version of DTrace that ships with macOS is out of date and yes, we would love it if it were more up to date in macOS. :( -sc -sc -- Sean Chittenden On Apr 12, 2017, 22:19 -0700, Jan Beich , wrote: > jbe...@freebsd.org (Jan Beich) writes: > > > > If so, please point me at active bugs in this area. > > > > Firefox is affected by a few more DTrace issues but those are old and > > have been worked around in the ports tree. > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214556 # dtrace on aarch64 > > https://bugzilla.mozilla.org/show_bug.cgi?id=1041353 # dtrace vs. ld.gold > > https://bugzilla.mozilla.org/show_bug.cgi?id=702179 # dtrace vs. static libs > > https://bugzilla.mozilla.org/show_bug.cgi?id=1353558 # FF55 bustage > > Is there any chance FreeBSD adds compatibility with DTrace on OS X? > ___ > freebsd-dtr...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-dtrace > To unsubscribe, send any mail to "freebsd-dtrace-unsubscr...@freebsd.org" ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
jbe...@freebsd.org (Jan Beich) writes: >> If so, please point me at active bugs in this area. > > Firefox is affected by a few more DTrace issues but those are old and > have been worked around in the ports tree. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214556 # dtrace on aarch64 > https://bugzilla.mozilla.org/show_bug.cgi?id=1041353 # dtrace vs. ld.gold > https://bugzilla.mozilla.org/show_bug.cgi?id=702179 # dtrace vs. static libs https://bugzilla.mozilla.org/show_bug.cgi?id=1353558 # FF55 bustage Is there any chance FreeBSD adds compatibility with DTrace on OS X? ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
On 12 Feb 2017, at 14:18, Jan Beich wrote: "George Neville-Neil" writes: Hi, I'm told that the reason we don't have a firefox package is due to DTrace. "firefox" package was masked on 12.0-CURRENT for 1 week due 2 regressions since then fixed. Other FreeBSD release are unaffected. https://svnweb.freebsd.org/changeset/base/313504 https://svnweb.freebsd.org/changeset/ports/433889 https://svnweb.freebsd.org/changeset/ports/433904 If so, please point me at active bugs in this area. Firefox is affected by a few more DTrace issues but those are old and have been worked around in the ports tree. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214556 # dtrace on aarch64 https://bugzilla.mozilla.org/show_bug.cgi?id=1041353 # dtrace vs. ld.gold https://bugzilla.mozilla.org/show_bug.cgi?id=702179 # dtrace vs. static libs OK, thanks! Best, George ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
Re: DTrace issues?
"George Neville-Neil" writes: > Hi, > > I'm told that the reason we don't have a firefox package is due to > DTrace. "firefox" package was masked on 12.0-CURRENT for 1 week due 2 regressions since then fixed. Other FreeBSD release are unaffected. https://svnweb.freebsd.org/changeset/base/313504 https://svnweb.freebsd.org/changeset/ports/433889 https://svnweb.freebsd.org/changeset/ports/433904 > If so, please point me at active bugs in this area. Firefox is affected by a few more DTrace issues but those are old and have been worked around in the ports tree. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214556 # dtrace on aarch64 https://bugzilla.mozilla.org/show_bug.cgi?id=1041353 # dtrace vs. ld.gold https://bugzilla.mozilla.org/show_bug.cgi?id=702179 # dtrace vs. static libs ___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
