Closed aputrevu closed 1 year ago
Hi @aputrevu Would you mind confirming node.js version, operating system and CPU architecture the crash happened on as well as the node.js version, Operating System and cpu architecture that you are debugging on Thanks
@No9 Our node.js app runs inside a docker container on our production systems.
Server configuration: CPU Arch: x86-64 Node.js version: 10.24.1 docker container OS: Debian GNU/Linux 10 (buster) docker container base image: keymetrics/pm2:10-buster
My laptop configuration on which I'm debugging: CPU: Intel core i7 node.js version: 10.24.1 OS: MacOS Catalina - 10.15.7
I was able to install llnode on my laptop but the "v8 xxx" commands didn't show any useful information. So, I installed llnode inside a docker container with the same base image as our app(keymetrics/pm2:10-buster). some of the "v8 xxx" commands are working, but "v8 findjsobjects" command is failing.
Which version of llnode are you using? Latest v4.0.0 does not support node 10 as that was put into end of life over a year ago 2021-04-30 However v3.3.0 may work but we can't provide bug fixes. Also note LLVM-7 isn't in our test system - it should work but isn't validated.
@No9 I installed llnode v3.3.0 + lldb v8 in Ubuntu 18.04 VM, and the 'v8 findjsobjects' command still failed with a similar stacktrace as above. Since llnode v3 is not supported anymore, I'll look for other ways to debug my app.
Thanks for the help 🙂
What does the below stacktrace mean? Does it mean my core dump file is corrupt?