http://www.noodlesoft.com/blog/2007/02/07/debugging-lesson-take-a-look-back-to-go-forward/ On Mac OS X programming Tue, 02 Dec 2008 12:08:38 +0000 http://wordpress.org/?v=2.6.3 http://www.noodlesoft.com/blog/2007/02/07/debugging-lesson-take-a-look-back-to-go-forward/#comment-801 T. Moeller Thu, 15 Mar 2007 11:27:38 +0000 http://www.noodlesoft.com/blog/2007/02/07/debugging-lesson-take-a-look-back-to-go-forward/#comment-801 ... or just use Leopard's dtrace ... http://www.theregister.co.uk/2004/07/08/dtrace_user_take http://prefetch.net/articles/dtracecookbook.html http://prefetch.net/articles/solaris.dtracetopten.html … or just use Leopard’s dtrace …
http://www.theregister.co.uk/2004/07/08/dtrace_user_take
http://prefetch.net/articles/dtracecookbook.html
http://prefetch.net/articles/solaris.dtracetopten.html

]]> http://www.noodlesoft.com/blog/2007/02/07/debugging-lesson-take-a-look-back-to-go-forward/#comment-619 Michael Thu, 08 Feb 2007 18:13:35 +0000 http://www.noodlesoft.com/blog/2007/02/07/debugging-lesson-take-a-look-back-to-go-forward/#comment-619 Or you can just use a back in time debugger. All you have to do is collect a trace log of the history from within the debugger or externally, load that log, and step backwards to figure out what happened. No manual logging No reproducing problems No more headaches like the ones you describe. Check it out: http://www.ghs.com/products/timemachine.html Or you can just use a back in time debugger. All you have to do is collect a trace log of the history from within the debugger or externally, load that log, and step backwards to figure out what happened.
No manual logging
No reproducing problems
No more headaches like the ones you describe.
Check it out: http://www.ghs.com/products/timemachine.html

]]>