[Bug 297638] ldd reports signal 13 when in pipeline

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297638

--- Comment #4 from Benjamin Jacobs <[email protected]> ---
(In reply to Markus Wild from comment #3)
I think that you are mistaken because, contrary to what you wrote, it is well
the behaviour of standard utilities to behave like this (N.B. the fact that ldd
forks is an implementation detail and is irrelevant to this discussion). Let's
take tar for example:  `set -o pipefail; tar -cf - ./veryimportantdirectory |
head -c1 > badbackup.tar ; echo $? ` most definitely returns an error and emits
a message. And rightly, if you ask me.

The problem is that there is no way for the sending side to know that the
receiving side exited early but we shouldn't care because all is actually fine.
Your cat example still returns a non-zero value. So, some utilities emit a
message, some don't... Aren't we just going to create more compatibility
problems by changing this now? And isn't it better to know why something is
failing? Or would you argue that utilities shouln'd even return an error in
this case?

Disclaimer: I've no authority to argue and I'll adapt to whatever comes out of
this problem reports, even if I think that it is undue. I've shared two
techniques to avoid having to create temporary files which, in my view, have
better chances of achieving your goal than having someone implementing and
committing the requested change.

-- 
You are receiving this mail because:
You are the assignee for the bug.