Catalogue existing tools for Node.js post-mortem analysis.

[hhellyer]

One of the first actions from the meeting was to catalogue existing post mortem tools and identify any capability gaps. Raising this issue as somewhere to gather that information.

Tool	Description	URL
node-inspector	Standalone version of the Chrome dev tools	https://www.npmjs.com/package/node-inspector
heapdump	Trigger v8 heap dumps from javascript	https://www.npmjs.com/package/heapdump
mdb_v8	JavaScript and C inspection for core files and live processes. Also contains a general description of postmortem debugging and tips for doing so.	https://github.com/joyent/mdb_v8

[davepacheco]

Tool	Description	URL
mdb_v8	JavaScript and C inspection for core files and live processes. Also contains a general description of postmortem debugging and tips for doing so.	https://github.com/joyent/mdb_v8

[seabaylea]

Adding IDDE to the list:

Tool	Description	URL
IDDE	Cross-platform JavaScript, Java and C inspection for core files. Runs in an Eclipse IDE but also provides client/server support	https://www.ibm.com/developerworks/java/jdk/tools/idde/

Does anyone have any objections to me starting a separate issues for tools/modules/approaches for generating "post-mortem" data, and keep this for tools that consume/analyze the data?

[lucamaraschi]

Shouldn't we list also the compatibilities and key features of each one of the available tools/technologies?It would make easier to define a list of requirements and contextualise them into real case scenarios.
Does it make sense?

[davepacheco]

@lucamaraschi I think that's covered by #7, but it wouldn't hurt to include that information about each of the tools as well.

[lucamaraschi]

@davepacheco I think we should actually match use cases -> users -> tools and generate a requirements list. I am not a believer of "one size fits all" software ;-)
If this makes sense, shouldn't we create just one issue that we can start to document?
I would like to help here as we are using heavily post-mortem in development and production.

[richardlau]

Closing due to inactivity. If this work still needs to be tracked, please open a new issue over in https://github.com/nodejs/diagnostics.