News for hackers. Stuff that matters.
Re:Oracle's port of DTrace to Linux is not DTrace by bcantrill on Monday October 10, 2011 @07:07PM (#3096278)
You're missing an essential bit here: the use of DTrace damaged the system. This violates the Hippocratic promise of DTrace: to do no harm.[1] This transgression should not be written off as a youthful indiscretion of the port, for it reflects that those undertaking it do not understand this most essential of constraints. And to be honest, I'm personally astounded that a port with such modest ambition could be so busted: if you can't get the syscall provider right, FBT, SDT, USDT and so on will remain firmly out of reach.

[1] http://dtrace.org/blogs/bmc/2005/07/19/dtrace-safety/

Re:Oracle's port of DTrace to Linux is not DTrace by apaprocki on Monday October 10, 2011 @08:10PM (#3096469)
There's a difference between an implementation which clearly violates the intended design and a tricky bug that is breaking something. Without knowing exactly why it is broken, it just seems to be a missed first opportunity for them to wow everyone. I'd be more concerned if it stayed broken more than a short period of time now that it has been publicly pointed out to them. It would be helpful if the Oracle guys posted the most efficient way for users to funnel them bug reports.
Re:Oracle's port of DTrace to Linux is not DTrace by adamleventhal on Monday October 10, 2011 @08:31PM (#3096527)
... or if they posted the source code...