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 }}
This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
While building against a shared openssl 1.0.1h (on gentoo), this test fails:
(gdb) run test/simple/test-crypto-dh-odd-key.js
Starting program: /home/jbergstroem/node/out/Debug/node test/simple/test-crypto-dh-odd-key.js
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7ffff5f68700 (LWP 5858)]
[New Thread 0x7ffff7fe5700 (LWP 5859)]
[New Thread 0x7ffff7fd4700 (LWP 5860)]
[New Thread 0x7ffff7fc3700 (LWP 5861)]
Program received signal SIGSEGV, Segmentation fault.
bn_mul_mont () at x86_64-mont.s:61
61 x86_64-mont.s: No such file or directory.
The backtrace doesn't really help here since I guess we're heading into assembly land. I'm not sure whether the openssl provided by gentoo is doing "something wrong" here, but as long as there's a provided --shared-openssl when configuring the build, I'd at least want to see tests passing.
..if I build with the bundled openssl, it works just fine.
Suggestions on how to proceed?
(On the other hand -- while building with bundled openssl I had to add -ldl to linker args, otherwise it bailed with libopenssl.a(dso_dlfcn.o): undefined reference to symbol 'dlclose@@GLIBC_2.2.5') when doing a debug build.
The text was updated successfully, but these errors were encountered:
This is expected, the node.js is using patched version of openssl. The patch itself is in upstream, but is far from being included in a next release and updated on all OSes. Sorry, not much you could do, except probabaly building OpenSSL yourself.
While building against a shared openssl 1.0.1h (on gentoo), this test fails:
The backtrace doesn't really help here since I guess we're heading into assembly land. I'm not sure whether the openssl provided by gentoo is doing "something wrong" here, but as long as there's a provided
--shared-openssl
when configuring the build, I'd at least want to see tests passing...if I build with the bundled openssl, it works just fine.
Suggestions on how to proceed?
(On the other hand -- while building with bundled openssl I had to add
-ldl
to linker args, otherwise it bailed withlibopenssl.a(dso_dlfcn.o): undefined reference to symbol 'dlclose@@GLIBC_2.2.5'
) when doing a debug build.The text was updated successfully, but these errors were encountered: