You are not logged in.

#1 2025-06-25 13:08:57

lquidfire
Member
From: South Africa
Registered: 2017-07-26
Posts: 77

Test for AWS-LC fails - How to debug

Hi!

I am trying to build AWS-LC.

I am using the following incantations, based on their documentation, as well as the Archlinux wiki for Cmake PKGBUILDs:

$ cmake -GNinja -B build \
            -DCMAKE_BUILD_TYPE=RelWithDebInfo \
            -DCMAKE_INSTALL_PREFIX=/usr \
            -DCMAKE_INSTALL_SBINDIR:PATH=bin \
            -DBUILD_SHARED_LIBS=1
$ ninja -C build

So far, so good.

$ ninja -C build run_tests

Towards the end of the CI tests to be run, it hangs. The last line is always:

ssl/integration_test

I can't seem to find out where exactly, or why it hangs. I ran the run_tests through gdb, and I couldn't find the issue (I don't usually wrangle with gdb output).

The output of gdb (with interrupt and backtrace) can be found here: http://0x0.st/8ljC.txt

When I manually go into the directory "build/ssl" and then run "./integration_test", it runs just fine (and passes all tests).

Update: In fact, all the tests run fine if invoked manually.

Perhaps the run_tests programme crashes after this test, or during another test, but I don't know how to find out. Adding "-v" to the ninja command did not add more information.

I hope someone can help.

Thank you in advance!


________

Looking through the gdb output, I notice an error:

        parser = {<Parser> = {_vptr.Parser = 0x55555559e688 <vtable for ManifestParser+16>, state_ = 0x7fffffffdc68, file_reader_ = 0x7fffffffdd70, lexer_ = {filename_ = {str_ = 0x7fffffffdb20 "build.ni", len_ = 11}, input_ = {str_ = 0x7ffff783d010 <error: Cannot access memory at address 0x7ffff783d010>, len_ = 893097}, ofs_ = 0x7ffff79170ba <error: Cannot access memory at address 0x7ffff79170ba>, last_token_ = 0x7ffff79170b9 <error: Cannot access memory at address 0x7ffff79170b9>}}, env_ = 0x7fffffffdce8, options_ = {phony_cycle_action_ = kPhonyCycleActionWarn}, quiet_ = false}

However, grepping through the directory for "build.ni" (in case that is a wrong filename and should be "build.ini") does not give any results. Perhaps I'm on the wrong track.

There are a number of occurrences of "optimized out", so, for what it's worth, I will try build this with -O0 when I am home again.

Last edited by lquidfire (Yesterday 09:30:30)

Offline

#2 Yesterday 09:38:07

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,858

Re: Test for AWS-LC fails - How to debug

This topic would fit better in Creating & Modifying Packages OR Programming & Scripting .

Do you intend to create a PKGBUILD for this ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#3 Yesterday 09:39:01

lquidfire
Member
From: South Africa
Registered: 2017-07-26
Posts: 77

Re: Test for AWS-LC fails - How to debug

If I can get it built and working, then yes. There are packages for LibreSSL and WolfSSL.

Offline

#4 Yesterday 09:59:22

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,858

Re: Test for AWS-LC fails - How to debug

The approach that tends to work best on archlinux is to start a PKGBUILD.
One of the reasons for that is upstream usually targets debian/ubuntu and fedora/redhat type distros and archlinux does things different .

Moderator Note
Moving to Creating & Modifying Packages


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#5 Yesterday 10:14:06

lquidfire
Member
From: South Africa
Registered: 2017-07-26
Posts: 77

Re: Test for AWS-LC fails - How to debug

Thanks.

A first attempt at a PKGBUILD is here: http://0x0.st/8l47.txt

Since the errors I tried to build and test the package manually, hoping there would be more error output.

Last edited by lquidfire (Yesterday 10:14:41)

Offline

#6 Yesterday 19:28:48

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,858

Re: Test for AWS-LC fails - How to debug

When building in a clean chroot crypto/crypto_test --gtest_also_run_disabled_tests --gtest_filter=BNTest.DISABLED_WycheproofPrimality hung .
I gave it 10 minutes, then aborted build .


log of the check() function

ninja: Entering directory `build'
[0/2] cd /build/aws-lc/src/aws-lc-1.53.1 && /usr/bin/cmake -E echo Running\ SSL\ tests && cd ssl/test/runner && /usr/bin/go test -timeout 10m -shim-path /build/aws-lc/src/aws-lc-1.53.1/build/ssl/test/bssl_shim -handshaker-path /build/aws-lc/src/aws-lc-1.53.1/build/ssl/test/handshaker -ssl-transfer-test-file /build/aws-lc/src/aws-lc-1.53.1/ssl/test/runner/ssl_transfer/test_case_names.txt
Running SSL tests
go: downloading golang.org/x/crypto v0.10.0
go: downloading golang.org/x/sys v0.9.0
0/0/976/1000/9321
                  0/0/977/1000/9321
                  0/0/1976/2000/9321
                   0/0/1976/2000/9321
                   0/0/1977/2000/9321
                   0/0/2976/3000/9321
                   0/0/2977/3000/9321
                   0/0/3976/4000/9321
                   0/0/3976/4000/9321
                   0/0/3976/4000/9321
                   0/0/3977/4000/9321
                   0/0/4976/5000/9321
                   0/0/4977/5000/9321
                   0/0/5976/6000/9321
                   0/0/5977/6000/9321
                   0/0/6976/7000/9321
                   0/0/6977/7000/9321
                   0/0/7976/8000/9321
                   0/0/7976/8000/9321
                   0/0/7977/8000/9321
                   0/0/8976/9000/9321
                   0/0/8977/9000/9321
                   0/0/9321/9321/9321

PASS
ok  	boringssl.googlesource.com/boringssl/ssl/test/runner	7.845s
[1/2] cd /build/aws-lc/src/aws-lc-1.53.1 && /usr/bin/cmake -E echo && /usr/bin/cmake -E echo Running\ Go\ tests && /usr/bin/go test ./ssl/test/runner/hpke ./util/ar && /usr/bin/cmake -E echo && /usr/bin/cmake -E echo Running\ unit\ tests && /usr/bin/go run util/all_tests.go -build-dir /build/aws-lc/src/aws-lc-1.53.1/build

Running Go tests
ok  	boringssl.googlesource.com/boringssl/ssl/test/runner/hpke	0.098s
ok  	boringssl.googlesource.com/boringssl/util/ar	0.004s

Running unit tests
crypto/crypto_test [shard 2/24]
crypto/crypto_test [shard 7/24]
crypto/crypto_test [shard 5/24]
crypto/crypto_test --gtest_filter=Crypto.OnDemandIntegrityTest (custom environment)
crypto/urandom_test
crypto/urandom_test (custom environment)
crypto/crypto_test --gtest_also_run_disabled_tests --gtest_filter=SnapsafeGenerationTest.*
crypto/urandom_test (custom environment)
crypto/urandom_test (custom environment)
crypto/urandom_test (custom environment)
crypto/urandom_test (custom environment)
crypto/crypto_test --fork_unsafe_buffering --gtest_filter=RandTest.*:-RandTest.Fork
crypto/crypto_test --gtest_filter=RandTest.* (custom environment)
crypto/crypto_test [shard 6/24]
crypto/crypto_test --gtest_filter=ForkDetect.* (custom environment)
crypto/crypto_test [shard 19/24]
crypto/crypto_test [shard 9/24]
crypto/crypto_test [shard 15/24]
crypto/crypto_test [shard 17/24]
ssl/ssl_test [shard 1/24]
ssl/ssl_test [shard 5/24]
crypto/crypto_test [shard 11/24]
ssl/ssl_test [shard 2/24]
crypto/crypto_test [shard 13/24]
ssl/ssl_test [shard 3/24]
ssl/ssl_test [shard 6/24]
crypto/crypto_test [shard 16/24]
ssl/ssl_test [shard 4/24]
ssl/ssl_test [shard 7/24]
ssl/ssl_test [shard 10/24]
ssl/ssl_test [shard 9/24]
ssl/ssl_test [shard 8/24]
ssl/ssl_test [shard 11/24]
ssl/ssl_test [shard 12/24]
ssl/ssl_test [shard 13/24]
crypto/crypto_test [shard 3/24]
ssl/ssl_test [shard 14/24]
ssl/ssl_test [shard 16/24]
ssl/ssl_test [shard 17/24]
crypto/mem_test
crypto/mem_set_test
crypto/dynamic_loading_test
ssl/ssl_test [shard 15/24]
crypto/rwlock_static_init
ssl/ssl_test [shard 19/24]
ssl/ssl_test [shard 18/24]
ssl/ssl_test [shard 21/24]
ssl/ssl_test [shard 22/24]
ssl/ssl_test [shard 20/24]
ssl/ssl_test [shard 23/24]
crypto/crypto_test [shard 1/24]
ssl/ssl_test [shard 24/24]
crypto/crypto_test --gtest_also_run_disabled_tests --gtest_filter=RSATest.DISABLED_BlindingCacheConcurrency
crypto/crypto_test [shard 4/24]
crypto/crypto_test [shard 18/24]
crypto/crypto_test [shard 24/24]
crypto/crypto_test [shard 8/24]
crypto/crypto_test [shard 14/24]
crypto/crypto_test [shard 12/24]
crypto/crypto_test [shard 10/24]
ssl/integration_test
tool-openssl/tool_openssl_test
crypto/crypto_test --gtest_also_run_disabled_tests --gtest_filter=BNTest.DISABLED_WycheproofPrimality
signal: interrupt
ninja: build stopped: interrupted by user.

[1m[31m==> ERROR:(B[m[1m Aborted by user! Exiting...(B[m

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Board footer

Powered by FluxBB