Issue #11553 has been updated by Carlos Alberto Lopez Perez.


Ok...

I didn't knew systemtap provided a dtrace binary, neither that it can use the DTrace probes just fine. I just tested it and it worked. Very interesting stuff.

So, I agree that is best keep the default as currently is.

I think dtrace4linux is not shipped with any distro by default. I (Debian user) had to build and install from sources myself.


I think we can close this bug as wontfix/invalid. I would do it myself, but it seems I don't have the required permissions to change the bug status.

----------------------------------------
Bug #11553: Disable by default the DTrace support on Linux systems.
https://bugs.ruby-lang.org/issues/11553#change-54296

* Author: Carlos Alberto Lopez Perez
* Status: Open
* Priority: Normal
* Assignee: 
* ruby -v: ruby 2.3.0dev (2015-09-26 trunk 51943) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
The issue is the following:

* Linux has an unnofficial implementation of DTrace (dtrace4linux).
* However, this still don't works as expected and causes either build failures or segfaults at runtime when is enabled on the Ruby build.
  * Examples:
     * https://github.com/dtrace4linux/linux/issues/111
     * https://github.com/dtrace4linux/linux/issues/116


So, I propose to (by default) disable dtrace support on Linux systems.

Otherwise users that try to build Ruby on a Linux system with dtrace4Linux installed (me for example), will end with a broken build.

Linux users willing to try this feature, can still pass the --enable-dtrace flag to enable it.

Patch attached.

---Files--------------------------------
Disable-by-default-the-dtrace-support-on-Linux-syste.patch (1.5 KB)


-- 
https://bugs.ruby-lang.org/