Re: kern/50700: dtrace module(s) cannot be loaded

[Paul Goyette <paul%whooppee.com@localhost>]

On Sun, 24 Jan 2016, Christos Zoulas wrote:

> I don't understand; do you mean that a kernel compiled with KDTRACE_HOOKS
> fails to load the dtrace module? Because it does not seem to be the case
> here. As far as defining KDTRACE_HOOKS by default, I thought this had been
> done. OTOH I don't think that removing the option completely is needed...

No.

If everything is built-in (ie, KDTRACE_HOOKS is defined), there is no 
problem.  the module doesn't need to "load" since it is already 
built-in.

The problem occurs when the module is NOT built-in, ie, KDTRACE_HOOKS is 
not defined.

In this case, the modules that are built are not "complete".  They don't 
contain critical trap/vector "support-code", and they don't contain the 
various "probes".  The lack of support-code prevents them from even 
being loaded (due to the error messages reported in the PR).

Even if the support-code issue were resovled (by including it in all 
kernels, unconditionally), the load-at-run-time modules would be of no 
value, since none of the "probes" would exist.


+------------------+--------------------------+------------------------+
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:      |
| (Retired)        | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com   |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
+------------------+--------------------------+------------------------+