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
[help] Using llnode with Deno #288
Comments
This might be due to an unsupported V8 version. Which V8 version is your deno using? |
@mmarchini we're currently running V8 7.7.200 |
That version is not yet supported. Take a look at the issues in this repo labeled V8 Changes... you'll see llnode is increasingly drifting behind. |
@cjihrig duh! Thanks for the tip, my bad. Closing this issue for now. |
Hopefully in the future we can leverage the new postmortem API which landed in V8 a few days ago (https://chromium-review.googlesource.com/c/v8/v8/+/1717090), but right now llnode is only work to V8 versions up to 6.8. |
I'm trying to use
llnode
to debug deno.I do realize that's not the scope of this lib, but I hope you guys might be able to help.
Unfortunately backtrace using
v8 bt
gives exactly same output asbacktrace
, neitherv8 findjsobjects
norv8 source list
work.Here's my excerpt from my building config:
Here's output from
llnode
:I assume frame #9 is a JS frame, but I couldn't find a way to actually annotate it using
llnode
.I suspect the problem is with build config, any tips would be highly appreciated 🙏
The text was updated successfully, but these errors were encountered: