Hi,
I've come across a situation in which find will enter an infinite loop
when it shouldn't. I've written a script to reproduce the issue,
loop.sh, that I'm attaching together w/ the output, out.
The problem occurs when find is run on a file that cannot be opened
for reading as well as a large number of file (the order matters).
The problem will only occur when -exec [..] {} + is used, not w/ -exec
[..] {} \; or -print0 | xargs.
The problem will not occur if the number of files is too small (6664
does it for me, if you're unable to reproduce the issue w/ my script,
please try something greater than that) or if the above-mentioned file
is missing.
This is probably related to bug #27328 (I've had segfaults w/ slightly
different invocations earlier as well, I find myself unable to come up
w/ a test case that doesn't involve the 2G directory I ran it on, for
that, though)
-- Elias
out (1K) 