llnode
llnode copied to clipboard
nodejs
An lldb plugin for Node.js and V8, which enables inspection of JavaScript states for insights into Node.js processes and their core dumps.
The JSArrayBuffer has failed in node 18 in lldb versions 8, 11, 13, 14 but when re-ran they all pass. It's not clear what is causing it so we have...
**Describe the bug** llnode crashes when I run `v8 i -s `. **To reproduce** - Having this file `crash.js` ```js 'use strict'; throw new Error('this is uncaught'); ``` - Running...
As per https://github.com/nodejs/llnode/issues/287#issuecomment-1250090957 the core project used to detect breaking changes but this has been removed. This issue is to track conversation on how the llnode project can either re-establish...
## Context As `v8` API evolves and changes, we have to catch and handle breaking changes in the code. @kvakil suggest to use `debug_helper` in `llnode` [see proposal](https://github.com/nodejs/diagnostics/issues/571#issue-1306947839). > The...
This is a followup to https://github.com/nodejs/llnode/pull/389: * Updates the range of LLVM versions we check (from 20, which is next dev version, to 99) * Support downloading headers if the...
**Describe the bug** When initiating LLDB with LLNODE plugin, it fails **To reproduce** Steps to reproduce the behavior: 1. Initiated LLDB 2. Ran command 'plugin load /usr/local/lib/node_modules/llnode/llnode.dylib' 3. errored -...
Hi, I'm a total newbie regarding coredumps and the whole ecosystem around it, but I have managed to grab a coredump from a Node.js process running on an ARM-based AWS...
I have a core dump with lots of suspicious strings (64 random hex chars, if it rings a bell for anyone) and trying to figure out where they come from...
 why cannot load the core file and print nothing
