[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #27975] Infinite loop for -exec [..] {} +
From: |
James Youngman |
Subject: |
[bug #27975] Infinite loop for -exec [..] {} + |
Date: |
Sun, 08 Nov 2009 23:04:21 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.15) Gecko/2009102814 Iceweasel/3.0.6 (Debian-3.0.6-3) |
URL:
<http://savannah.gnu.org/bugs/?27975>
Summary: Infinite loop for -exec [..] {} +
Project: findutils
Submitted by: jay
Submitted on: Sun 08 Nov 2009 11:04:20 PM GMT
Category: None
Severity: 4 - Important
Item Group: Wrong result
Status: None
Privacy: Public
Assigned to: jay
Originator Name: Elias Pipping
Originator Email: address@hidden
Open/Closed: Open
Discussion Lock: Any
Release: None
Fixed Release: None
_______________________________________________________
Details:
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
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?27975>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #27975] Infinite loop for -exec [..] {} +,
James Youngman <=