-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
node v4.2.2 app finalize abruptly signaling SIGILL - Illegal instruction #4121
Comments
/cc @nodejs/crypto |
I cannot reproduce the error neither on node v0.12 xor v0.10 but on v4.2.2, v5.0.0, v5.1.0 |
@diegosanchez what is the platform you are running this on? What CPU features does it support? Could you please gist your |
|
Does |
@diegosanchez are you running this in some sort of virtualized environment like VirtualBox or something like this? Or is it running on a bare metal? |
@bnoordhuis I think it is BMI2 that is absent, that causes this. |
It is strange that OpenSSL did not pick up AVX+SSSE3, though |
Ah, it is AMD... |
@indutny Not it isn't a virtualized env. |
@diegosanchez so far it looks like OpenSSL assembly code is not supported by your CPU. To work it should either:
From the cpuinfo that you have posted - it looks like your CPU does not support either of this modes. (@bnoordhuis please correct me if I'm off with this statement). The simplest fix would be to use |
It seems that it So far, it is a good workaround. I have narrowed down the issue a bit more here Project where I reproduce the error |
Here is documentation. In a nutshell, openssl tries (and apparently fails in your case) to auto-detect the CPU's capabilities. |
It looks like this was fixed upstream recently? |
@bnoordhuis @indutny awesome thanks. |
Yes, it was helpful, thanks. The ud2 and the stack trace told me where to go looking. |
@diegosanchez Can you try the master branch now and check if the upgrade to OpenSSL 1.0.2e helped you at all? |
Sure
|
@mscdex Works fine! with v6.0.0-pre
whereas with v4.2.2
|
Awesome! 👍 If you want to stick to LTS, the OpenSSL upgrade should be in v4.2.3 now too. |
Having built node v4.2.2 I get a segmentation fault.
The binary shasum is:
6ec12774e7b80f3bc391ed0ebdc6890d9660907f v4.2.2/bin/node
.Because of this I recompile de binary using the command
./configure --prefix=<path> --gdb --debug
in order to perform a backtrace.Bellow the backtrace:
SO Information
I don't want to overwhelm you with immaterial information so that I'm eager to supply requested information.
The text was updated successfully, but these errors were encountered: