[Bug 215237] sysutils/tmux: `lost server' when running `tmux'

[bugzilla-noreply at freebsd.org]

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

            Bug ID: 215237
           Summary: sysutils/tmux: `lost server' when running `tmux'
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: mat at FreeBSD.org
          Reporter: sylvain at sylvaingarrigues.com
          Assignee: mat at FreeBSD.org
             Flags: maintainer-feedback?(mat at FreeBSD.org)

Created attachment 177893
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=177893&action=edit
truss output

Today on 2016-12-12,I just installed a fresh CURRENT snapshot as of 2016-11-01
on my machine. I also installed tmux 2.3 package on this fresh machine, let's
call it machine A.

I also have machine B which also has a snapshot of 2016-11-01 but which was
installed around 2016-11-01. tmux 2.3 was installed at that time.

On machine A, simply typing `tmux' fails with 'lost server'. No problem on
machine B.
However on both machine, 'tmux new bash' works. 

I run with "-v" and server log are exactly the same except there is no session
created in server so server stop after "spawn ...".

What is interesting is the output of (see file attached):
truss -a -f -e -s 1024 -o tmux_truss.trace tmux -v

I can see an undefined symbol "basename" in log.
92142: write(2,"/usr/local/bin/tmux: Undefined symbol "basename"",48) = 48
(0x30)
92142: write(2,"\n",1)                           = 1 (0x1)
92143: pselect(0x1,0x7fffffffd7f0,0x0,0x0,0x0,0x7fffffffd7e0) ERR#4
'Interrupted system call'
92143: SIGNAL 1 (SIGHUP)
92143: sigreturn(0x7fffffffd240)                 ERR#4 'Interrupted system
call'
92143: ioctl(2,TIOCSTART,0x0)                    ERR#6 'Device not configured'
92143: ioctl(0,TIOCSETAW,0x711e6c)               ERR#6 'Device not configured'

Was this introduced by clang-3.9? (maybe the package was build with newer
clang)

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