And It All Went Horribly Wrong: Debugging Production ... - Joyent

More documents

Recommendations

Info

DTrace in other environments • This technique has been generalized by Chris <strong>And</strong>rews in his node-dtrace-provider npm module: https://github.com/chrisa/node-dtrace-provider • Chris has also done this for Ruby (ruby-dtrace) and Perl (Devel::DTrace::Provider) • Neither technique addresses the problem of associating in-kernel events with their user-level (dynamic) context Thursday, November 17, 2011
Extending DTrace into the VMs • To allow DTrace to meaningfully understand VM state from probe context, we introduced the notion of a helper — programmatic logic that is attached to the VM itself • For the stack helper, a VM defines — in D — the logic to get from frame pointers to a string that names the frame • Must run in the kernel, in probe context — brutally hard to program • This was done for Java initially, but has also been done for Python by John Levon and node.js by Dave Pacheco Thursday, November 17, 2011
Page 1 and 2: And It All Went Horribly Wrong: Deb
Page 3 and 4: In the beginning... Sir Maurice Wil
Page 5 and 6: Debugging through the ages • As s
Page 7 and 8: Do we still need to care about fail
Page 9 and 10: Wait, it gets worse • This assume
Page 11 and 12: Debugging in the modern era • Fai
Page 13 and 14: Postmortem advantages • There is
Page 15 and 16: Postmortem challenges • Must have
Page 17 and 18: Postmortem debugging • Postmortem
Page 19 and 20: Postmortem debugging: node.js • D
Page 21 and 22: Debugging transient component failu
Page 23 and 24: DTrace • Facility for dynamic ins
Page 25: DTrace for node.js • Given the na
Page 29: Thank you! • Dave Pacheco (@dapsa

And It All Went Horribly Wrong: Debugging Production ... - Joyent

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?