https://sourceware.org/bugzilla/show_bug.cgi?id=28138
--- Comment #7 from Sergei Trofimovich <slyfox at inbox dot ru> ---
I think I got closer to the problem: it's a bad error handling related to
-EMFILE (too many open files). nodejs is probably just very close to open file
limit (default 1023):
$ strace -f -olog -etrace=execve,openat ./mk.bash
...
684205
execve("/usr/lib/gcc/x86_64-pc-linux-gnu/12.0.0/../../../../x86_64-pc-linux-gnu/bin/ld",
...
684205 openat(AT_FDCWD,
"/tmp/portage/net-libs/nodejs-16.5.0/work/node-v16.5.0/out/Release/obj.target/v8_compiler/deps/v8/src/compiler/simd-scalar-lowering.o",
O_RDONLY) = 10
23
684205 openat(AT_FDCWD,
"/tmp/portage/net-libs/nodejs-16.5.0/work/node-v16.5.0/out/Release/obj.target/v8_compiler/deps/v8/src/compiler/simd-scalar-lowering.o",
O_RDONLY) = 89
8
684205 openat(AT_FDCWD,
"/tmp/portage/net-libs/nodejs-16.5.0/work/node-v16.5.0/out/Release/obj.target/v8_compiler/deps/v8/src/compiler/backend/instruction-scheduler.o",
O_RDO
NLY) = -1 EMFILE (Too many open files)
684205 +++ exited with 1 +++
Don't yet know why EMFILE handling did not kick in.
--
You are receiving this mail because:
You are on the CC list for the bug.
