-
Notifications
You must be signed in to change notification settings - Fork 32
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
node v16.13: infinite loop in node_mksnapshot #516
Comments
I run
encounter error:
|
Did you reuse an old build root? Try adding --clean. |
Thanks And when i want to debug it by gdb
Is this virtual machine don't support gdb? |
Looks like it is caused by nested VM. gdb uses ptrace for sub-process operations. ptrace is a feature of kernel IIRC. |
Qemu linux-user emulation does not support ptrace. You need to use system emulation or real hardware if you want to run gdb. I usually export the build root via nfs, so that I can mount it on my hifive board. Or you can use "osc build --vm-type qemu native riscv64" to start qemu in system emulation. |
Hi @andreas-schwab
It should be |
May be you should add patch : https://chromium-review.googlesource.com/c/v8/v8/+/3093009 |
Importing the whole patch causes node_mksnapshot to crash. |
And the s/eq/ne/ change alone has the same problem. |
i will try it again |
0001-fix.zip |
Paste the patch as a github gist may better. Thanks. I had updated. |
Thanks a lot, this patch fixes the issue. |
While building node v16.13 (using v8 9.4.146.19) the following command runs into an infinite loop:
LD_LIBRARY_PATH=/home/abuild/rpmbuild/BUILD/node-v16.13.0/out/Release/lib.host:/home/abuild/rpmbuild/BUILD/node-v16.13.0/out/Release/lib.target:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH; cd ../.; mkdir -p /home/abuild/rpmbuild/BUILD/node-v16.13.0/out/Release/obj/gen; "/home/abuild/rpmbuild/BUILD/node-v16.13.0/out/Release/node_mksnapshot" "/home/abuild/rpmbuild/BUILD/node-v16.13.0/out/Release/obj/gen/node_snapshot.cc"
https://build.opensuse.org/package/live_build_log/openSUSE:Factory:RISCV/nodejs16/standard/riscv64
The text was updated successfully, but these errors were encountered: