Repository navigation
Segmentation fault on riscv64 starting with v24.22.0 due to missing v8 commit #67066
Description
Version
v24.22.1
Platform
Linux k3 7.3.0+ #1 SMP PREEMPT Mon Oct 19 11:14:35 UTC 2026 riscv64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
Just start nodejs with ./node
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
$ ./node
Welcome to Node.js v24.21.0.
Type ".help" for more information.
>
What do you see instead?
$ ./node
Segmentation fault ./node
This is the corresponding GDB output:
$ gdb ./node
GNU gdb (Debian 18.1-3) 18.1
Copyright (C) 2026 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "riscv64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
+------------------------------------------------------------------------------+
| Find the GDB manual online at: |
| http://www.gnu.org/software/gdb/documentation/. |
| For help, type "help". |
| Type "apropos word" to search for commands related to "word". |
+------------------------------------------------------------------------------+
Reading symbols from ./node...
(No debugging symbols found in ./node)
(gdb) run
Starting program: /home/aurel32/nodejs/node/node
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/riscv64-linux-gnu/libthread_db.so.1".
[New Thread 0x3ff0d05f80 (LWP 1032058) (id 2)]
[New Thread 0x3febffef80 (LWP 1032059) (id 3)]
[New Thread 0x3feb7fdf80 (LWP 1032060) (id 4)]
[New Thread 0x3feaffcf80 (LWP 1032061) (id 5)]
[New Thread 0x3fea7fbf80 (LWP 1032062) (id 6)]
[New Thread 0x3ff0479f80 (LWP 1032063) (id 7)]
Thread 1 "MainThread" received signal SIGSEGV, Segmentation fault.
0x0000003ff52df1e6 in v8::internal::Runtime_InstallBaselineCode(int, unsigned long*, v8::internal::Isolate*) () from /home/aurel32/nodejs/node/out/Release/libnode.so.137
(gdb) bt
#0 0x0000003ff52df1e6 in v8::internal::Runtime_InstallBaselineCode(int, unsigned long*, v8::internal::Isolate*) () from /home/aurel32/nodejs/node/out/Release/libnode.so.137
#1 0x0000003ff4915be4 in Builtins_CEntry_Return1_ArgvOnStack_NoBuiltinExit () from /home/aurel32/nodejs/node/out/Release/libnode.so.137
Backtrace stopped: frame did not save the PC
(gdb)
Additional information
The problem has been introduced with commit fb0d0ca.
It happens that the following v8 commit is missing now that the above commit has been backported and also needs to be backported: https://chromium.googlesource.com/v8/v8.git/+/ec2f506f97dfbb5fa19e4fe9103965a3c94690af
Activity