What happens if you kill the tmux client or close the terminal it is in? Does the server recover?
On Wed, Dec 19, 2012 at 07:54:28PM +0800, Guang-Nan Cheng wrote: > Okay, PID 578 is the hanging attaching tmux clients. Here is the backtrace > for the original tmux server. > (gdb) bt > #0 **0x00007f8696181950 in __write_nocancel () at > ../sysdeps/unix/syscall-template.S:82 > #1 **0x000000000042d1c0 in tty_stop_tty (tty=tty@entry=0xe12c68) at > tty.c:242 > #2 **0x000000000042d35c in tty_close (tty=tty@entry=0xe12c68) at tty.c:272 > #3 **0x0000000000423490 in server_client_msg_dispatch (c=0xe02b60) at > server-client.c:776 > #4 **0x000000000042372d in server_client_callback (fd=22, events=2, > data=0x7) at server-client.c:213 > #5 **0x00007f86968850c2 in event_process_active_single_queue > (activeq=<optimized out>, base=<optimized out>) at event.c:1340 > #6 **event_process_active (base=<optimized out>) at event.c:1407 > #7 **event_base_loop (base=<optimized out>, flags=flags@entry=1) at > event.c:1604 > #8 **0x00007f8696886131 in event_loop (flags=flags@entry=1) at > event.c:1518 > #9 **0x0000000000424f2a in server_loop () at server.c:210 > #10 0x000000000042549f in server_start () at server.c:201 > #11 0x0000000000404829 in client_connect (path=0x66fc80 > "/tmp//tmux-0/default", start_server=1) at client.c:80 > #12 0x0000000000404ca9 in client_main (argc=argc@entry=0, > argv=argv@entry=0x7fff03c09050, flags=flags@entry=1) at client.c:152 > #13 0x0000000000403537 in main (argc=0, argv=0x7fff03c09050) at tmux.c:406 > On Wed, Dec 19, 2012 at 7:39 PM, Guang-Nan Cheng <[1]chen...@gmail.com> > wrote: > > Thanks for the tip. It seems**related**with epoll_wait. I have no idea > what it is. > > strace -p 578 > Process 578 attached > epoll_wait(3,** > > gdb > Missing separate debuginfos, use: debuginfo-install > tmux-1.6-1.fc17.x86_64 > (gdb) bt > #0 **0x00007f18e7b9dc53 in __epoll_wait_nocancel () from > /lib64/libc.so.6 > #1 **0x00007f18e82a8223 in ?? () from /lib64/libevent-2.0.so.5 > #2 **0x00007f18e8293e00 in event_base_loop () from > /lib64/libevent-2.0.so.5 > #3 **0x0000000000404d20 in ?? () > #4 **0x0000000000403537 in ?? () > #5 **0x00007f18e7acd735 in __libc_start_main () from /lib64/libc.so.6 > #6 **0x000000000040374d in ?? () > #7 **0x00007fff70392898 in ?? () > #8 **0x000000000000001c in ?? () > #9 **0x0000000000000002 in ?? () > #10 0x00007fff70393bd2 in ?? () > #11 0x00007fff70393bd7 in ?? () > #12 0x0000000000000000 in ?? () > On Wed, Dec 19, 2012 at 12:59 AM, Thomas Adam <[2]tho...@xteddy.org> > wrote: > > On 18 December 2012 16:11, Guang-Nan Cheng <[3]chen...@gmail.com> > wrote: > > It happend again. This time, I don't even have a .tmux.conf file. > > > > Is there any trick so that I can send a signal to the PID and tmux > will > > print the stack so we know why it hangs? > > Attach strace to the server pid of tmux. **Or better yet, gdb, and > issue "bt" to see if that helps any. > -- Thomas Adam > > References > > Visible links > 1. mailto:chen...@gmail.com > 2. mailto:tho...@xteddy.org > 3. mailto:chen...@gmail.com ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
