[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #47261] find produces two different results for the same command

From: Dale Worley
Subject: [bug #47261] find produces two different results for the same command
Date: Tue, 01 Mar 2016 19:55:27 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0

Follow-up Comment #6, bug #47261 (project findutils):

You can strip the memory addresses from the traces (which vary) by doing:

     <find1.txt sed -e 's/0x[0-9a-f]*/0x*/g' >f1
     <find2.txt sed -e 's/0x[0-9a-f]*/0x*/g' >f2

Then you can compare the traces directly with "diff -u f1 f2".

Looking at the results of that, I see that the major difference is that find2
has a huge block of fstat() calls, starting with "options", that are added
after all the processing that is seen in find1.  I suspect that some section
of the filesystem was added or became visible between the two runs.

You could write a simple script to trace through all the open() and fchdir()
calls to figure out what the full path of "options", etc. are, but I didn't
put in the work.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]