You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wouldn't it be nice if llnode worked out of the box with node 8? Indeed it would but it won't happen without some even-toed ungulate clipping1. Here is what needs to be done:
update tools/gen-postmortem-metadata.py in upstream V8
back-port changes to nodejs/node
update llnode to support new object layouts
Bonus points if llnode is taught to print something sensible for WASM and Ignition stack frames/code objects/etc.
Activity
bnoordhuis commentedon Apr 25, 2017
Related V8 issue: No build bots build debug-support.cc
bnoordhuis commentedon Apr 26, 2017
V8 changes: https://codereview.chromium.org/2842843004/
deps: cherry-pick bfae9db from upstream v8
deps: cherry-pick bfae9db from upstream v8
deps: cherry-pick bfae9db from upstream v8
deps: cherry-pick bfae9db from upstream v8
3 remaining items
deps: cherry-pick bfae9db from upstream v8
deps: cherry-pick bfae9db from upstream v8
deps: cherry-pick bfae9db from upstream v8
deps: cherry-pick bfae9db from upstream v8
deps: cherry-pick bfae9db from upstream v8
deps: cherry-pick bfae9db from upstream v8
deps: cherry-pick bfae9db from upstream v8