[erlang-questions] FreeBSD dtrace-enabled builds

Dave Cottlehuber dch@REDACTED
Sat Jan 31 10:02:45 CET 2015


On FreeBSD 10.1R amd64, after building a modified lang/erlang port, the following alarming warning is displayed. This is the same in the newer lang/erlang-runtime17 flavour as well BTW.

WARNING: number of probes fixed does not match the number of defined probes (1001 != 1088, respectively)
WARNING: some probes might not fire or your program might crash
Erlang/OTP 17 [erts-6.3] [source] [64-bit] [smp:8:8] [async-threads:64] [hipe] [kernel-poll:true] [dtrace]

Eshell V6.3  (abort with ^G)

No doubt this is in reference the forthcoming zombie apocalypse…

How serious is this — does anybody have practical experience to relate?

Any idea on what the problem might be or what I might need to do to fix it?

Assuming this is resolved, what is the practical impact of using a dtrace-enabled build in production? Is there likely to be a significant performance hit, or is this even foolish from a stability perspective? Handwavey answers are entirely appropriate here.

A+, Dave
— sent from my Couch

More information about the erlang-questions mailing list