You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
node --jitless segfault on mipsel or mips64el #33703
Is it possible for you to obtain a backtrace (with bt) and the output of disassembly, info registers and info proc mappings? That probably contains some clues.
Thanks. Can you report this to V8? I don't think this is a bug we can fix.
V8's regexp interpreter is trying to load from address 0xfff86c7ca8 but that address isn't mapped to anything. My hunch is a calling convention mismatch between code generated by gcc and V8.
The binary is compiled on the machine it's run on? If not, you should run configure with ./configure <options> -- -Dv8_host_byteorder=little if they have different endianness.
Activity
bnoordhuis commentedon Jun 4, 2020
Is it possible for you to obtain a backtrace (with
bt) and the output ofdisassembly,info registersandinfo proc mappings? That probably contains some clues.kapouer commentedon Jun 4, 2020
Yes, as soon as it's rebuilt, in a day or two.
bnoordhuis commentedon Jun 9, 2020
Ping @kapouer.
kapouer commentedon Jun 9, 2020
I'm doomed by the build servers... https://buildd.debian.org/status/package.php?p=nodejs&suite=experimental has been waiting for three days. It should eventually run.
bnoordhuis commentedon Jun 9, 2020
No problem, thanks for the update.
kapouer commentedon Jun 13, 2020
On mips64el, nodejs 12.18.0
Backtrace
bnoordhuis commentedon Jun 16, 2020
Thanks. Can you report this to V8? I don't think this is a bug we can fix.
V8's regexp interpreter is trying to load from address 0xfff86c7ca8 but that address isn't mapped to anything. My hunch is a calling convention mismatch between code generated by gcc and V8.
The binary is compiled on the machine it's run on? If not, you should run configure with
./configure <options> -- -Dv8_host_byteorder=littleif they have different endianness.build: configure byte order for mips targets
kapouer commentedon Jun 16, 2020
https://bugs.chromium.org/p/v8/issues/detail?id=10618
tomtastic commentedon Jun 16, 2020
"Permission denied." Is this not public ?
schuay commentedon Jun 16, 2020
It is now.
build: configure byte order for mips targets
build: configure byte order for mips targets
build: configure byte order for mips targets
zjiaz commentedon Jul 3, 2020
Hi, this bug is indeed in v8, and it's fixed in v8 by: [mips] Use t9 as the function call register.
bnoordhuis commentedon Jul 3, 2020
v8/v8@7889803 doesn't apply cleanly to deps/v8 in node master. Anyone want to take a stab at back-porting it?
codebytere commentedon Jul 3, 2020
@bnoordhuis looks like it's already there:
node/deps/v8/src/codegen/mips64/macro-assembler-mips64.cc
Lines 4207 to 4211 in 1d6adf7
I think it should be in 14 as well given that we just updated v8 there so this may just need to go to 12?
build: configure byte order for mips targets
build: configure byte order for mips targets
build: configure byte order for mips targets
deps: V8: cherry-pick 7889803e82d3
deps: V8: cherry-pick 7889803e82d3