On Fri Jul 18 10:41:25 2025 +0000, Alfred Agrell wrote:
on wine, this returns unknown argument twice. On native, the second call returns usage, first returns a blank string.
thanks for the small repro
yes, look like native `find` bails out when some std handles are invalid (tried with a large file to search into, and it returns immediately).
I tend to agree that if could avoid to redirect find's input; that would be nice
one option that we could consider is to pass as stdin the handle to a file filled with '\n' and check at the end of test if file position hasn't changed (that would detect rogue read operations that should be set inside the tests) and giving test writer some insight of what happens). hoping that find doesn't actually read from it.