DTrace is a comprehensive dynamic tracing framework created by Sun Microsystems for troubleshooting kernel and application problems on production systems in real time. Originally developed for Solaris, it has since been released to open source community in 2004 and has been ported to several other Unix systems.
Apple ported DTrace for OS X Leopard, including a GUI called Instruments and made it co-exist with the existing legacy stack of performance troubleshooting toolkits.
We are going to tame this beast to help us hunt down and eliminate all sorts of application and system-wide troubles when doing development of iOS and OS X apps.
$ open "$SEE_THE_FACEBOOK_GROUP_AT http://facebook.com/groups/iosdevorgua"
- DTrace introduction
- DTrace use cases in software engineering industry
session two (October 3, https://www.facebook.com/events/387735561298626/)
- DTrace script language crash course
- OSX vs canonical (Solaris) implementations overview
- http://kirillov.im/dtrace_begin.pdf
- http://learningsolaris.com/docs/dtrace_course.2005.8.18.pdf
- http://www.brendangregg.com/DTrace/dtrace_topics_intro.pdf
session three (October 17, https://www.facebook.com/events/448235101889087/)
- Establishing DTrace probes on a running process in OSX, Objective-C provider
- Combining DTrace techniques with classic sequential ptrace debugging (GDB)
- Establishing DTrace probes during process bootstrap stage
- Tracing application code activity
- Tracing library code activity
- DTrace and the legacy OSX performance monitoring stack
- Monitoring threaded activity
- Correlating process activity to kernel services activity
- Performance monitoring
- DTrace for dynamic languages and runtimes
- http://dtrace.org/blogs/brendan/2011/10/10/top-10-dtrace-scripts-for-mac-os-x/
- http://dtrace.org/blogs/brendan/2012/08/09/10-performance-wins/
- http://docs.oracle.com/cd/E19963-01/html/821-1601/compile-19263.html
- http://kirillov.im/darwin_breakdown.pdf
- http://kirillov.im/darkproger_introspecting_mach.pdf
- http://kirillov.im/aact/
