Hi,

I've been using tmux happily for a while.

This is a bug report for tmux-1.4.

I'm getting EAGAIN errors while writing to stdout.  I can
reproduce it reliably with tmux-1.4 on Solaris and Linux; it
doesn't happen with tmux-1.3.

$ tmux # run subsequent commands under tmux
$ tmux set foo bar; ls -l /usr/bin/

The output has various missing fragments and the process dies with
"/usr/local/bin/ls: write error":

    lrwxrwxrwx  1 root   root      7 2010-08-11 07:24 timesysp -> ./mailp*
    -R-xr-xr-x  1 root   sys     10K 2007-06-12 17:35 timex*
    -R-s--x--x  1 uucp   bin     51K 2007-01-05 17:20 tip*
    root   bin     134 2005-01-21 19:03 unalias*
    lrwxrwxrwx  1 root   root     16 2010-08-11 07:24 uname -> ../../sbin/uname*
    /usr/local/bin/ls: write error


Another example, python:

    $ tmux set foo bar; python
    >>> mystring = ...
    >>> print mystring  ==> IOError: [Errno 11] Resource temporarily unavailable
    >>> sys.stdout.write(mystring[:2000]) ==> IOError: [Errno 11] Resource 
temporarily unavailable
    >>> sys.stdout.write(mystring[:1800]) ==> ok, most of the time
    >>> sys.stdout.write(mystring[:1000]) ==> ok
    >>> sys.stderr.write(mystring) ==> ok

The stack trace, prompt, etc. print fine and printing a short
string works fine.  But trying to print mystring (or a 2000-byte
substring of it) reliably causes EAGAIN.

On Linux, strace shows write(1, ...) failing with EAGAIN.
(I couldn't reproduce the issue while trussing on Solaris.)

For some reason invoking "tmux set" immediately before the command
causes this problem, for the entire execution of the next program.
I only found this because I have "tmux set default-path $PWD &!"
in my zsh's chpwd function() and I noticed "cd"ing before a
command affects it.

Is this a known issue?

Thanks,
Karl


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users

Reply via email to