[bug #64451] Unexpected behaviour of xargs when multiple children exit with 255 in parallel

Follow-up Comment #5, bug #64451 (project findutils): >From wait(2): *WIFSTOPPED(*_wstatus_*)* returns true if the child process was stopped by delivery of a signal; this is possible only if the call was done using *WUNTRACED* or when the child is being traced (see *ptrace*(2)). OK so I g

Re: [bug #58197] "find" fails to optimize "-path /usr/foo -o -path /usr/bar" to "-regex '/usr/\(foo\|bar\)'"

> On 19 Jul 2023, at 11:52 PM, Spencer Baugh wrote: > > Follow-up Comment #3, bug #58197 (project findutils): > > One use case is GNU Emacs which heavily uses find, for example in M-x rgrep. > Emacs often constructs find commands which look like this by default: > > find -H . \( -path \*/S

[bug #64451] Unexpected behaviour of xargs when multiple children exit with 255 in parallel

Follow-up Comment #4, bug #64451 (project findutils): I still can't figure out how catching SIGSTOP is supposed to work. Neither SIGSTOP nor SIGTSTP seem to be caught. ___ Reply to this item at: _

[bug #64451] Unexpected behaviour of xargs when multiple children exit with 255 in parallel

Follow-up Comment #3, bug #64451 (project findutils): I've been able to fix this behaviour by explicitly calling _wait_for_proc_all_(). I can't imagine any reprocussions from doing this, but the current code expects _wait_for_proc_all_() to be called _atexit_() so I would need some insight into wh

[bug #64451] Unexpected behaviour of xargs when multiple children exit with 255 in parallel

Follow-up Comment #2, bug #64451 (project findutils): Because checks for WSTOPSIG and WTERMSIG are done in the same place, sending SIGTERM or SIGSTOP to the children should also cause the same behaviour. In reality though trying to _kill_ chuldren with this tester seq 3 | xargs -n1 -P0 sh -c

[bug #64451] Unexpected behaviour of xargs when multiple children exit with 255 in parallel

Follow-up Comment #1, bug #64451 (project findutils): A workaround for scripts is to perform checks as soon as possible and exit 1 (or other value) instead. Potentially hundreds of processes will still be spawned but this avoids potentially processing outputs that are not yet complete. Ano

[bug #64451] Unexpected behaviour of xargs when multiple children exit with 255 in parallel

URL: Summary: Unexpected behaviour of xargs when multiple children exit with 255 in parallel Group: findutils Submitter: None Submitted: Thu 20 Jul 2023 07:46:06 AM UTC Catego