On Fri, Feb 20, 2015 at 9:04 AM, Andy Wingo <[email protected]> wrote:
> I got stuck a week ago with a really strange crash that I couldn't > understand. Maybe this rarely happens to you all :) To me it happens > sometimes but my experience with GDB has always been frustrating. With > JITted code you can't even get a backtrace that makes any sense. We were frustrated with this for a long time as well. Our solution was to build rich support into MDB for stack traces as well as object printing. Here's some draft documentation: https://github.com/davepacheco/node/blob/64cbc820cfab759ec3c9d3a66356bec6886af22e/doc/api/postmortem-debugging.markdown While it's documented for Node, there's almost no dependency on Node itself. It should work on any V8-embedded program that was built with v8_postmortem_support=true. That flag is cheap enough for production: it just includes a small amount of metadata in the binary that the debugger reads. (We designed it so that other debuggers could read it too.) There's no runtime overhead at all, so it's suitable for production use. MDB is limited to illumos-based systems, but it can grok core files from GNU/Linux systems as well. Hope this helps, Dave -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
