Created attachment 868870 [details] app-crypt:gcr-4.1.0:20230828-033127.log =app-crypt/gcr-4.1.0 fails its test phase for me. Specifically, the test "gcr:gck / object" fails with SIGSEGV. When I tried to debug it by running the test program directly (using the command line in testlog.txt) it completed without error, but I've been unable to get such a successful result from the ebuild environment. Here's the output for this test from testlog.txt (which I will attach in full after the build log): =================================== 17/44 ==================================== test: gcr:gck / object start time: 03:32:11 duration: 0.01s result: killed by signal 11 SIGSEGV command: LD_LIBRARY_PATH=/var/tmp/portage/app-crypt/gcr-4.1.0/work/gcr-4.1.0-build/gck MALLOC_PERTURB_=108 /var/tmp/portage/app-crypt/gcr-4.1.0/work/gcr-4.1.0-build/gck/test-gck-object ----------------------------------- stdout ----------------------------------- TAP version 13 # random seed: R02Sb9e92808db0d694a29c2dbab689d014a 1..8 # Start of gck tests # Start of object tests ok 1 /gck/object/object_props ok 2 /gck/object/object_equals_hash # Gck-DEBUG: created object: (4) [ { CKA_CLASS = CKO_DATA }, { CKA_LABEL = (10) "TEST LABEL" }, { CKA_TOKEN = (1) "\x00" }, { CKA_VALUE = (4) NOT-PRINTED } ] # Gck-DEBUG: created object: (4) [ { CKA_CLASS = CKO_DATA }, { CKA_LABEL = (10) "TEST LABEL" }, { CKA_TOKEN = (1) "\x00" }, { CKA_VALUE = (4) NOT-PRINTED } ] ok 3 /gck/object/create_object # Gck-DEBUG: created object: (3) [ { CKA_CLASS = CKO_DATA }, { CKA_LABEL = (11) "TEST OBJECT" }, { CKA_TOKEN = (1) "\x01" } ] # Gck-DEBUG: created object: (3) [ { CKA_CLASS = CKO_DATA }, { CKA_LABEL = (11) "TEST OBJECT" }, { CKA_TOKEN = (1) "\x01" } ] ok 4 /gck/object/destroy_object ok 5 /gck/object/get_attributes ok 6 /gck/object/get_data_attribute ok 7 /gck/object/set_attributes # Gck-DEBUG: created object: (2) [ { CKA_CLASS = CKO_DATA }, { CKA_LABEL = (12) "UNIQUE LABEL" } ] # Gck-DEBUG: created object: (2) [ { CKA_CLASS = CKO_DATA }, { CKA_LABEL = (11) "OTHER LABEL" } ] # Gck-DEBUG: matching: (1) [ { CKA_LABEL = (12) "UNIQUE LABEL" } ] # Gck-DEBUG: matching: (0) [ ] # Gck-DEBUG: matching: (1) [ { CKA_LABEL = (9) "blah blah" } ] ==============================================================================
Created attachment 868871 [details] testlog.txt
Created attachment 868872 [details] emerge-info.txt
Try running under the 'sandbox' command manually?
I hit this same failure with version 3.41.1-r2, and tried running the command line from the failing test within a "sandbox" environment (I went to the build directory via "cd", typed "sandbox", and pasted in "UBSAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1:print_stacktrace=1 MALLOC_PERTURB_=1 LD_LIBRARY_PATH=/var/tmp/portage/app-crypt/gcr-3.41.1-r2/work/gcr-3.41.1-build/gck ASAN_OPTIONS=halt_on_error=1:abort_on_error=1:print_summary=1 /var/tmp/portage/app-crypt/gcr-3.41.1-r2/work/gcr-3.41.1-build/gck/test-gck-object"). It completed without error. When I reran the build (with the tests failing again) I saw this in "dmesg": [42022961.247448] pool-/var/tmp/p[4525]: segfault at 55df6dd0b5ab ip 00007f9d33cd0d63 sp 00007f9d32435a98 error 4 in libgck-testable.so[7f9d33ccb000+1e000] likely on CPU 1 (core 1, socket 0) [42022961.247462] Code: 48 8b 4f 08 31 d2 48 8b 3f 31 c0 48 85 c9 75 12 eb 25 0f 1f 44 00 00 8d 42 01 48 89 c2 48 39 c8 73 15 48 8d 04 40 48 8d 04 c7 <48> 3b 30 75 e8 c3 0f 1f 80 00 00 00 00 31 c0 c3 48 83 ec 08 48 8d
