-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
build 12.13.0 on mips64el segfault around mksnapshot #30304
Comments
Is it possible to obtain a stack trace or core dump of the segfault?
mksnapshot tries to reserve (not commit) 2 GB of memory. That should normally succeed on a 64 bits system because there's plenty of address space. The reservation is so that runtime generated machine code can use near calls. |
@kapouer I'm closing this for lack of follow-up but feel free to reopen if you have more information. |
I just ran into this same problem building 14.5 on Big Endian PowerPC. I have a stack trace and core dump, but the lack of debug symbols admittedly might be less useful. The last function on the call stack is what didn't resolve, and it seems to in "Invoke".
Let me know if the ~50MB core might be useful to you. |
Hi @KungFuJesus the problem you see is probably not related to this issue. |
Applying the patch now and trying it out. It looks like you may be right but it takes a while to get there on a Quad G5. For the record I'm not expecting node to work after this, there are holes that require POWER5 for the JIT to work that I'm aware of, but this will at least get me further. |
Version: 12.13.0
Platform: GNU/Linux
Subsystem: build
Now that 10.17.0 builds just fine, i gave a shot at 12.13.0 ;)
full log here
On mipsel, a different failure may indicate build is using too much memory at some point.
full log here
The text was updated successfully, but these errors were encountered: