Apple Quietly Fixes DTrace 144
In January we discussed a blog entry revealing that Apple had "crippled" its DTrace port. As the author notes in a followup post, to say that DTrace had been "crippled" was at least overstated: "Unfortunately, most reactions seized on a headline paraphrasing a line of the post — albeit with the critical negation omitted." In an updated entry, the poster notes that Apple has made good (so we have too): "One issue was that timer based probes wouldn't fire if certain applications were actively executing (e.g. iTunes). This was evident both by counting periodic probe firings, and by the absence of certain applications when profiling. The good news is that Apple has (quietly) fixed the problem in Mac OS X 10.5.3."
Took them long enough (Score:2, Insightful)
This sort of issue wouldn't survive for a week on Linux.
Re:Took them long enough (Score:4, Insightful)
Re:22 January - 11 June (Score:1, Insightful)
Quietly, quietly (Score:5, Insightful)
Re:Took them long enough (Score:5, Insightful)
Re:Quietly, quietly (Score:5, Insightful)
Re:Mac's Suck (Score:3, Insightful)
Seriously, unless you are developing Cocoa(or Carbon) apps, there is very little reason to use XCode. There are better free software programs out there for writing c++ code, not to mention you could always just call good ol' gcc on the command line....
Re:22 January - 11 June (Score:1, Insightful)
Re:Mac's Suck (Score:4, Insightful)
$ make
Good news doesn't sell (Score:3, Insightful)