Re[2]: Problem with running tests during installing coreutils-5.94

[Adam Waltman]

Hello Bob, Paul

BP> Adam Waltman wrote:
>>   I am trying to install coreutils-5.94 on my Gentoo system.
>>   It fails during test stage. I have entered the error report here:
>>   http://forums.gentoo.org/viewtopic-p-3262580.html#3262580
BP> Which links to the bug report here:
BP>   http://bugs.gentoo.org/show_bug.cgi?id=130246

BP> Can you recreate this build manually?  Probably the best place to
BP> start is to get a current copy of the package and build it yourself.
BP> Because to debug this we will want to see what is happening in the
BP> test.  After building if you could send us the debug output from the
BP> test it would be good.

Thank you for your quick response.
Gentoo is all about getting the source and compiling things on my
computer using gcc settings appropriate for my system (and so on...
:-)), so here is the output:


env DEBUG=yes VERBOSE=yes make check -C tests/shred TESTS=exact
make: Entering directory 
`/var/tmp/portage/coreutils-5.94-r1/work/coreutils-5.94/tests/shred'
make  check-TESTS
make[1]: Entering directory 
`/var/tmp/portage/coreutils-5.94-r1/work/coreutils-5.94/tests/shred'
+ shred --version
shred (GNU coreutils) 5.94
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software.  You may redistribute copies of it under the terms of
the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
There is NO WARRANTY, to the extent permitted by law.

Written by Colin Plumb.
++ pwd
+ pwd=/var/tmp/portage/coreutils-5.94-r1/work/coreutils-5.94/tests/shred
+ tmp=exact.4992
+ trap 'status=$?; cd $pwd; rm -rf $tmp && exit $status' 0
+ trap '(exit $?); exit' 1 2 13 15
+ framework_failure=0
+ mkdir exact.4992
+ cd exact.4992
+ test 0 = 1
+ fail=0
+ for opt in --exact --zero
+ echo a
+ echo bb
+ echo ccc
+ shred --remove --exact a b
+ test -f a
+ test -f b
+ shred --remove --exact c
+ test -f c
+ for opt in --exact --zero
+ echo a
+ echo bb
+ echo ccc
+ shred --remove --zero a b
./exact: line 25:  4998 Segmentation fault      shred --remove $opt a b
+ fail=1
+ test -f a
+ fail=1
+ test -f b
+ fail=1
+ shred --remove --zero c
./exact: line 25:  4999 Segmentation fault      shred --remove $opt c
+ fail=1
+ test -f c
+ fail=1
+ exit 1
+ exit 1
+ status=1
+ cd /var/tmp/portage/coreutils-5.94-r1/work/coreutils-5.94/tests/shred
+ rm -rf exact.4992
+ exit 1
FAIL: exact
======================================
1 of 1 tests failed
Please report to address@hidden
======================================
make[1]: *** [check-TESTS] Error 1
make[1]: Leaving directory 
`/var/tmp/portage/coreutils-5.94-r1/work/coreutils-5.94/tests/shred'
make: *** [check-am] Error 2
make: Leaving directory 
`/var/tmp/portage/coreutils-5.94-r1/work/coreutils-5.94/tests/shred'


I have run my test then:
k13 coreutils-5.94 # src/shred --version
shred (GNU coreutils) 5.94
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software.  You may redistribute copies of it under the terms of
the GNU General Public License <http://www.gnu.org/licenses/gpl.html>.
There is NO WARRANTY, to the extent permitted by law.

Written by Colin Plumb.

k13 coreutils-5.94 # ll > adam
k13 coreutils-5.94 # ll > adam1
k13 coreutils-5.94 # src/shred --remove --zero adam adam1
Segmentation fault

It seems that he shred itself is the culprit.
I have no real experience in programming in Linux,
but I have installed gdb and tried to squeeze something out of it
without any success. Could you instruct me how to trace this segfault?

Best regards,
Adam