Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 913149 - app-crypt/gcr-4.1.0 fails test "gcr:gck / object" with segfault
Summary: app-crypt/gcr-4.1.0 fails test "gcr:gck / object" with segfault
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-28 11:52 UTC by Jonathan Lovelace
Modified: 2023-08-29 07:54 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
app-crypt:gcr-4.1.0:20230828-033127.log (app-crypt:gcr-4.1.0:20230828-033127.log,239.64 KB, text/plain)
2023-08-28 11:52 UTC, Jonathan Lovelace
Details
testlog.txt (testlog.txt,444.77 KB, text/plain)
2023-08-28 11:52 UTC, Jonathan Lovelace
Details
emerge-info.txt (emerge-info.txt,8.99 KB, text/plain)
2023-08-28 11:53 UTC, Jonathan Lovelace
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Lovelace 2023-08-28 11:52:11 UTC
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" } ]
==============================================================================
Comment 1 Jonathan Lovelace 2023-08-28 11:52:49 UTC
Created attachment 868871 [details]
testlog.txt
Comment 2 Jonathan Lovelace 2023-08-28 11:53:09 UTC
Created attachment 868872 [details]
emerge-info.txt
Comment 3 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2023-08-29 07:54:32 UTC
Try running under the 'sandbox' command manually?