Hello,
On 03/17/2016 02:49 PM, Paul Eggert wrote:
On 03/16/2016 09:14 AM, Assaf Gordon wrote:
Attached is a patch that adds errno information to 'write error' messages
Thanks, I installed the attached somewhat-tweaked version of that. Among other things I
renamed the new static functions to
On 03/16/2016 09:14 AM, Assaf Gordon wrote:
write(1, "2\n", 2) = -1 EPIPE (Broken pipe)
--- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=2893,
si_uid=1004} ---
write(2, "./src/grep: ", 12)= 12
Although this looks weird and it's not what I would
On 03/16/2016 09:14 AM, Assaf Gordon wrote:
Attached is a patch that adds errno information to 'write error' messages
Thanks, I installed the attached somewhat-tweaked version of that. Among
other things I renamed the new static functions to avoid confusion with
existing "safer" functions.
On 03/18/2016 11:30 AM, Assaf Gordon wrote:
> I found that on my weird setup, programs start with SIGPIPE set to
> SIG_IGN by default (not sure how I got myself into such situation).
There have been various automated robot testsuite runners (such as
Jenkins at one point in the past, although I
Hello,
First,
Attached is a patch that adds errno information to 'write error' messages, e.g.:
$ grep [...] > /dev/full
grep: write error: No space left on device
I hope it is self-explanatory enough (comments and suggestions are welcomed).
Second,
On one gnu/linux server I'm
