-
Notifications
You must be signed in to change notification settings - Fork 100
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
Consistent crashes with v8 findrefs -s
#429
Comments
(Originally submitted here.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is difficult due to a consistent crash.
I first tried a
v8 findrefs 0x...
for these strings, and that returns nothing. I then triedv8 findrefs -s <str>
, and that crashes consistently. This is with multiple core dumps, and many strings. All failed with the-s
without any exceptions.See the crash log below.
Local environment (please complete the following information):
Version of llnode: 4.0.0
OS Info: multiple Ubuntu-based environments --- Ubuntu w/ WSL2, Ubuntu in a docker container, and the same on AlmaLinux
lldb Version: 14.0.0 (installed via
apt install lldb-14 liblldb-14-dev
)Obtained using
lldb --version
Version of node.js [e.g. 16.17.0]
Obtained using
node --version
Server where the core was dumped (please complete the following information):
OS Info: [e.g. Linux ub 5.15.0-46-generic Changelog #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux]
Obtained using
uname -a
or on Windowswmic os get OsArchitecture && wmic os get name
lldb Version [e.g. 14.0.6]
Version of node.js: a few different versions, including 14.19.0, and 19.6.1
Additional context
The text was updated successfully, but these errors were encountered: