Now, most likely you will be running on Linux. In order to use mdb, you will need a supported OS. Does nothing to help debug crashes that originate from native code faults (SIGSEGV, etc)Ĥ) Joyent: Debugging Production Systems - talk by Bryan Cantrill on the tools and techniques he recommends (thx crickeys).Ģ017 update: Now you can use solution (llnode, based on lldb rather than mdb). While it makes for GREAT background reading, the article doesn't have many concrete tools and techniques in it.ģ) node-panic - A pure-JS tool for dumping state in the event of an assert-failure type crash.
Sadly, as far as I can tell, the source of that plugin was never released (nor any binary form).Ģ) Postmortem Debugging in Dynamic Environments - ACM Queue article also written by Dave Patheco (linked from the blog post).
It's a module I cooked up to get a native-code stack trace in the event of a hard-crash with a signal - eg deref of NULL leading to SIGSEGVįor investigating memory / allocation issues, here's some of the data I've collected thus far:ġ) Blog post by Dave Patheco - the author talks about using a plugin to MDB for getting JS stacks and such. For investigating crashes, I've found node-segfault-handler to be invaluable.
0 kommentar(er)
