Here's a preview of what should soon appear as coreutils-8.8.
This is mostly a bug-fix release, with numerous fixes to our
newly-parallelized sort. Any testing you can perform over
the weekend would be most welcome.
coreutils snapshot: (.gz files are here, too)
Jim Meyering wrote, On 12/17/2010 05:07 AM:
Here's a preview of what should soon appear as coreutils-8.8. [...]
Any testing you can perform over the weekend would be most welcome.
On CentOS 5.4, du/bigtime fails (in a reproducible manner).
$ uname -a
Linux XX 2.6.18-164.11.1.el5 #1 SMP
I just ran cppcheck 1.46 on the latest coreutils.
It ran for a _long_ time and reported these false positives
[coreutils/src/system.h:355]: (error) Resource leak: fd
[coreutils/src/chown-core.c:212]: (error) Resource leak: fd
[coreutils/src/ls.c:1963]: (error) Unusual pointer arithmetic
I just ran this on the latest coreutils:
scan-build -o clang ./configure
scan-build -o clang make
and it flagged a possible problem in wc
where it could spin if it got a read error
on a large file containing file names to process.
I think the following may address this:
diff --git a/src/wc.c
I found this one by tracking down a bug with the latest snapshot
on Solaris. Still haven't got to the real bug yet, but this bug
was getting in the way.
From 7669bee6d7e9d0e806e42cb1033bd2b6642b7e9a Mon Sep 17 00:00:00 2001
From: Paul Eggert egg...@cs.ucla.edu
Date: Fri, 17 Dec 2010 22:39:47
Hi Assaf,
On 17/12/10 19:29, Assaf Gordon wrote:
Hello,
A question regarding the memory usage requirements of the parallel sort:
It seems that the memory usage (resident size) increases with the number of
threads used.
It also seems to me (but not verified) that the increased memory usage
Pádraig Brady wrote:
On 17/12/10 16:11, Pádraig Brady wrote:
I also notice more warnings and a possible
uninitialized stat buf in cp.c.
I'll have a look at these later...
That was another buglet fixed with:
commit b0cce8793c0b7a305f0f336e2f563ea941c44a92
Author: Pádraig Brady
Paul Eggert wrote:
I found this one by tracking down a bug with the latest snapshot
on Solaris. Still haven't got to the real bug yet, but this bug
was getting in the way.
Subject: [PATCH] tests: set fail=0 by default
* tests/init.sh (setup_): Set fail=0. This was the intent as per
