Looking through existing bug reports for something similar to my freshly reported problem #382798 (bash builtin echo fails to cope with signals arriving at the wrong moment) I suspect that #332881 has the same root cause:
* Note that the the (useless) use of <(cat ...), twice, causes two subprocesses which will run asynchronously with the cmp. * If one or both of these subprocesses terminate at the right moment, just as `echo' is executing, echo's write(2) is interrupted. This causes (I suspect) echo to fail. * Since the script has no `set -e' (a serious mistake by the submitter) it carries on blithely, despite the lost output. Ian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
