On Mon, 2006-01-09 at 20:55 +0100, Jim Meyering wrote:
> Stavros Passas <[EMAIL PROTECTED]> wrote:
> ...
> > more,on coreutils 5.93 the output on the same command is:
> >
> > chmod: fts_read failed: Permission denied
> > *** glibc detected *** chmod: double free or corruption (fasttop):
>
> Thanks for the report.
> However, I'm not able to reproduce that with 5.93 and a small
> hierarchy created like this (on a RHEL 2.4.28-sparc system):
>
> $ mkdir -p {a,b,c}/{c,d,e}/{c,d,e}
> $ chmod o+r `find ./`
o+r means that you want to add read attr to owner,
but keep all the old attrs the same.The bug presented when the new attrs
are 0600 :
chmod 600 `find ./`
> Are you sure you saw that bug also with coreutils-5.93?
> There was indeed a double-free bug in fts.c, but it was
> fixed for coreutils-5.3.0. Did you build coreutils-5.93 yourself?
> If so, did it pass its self-tests (make -k check)?
My system uses the old coreutils, so I compile myself the coreutils-5.93
before the bug report. all the tools pass all them self-tests.
(I run them without EXPENSIVE env set)
Moreover, the old chmod don't print the memory map and backtrace on
sigsegv
> Please give the precise commands you used (show the one
> that invokes chmod --version, too) as well as the file list
> produced by `find .'. If that file list is long, it'd be good
> if you would pare it down to as small a test case as possible that
> still exhibits the problem.
mkdir a;cd a; touch b;
chmod 600 `find ./` or just chmod 600 ./ b
is enough
./test_chmod --version
chmod (GNU coreutils) 5.93
I hope to help.
Regards,
Stavros Passas
Computer Architecture and VLSI Systems Laboratory
Institute of Computer Science
Foundation for Research & Technology - Hellas
_______________________________________________
Bug-coreutils mailing list
Bug-coreutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-coreutils
