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:
<http://savannah.gnu.org/bugs/?47261>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
