-
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
[Question] examining coredumps on Mac x86 #432
Comments
alxgrk
changed the title
[Question] examine coredumps from ARM machine on x86
[Question] examining coredumps on Mac x86
Nov 14, 2023
Update: turned out that this has nothing to do with the system architecture. I was able to examine the coredump on another x86 EC2 instance. Question remains if anyone has an idea what goes wrong on Mac. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 EC2 instance. I now wanted to analyse it on my Mac running on x86 and executed
v8 nodeinfo
- telling meNo process objects found.
.I checked for the node version to be the same on my machine and the EC2 instance (v16.20.0) and also enabled DEBUG logging, yielding these lines:
My question is: could this be related to not having the same CPU architecture?
lldb -v
prints:Best,
Alex
The text was updated successfully, but these errors were encountered: