Re: bash, sed, SIGPIPE

[Jim Meyering]

Bruno Haible <address@hidden> wrote:
> Eric Blake wrote in 
> <http://lists.gnu.org/archive/html/bug-gnulib/2009-01/msg00007.html>:
>> > After 'trap - SIGPIPE', sed should get a fatal SIGPIPE signal in these 
>> > conditions.
>> > Quoting 
>> > <http://www.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#trap>
>> >
>> >   "If action is '-' , the shell shall reset each condition to the default 
>> > value."
>>
>> You're missing one other piece.
>>
>> "Signals that were ignored on entry to a non-interactive shell cannot be
>> trapped or reset, although no error need be reported when attempting to do
>> so."
>
> Is the culprit then the line 263 of build-aux/bootstrap, or is it in Jim's
> environment?

It must be something in my environment.
In a different screen(1) window on the same system (same shell, etc)
I cannot reproduce it.

Regardless, I have no SIGPIPE handler anywhere.
I.e.,

    $ perl -le 'print $SIG{PIPE}'
    Use of uninitialized value in print at -e line 1.