openssl: Test 04-test_encoder_decoder.t fails on NonStop x86
This particular test works fine on 3.0.0 as released and with updates along the 3.0.0 branch. Where it fails is in master:
04-test_encoder_decoder.t .......... 1/?
../../util/wrap.pl ../../test/endecode_test -rsa ../../test/certs/ee-key.pem -pss ../../test/certs/ca-pss-key.pem -context -config ../../test/default.cnf -provider default => 139
This is a reopen of what was #16950 focusing on the real issue rather than the red-herring subject of that issue. I’m trying to figure out what changed between the two branches in a significant way and would like help tracking this down. Running directly and debugging using endecode_test appears to report a 0 completion code when the wrap.pl reports 139.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 128 (128 by maintainers)
Commits related to this issue
- Statically link the legacy provider to endecode_test We already statically link libcrypto to endecode_test even in a "shared" build. This can cause problems on some platforms with tests that load the... — committed to mattcaswell/openssl by mattcaswell 3 years ago
- Statically link the legacy provider to endecode_test We already statically link libcrypto to endecode_test even in a "shared" build. This can cause problems on some platforms with tests that load the... — committed to t8m/openssl by mattcaswell 3 years ago
- Statically link the legacy provider to endecode_test We already statically link libcrypto to endecode_test even in a "shared" build. This can cause problems on some platforms with tests that load the... — committed to openssl/openssl by mattcaswell 3 years ago
If I build normally and the delete the providers/legacy.so file then rerunning make shows me exactly what gets linked in as follows:
the final make shows me what goes into legacy.so. For me that is:
So we can see it is made up of providers/legacy-dso-legacyprov.o, providers/liblegacy.a and providers/libcommon.a.
The .a files are made up of lots of .o files. by rebuilding them we can see what they contain. If I delete the liblegacy.a file via
rm providers/liblegacy.aand then rebuild it withmake providers/liblegacy.aI get:Similarly for libcommon.a, delete it via
rm providers/libcommon.aand rebuild it withmake providers/libcommon.a:I don’t see init.o anywhere in that list for either liblegacy.a or libcommon.a. What about for you?