llnode - Current Status

[No9]

As per Diagnostics Meeting 2022-07-26
This issue tracks work on llnode

Discussion

Support Matrix - nodejs/llnode#405

Work In Progress

• User Journeys for llnode - Document User Journey llnode#401 @tony-go
• Discussion on reducing features in tool to make it more maintainable is commencing.
  Supported Features Matrix llnode#405
  This will be followed up in later calls.
• Coordinate the announcement of support reestablished in the tool tier list https://github.com/nodejs/node/blob/main/doc/contributing/diagnostic-tooling-support-tiers.md
• Next call 2022-08-23

Backlog

• Medium term debug_helper is being evaluated as a possible replacement for some llnode capabilities
  Discussion around how debug_helper is integrated and additional requirements will be documented as discussion continues @kvakil to open issue as work starts.

Work Completed

• Establish core dump tools meeting to discuss roadmap/strategy/keyissues - core dump collaboration call llnode#402 Moved to main diagnostics
• CI is now back to green https://github.com/nodejs/llnode/actions/runs/2721848039
• 2FA Enabled on npm for publishing
• Support for later versions of llvm to 14 - https://github.com/nodejs/llnode/pull/389/commits @No9
• V8 Changes to support node v16-v18 - Not showing details of JS frames on node v16.14.0 llnode#399 Initial patch submitted this week and scope of further work needs to be defined. @kvakil

[RafaelGSS]

Meeting scheduled for next DWG (nodejs/llnode#402)

[github-actions]

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.