From: shevegen@...
Date: 2015-09-27T15:35:53+00:00
Subject: [ruby-core:70925] [Ruby trunk - Bug #11553] Disable by default the DTrace support on Linux systems.

Issue #11553 has been updated by Robert A. Heiler.


I assume that users will have to use --disable-dtrace to be on the safe side.

It is always a problem with binary yes/no enabling options since there is no middle ground in such a situation.

Ruby in general tries to enable whatever is available on the host system, if it can be found. I am not sure for
which programs this would not be the case but I assume that e. g. just about all the entries in ext/ subdirectory
work like that.


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

* 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/