Re: ls: write error: Broken pipe

[Jim Meyering]

Dan Nicolaescu <address@hidden> wrote:
> Jim Meyering <address@hidden> writes:
>
>   > Dan Nicolaescu <address@hidden> wrote:
>   > ...
>   > > I created a new account with /bin/tcsh as a shell, deleted all the dot
>   > > files in that new account, logged in on a linux console and run the
>   > > perl command above.  It prints IGNORE.
>   > >
>   > > tcsh is: tcsh-6.14-15
>   > > perl is: perl-5.8.8-23.fc7
>   >
>   > Finally!  So that version of tcsh may be at fault.
>
> I built tcsh-6.15 using the F8 rpm, and the problem still occurs with
> that one.
>
> When you tested this, did you try from an account that uses tcsh as
> the shell? Because if I start tcsh from bash things work...

Yes.  I changed my shell to /bin/tcsh and logged in again.

Have you tried on other systems?

Did you already look at /etc/csh.*?
Move them aside and try again, just in case.

I'm running out of ideas, but you might want to use oprofile
to trace everything from login to your first prompt.
Do it twice.  First with /bin/bash as your shell, then with /bin/tcsh.
Then compare.

>   > > So I have an older version of tcsh than you do.
>   > >
>   > > I looked at the src.rpm for my version of tcsh and it has a patch that
>   > > tinkers with signal handling (not with SIGPIPE, but still...). I'll
>   > > try to install your version of tcsh tonight, and maybe build my
>   > > version without any patches.
>   > >
>   > >   > If you could reproduce the problem by starting tcsh manually,
>   > >   > I'd suggest debugging (or just using strace) tcsh to see where
>   > >   > it's misbehaving.
>   > >
>   > > What should I look for?
>   >
>   > In source, look for calls to signal, sigaction, sigprocmask.
>   > On recent Linux, they show up in strace output as calls to
>   > rt_sigaction and rt_sigprocmask.
>
> strace did not show anything about SIGPIPE.

I wouldn't expect it to, since you can't reproduce the problem by
starting tcsh manually.