(
Jump to the original submission)
Sat 02 Apr 2011 09:54:40 PM UTC, comment #6:
No response => closing. I believe this is fixed.
|
Thu 07 Oct 2010 09:52:24 AM UTC, comment #5:
Is it possible that you could retest this, please?
|
Wed 31 Mar 2010 07:36:00 AM UTC, comment #4:
Please retest on findutils-4.5.6b.
|
Sun 05 Jul 2009 10:42:03 PM UTC, comment #3:
Leslie's code is now incoroprated into 4.5.x; is this still a problem?
|
Sat 16 Feb 2008 03:50:58 PM UTC, comment #2:
Regarding the merge of the fix for this problem, I'm planning to issue some 4.4.x release candidates besed on the current 4.3.x, and then issue a stable 4.4.0 release. Following that, we will have a 4.5.x development release series, into which I will merge Leslie's changes.
|
Sat 08 Sep 2007 03:30:50 PM UTC, comment #1:
We also have some problems with distinguishing the case where the command cannot be run from the case where it runs and returns status 126. Leslie Polzer's changes should, as a side effect, fix this. But merging Leslie's changes is a nontrivial amount of work.
|
Sat 26 May 2007 10:34:44 AM UTC, original submission:
The technique of using "kill $$" is unreliable. For example,
on MacOS X, the child just exits with a nonzero status.
This works better but is harder to use in a DejaGnu test:
yes | xargs -I{} echo | true
Part of the problem here of course is that the exit status of the
pipeline is the exit status of its last compinent.
The existing test is essentially
echo 'kill $$' | xargs -n1 -IARG sh -c ARG
... but this causes xargs to return status 123 on some systems, including:
OpenBSD 3.9
Solaris 10 SPARC
Solaris 10 IA-32
|
(Note: upload size limit is set to 16384 kB, after insertion of the required
escape characters.)
Attach File(s):
Comment:
No files currently attached
Depends on the following items
Digest:
bug dependencies.
Items that depend on this one: None found
Follow 3 latest changes.