On Tue, 31 Mar 2020, Christian Walther wrote: > Any news on this? I am seeing the same crash (same gdb backtrace) with > the nodejs 10.15.2~dfsg-2 and npm 5.8.0+ds6-4 provided by Debian 10 i386 > (on a virtual machine) while using "npm install" on an internal package.
We also have experienced this segfault in Kali while trying to build a package on . I'm wondering why this bug was not forwarded upstream? I know that linux 32 bit is no longer officially supported by upstream, but are they rejecting bug reports? It seems that "unofficial builds" are still made and thus bug reports and fixes are likely accepted, though not handled with any priority I guess. That would still give more visibility to this issue. https://unofficial-builds.nodejs.org/ I'm also wondering why i386 and armel are treated differently, given that both are unsupported upstream (in Debian, i386 is still built, but armel is no longer built). Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hert...@debian.org> ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS