Re: find terminated with SIGSEGV in partial_quotearg_n

2025-01-26 Thread James Youngman
error (0, 0, _("File system loop detected; " "the following directory is part of the cycle: %s"), safely_quote_err_filename (0, ent->fts_path)); Would it be clearer to stick to just saying "cycle" or "loop" but not using both words? I'm just considering that we may be making it harder to

Re: tests: adjust shell syntax that breaks AIX /bin/sh

2025-01-26 Thread James Youngman
FWIW, I think AIX is compliant here.I believe that this syntax is valid: for x; do y; done ... and this syntax is also valid for x do y done ... but for x; do y done ... isn't (at least in some POSIX versions - I don't know if this changed at any point).

Re: tests: adjust shell syntax that breaks AIX /bin/sh

2025-01-26 Thread Bernhard Voelker
On 1/26/25 07:29, Collin Funk wrote: On AIX, /bin/sh causes a testsuite failure with an output like this: Running /home/collinfunk/findutils-4.10.0.40-d4417/find/testsuite/find.gnu/execdir-multiple.exp ... FAIL: execdir-multiple.new-O0, ./runme[6]: syntax error at line 7 : `newline

Re: find terminated with SIGSEGV in partial_quotearg_n

2025-01-26 Thread Bernhard Voelker
On 1/24/25 16:03, Dietmar Hahn (Fujitsu) via Bug reports for the GNU find utilities wrote: From: Bernhard Voelker The fts_cycle looks corrupted. The underlying gnulib code seems to be a bit vague about this, and the comment about coreutils is also not true (any more): https://git.savannah.gnu