DTrace firing throws

[karlbohlmark]

I assume you know what you're doing, so you can consider this pull request more as an illustrated question. Currently, I can not see how the dtrace firing can actually work with dtrace-provider 0.2.4 on a platform that does not support dtrace.

Anyway, I'm using this project on linux with this patch applied and since it follows the syntax in dtrace-provider's readme I don't see a reason that it should break other platforms.

Maybe you actually want to prevent it from working on a non dtrace enabled platform?

[mcavage]

Hi,

(1) It's amazing (to me, anyway) that anybody has bothered to dig into this repo ;) - it's downright hostile in terms of docs, samples, etc.

(2) Well, honestly I've never tried this repo on a Linux install, so you're probably right that it doesn't work - I did do that particular syntax on purpose, as that prevents node-dtrace-provider from doing an O(n) scan. I had done some of the work a long time ago to make node-dtrace "stub out" on Linux - I didn't realize this portion wasn't stubbed. I think the right answer is to make it stub out since it's already handling this, and then just bump the dependency version.

m

[mihai-chiorean]

same issue....

[pfmooney]

Fixed in 6018c83.

Thanks