bugfindutils - Bugs: bug #19969, rc-125.exp fails on some systems

 
 

bug #19969: rc-125.exp fails on some systems

Submitted by:  James Youngman <jay>
Submitted on:  Sat May 26 10:34:44 2007  
 
Category: NoneSeverity: 2 - Minor
Item Group: Compilation FailureStatus: Need Info
Privacy: PublicAssigned to: James Youngman <jay>
Originator Name: Nelson H. F. BeebeOpen/Closed: Closed
Release: NoneFixed Release: None

Add a New Comment (Rich MarkupRich Markup):
   

You are not logged in

Please log in, so followups can be emailed to you.

 

(Jump to the original submission Jump to the original submission)

Sat Apr 2 21:54:40 2011, comment #6:

No response => closing. I believe this is fixed.

James Youngman <jay>
Project AdministratorIn charge of this item.
Thu Oct 7 09:52:24 2010, comment #5:

Is it possible that you could retest this, please?

James Youngman <jay>
Project AdministratorIn charge of this item.
Wed Mar 31 07:36:00 2010, comment #4:

Please retest on findutils-4.5.6b.

James Youngman <jay>
Project AdministratorIn charge of this item.
Sun Jul 5 22:42:03 2009, comment #3:

Leslie's code is now incoroprated into 4.5.x; is this still a problem?

James Youngman <jay>
Project AdministratorIn charge of this item.
Sat Feb 16 15:50:58 2008, 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.

James Youngman <jay>
Project AdministratorIn charge of this item.
Sat Sep 8 15:30:50 2007, 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.

James Youngman <jay>
Project AdministratorIn charge of this item.
Sat May 26 10:34:44 2007, 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

James Youngman <jay>
Project AdministratorIn charge of this item.

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Digest:
   bug dependencies.

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by jay (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 3 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat Apr 2 21:54:40 2011jayOpen/ClosedOpen=>Closed
    Sun Jul 5 22:42:03 2009jayStatusNone=>Need Info
    Mon Mar 24 00:04:05 2008jayDependencies-=>Depends on bugs #22708

    Back to the top


    Powered by Savane 3.1-cleanup