./length-check.sh: line 32: 206 Segmentation fault $@ ./length-check.sh: test failed for file length 0. FAIL: length-check.sh ./ccrypt-check.sh: line 40: 322 Segmentation fault $@ 2> /dev/null ./ccrypt-check.sh:136: Action returned 139 instead of 0. ./ccrypt-check.sh: test failed. ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib-hardened_libressl-test_20190113-153406 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) emerge -qpvO app-crypt/ccrypt [ebuild N ] app-crypt/ccrypt-1.10
Created attachment 561074 [details] emerge-info.txt
Created attachment 561076 [details] app-crypt:ccrypt-1.10:20190114-150544.log
Created attachment 561078 [details] emerge-history.txt
Created attachment 561080 [details] environment
Created attachment 561082 [details] etc.portage.tbz2
Created attachment 561084 [details] logs.tbz2
Created attachment 561086 [details] temp.tbz2
I cannot reproduce. Need your help... Is it working with openssl? or stable gcc? Can you run in ${S}: $ ./src/ccrypt -K key1 < /dev/null > /dev/null And reproduce the segfault? Can you please run this under gdb so we can see the stack?
Update summary. [something] is used when something refers to an overlay
