On Jun 7, 2008, at 3:38 PM, Adam Leventhal wrote: > I'm pleased to pass along news that the Mac OS X DTrace port has been > updated > in 10.5.3 to fix the issue that caused timer based probes not to fire > in the > presence of certain untraceable applications.
Thanks for the mention! In > > http://blogs.sun.com/ahl/entry/apple_updates_dtrace you write: >> "For the Apple folks: I'd argue that revealing the name of >> otherwise untraceable processes is no more transparent than what >> Activity Monitor provides — could I have that please?" Let's see what we can do. To cover this issue I've filed: <rdar://problem/5996285> DTrace: restore execname and pid lossage when P_LNOATTACH is asserted and: >> "Also, I'm not sure if this has always been true, but the ustack() >> action doesn't seem to work from the profile action" We encountered this some time ago. It's a very deep constraint on our ability to do copyin() on the interrupt stack. I'd like to fix this, but it will be challenging on a number of fronts. <rdar://problem/5369033> DTrace: ustack() action fails under profile and tick probes SCP -- Steve Peters [EMAIL PROTECTED] _______________________________________________ dtrace-discuss mailing list [email protected]
