-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve the documentation about post-mortem debugging #151
Comments
Cc @nodejs/post-mortem |
There was some work on this last year, but it did not make it into the node.js.org website: |
This would be great. I submitted a PR a few years ago to add top-level sections to the Node docs for both postmortem debugging and dynamic tracing: but it never made it in. I ended up moving the postmortem debugging parts to a usage guide for mdb_v8: Much of that is mdb_v8-specific, but much of it is general, and I would be happy for any of it to be used for general documentation if people find it to be useful. |
should this remain open? [ I am trying to chase dormant issues to closure ] |
This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made. |
I believe this falls under the bigger User Journeys and Documentations initiatives, so will close it for now. Feel free to reopen if you want to continue discussion though. |
It came out from diagnostics summit that we have very little documentation about post mortem debugging in our website.
This should include node-rerport, heapdumps, llnode, mdb etc.
The text was updated successfully, but these errors were encountered: