Re: Fwd: Re: error.c: "Unknown system error" should report errno value
From:
Martin Koeppe
Subject:
Re: Fwd: Re: error.c: "Unknown system error" should report errno value
Date:
Sun, 7 Oct 2007 13:12:50 +0200 (CEST)
On Sat, 6 Oct 2007, Jim Meyering wrote:
Martin Koeppe <address@hidden> wrote:
The first 'Segmentation fault' with dd doesn't occur when I run just
the failing command in the src dir:
./dd cbs=4 ibs=4 conv=unblock,sync < dd-in > dd-out
dd-out looks fine there. So I don't currently know how to reproduce
it...
How about when you run the test with VERBOSE=yes?
If the failing test is in tests/dd/misc, you'd do this:
make -C tests/dd check TESTS=misc VERBOSE=yes
Unfortunately, I cannot reproduce this seg fault any more. It's just
fine now, also with snapshot 303. Several other tests fail due to
broken seq as already discussed.
#####
2 tests fail because on Interix '\' is not a valid filename character
(other POSIX filename characters like '*' or '+' or '|' are fine),
I removed those tests for me:
{OUT=>"f: OK\n"}],
--- tests/misc/sha1sum.orig Sun Sep 16 09:06:25 2007
+++ tests/misc/sha1sum Sun Oct 7 00:24:18 2007
@@ -56,8 +56,8 @@
{OUT=>"50abf5706a150990a08b2c5ea40fa0e585554732 f\n"}],
['million-a', {IN=> {f=> 'a' x 1000000}},
{OUT=>"34aa973cd4c4daa4f61eeb2bdbad27316534016f f\n"}],
- ['bs-sha', {IN=> {".\\foo"=> ''}},
- {OUT=>"\\$sha_degenerate .\\\\foo\n"}],
+# ['bs-sha', {IN=> {".\\foo"=> ''}},
+# {OUT=>"\\$sha_degenerate .\\\\foo\n"}],
# The sha1sum and md5sum drivers share a lot of code.
# Ensure that sha1sum does *not* share the part that makes
# md5sum accept BSD format.
#####
The test tests/rm/deep-1 seems to cause an infinite loop or something
like that, I have to kill it always, so I disabled it for me, too.
The last lines in the test's log are:
++ exit 130
+ st=130
+ cleanup_
+ :
+ d=/srv/non-deb/coreutils/cu/tests/rm/cu-deep-1.kSpfDo3431
+ cd /srv/non-deb/coreutils/cu/tests/rm
+ chmod -R u+rwx /srv/non-deb/coreutils/cu/tests/rm/cu-deep-1.kSpfDo3431
So it seems to hang on cleanup, during chmod ... Didn't look into
this to more detail yet.
#####
The test tests/rm/dir-nonrecur shows IMO a real bug in coreutils,
however:
"rm d" should fail at
remove.c:1094 with "cannot remove 'd': Is a directory"
but fails there with "cannot remove 'd': No such file or diectory"
If I remove the translation call _() around the text, then it fails
correctly with "Is a directory". I think failures during translation
shouldn't change the errno reported.