Tmux 1.8 cored on Solaris while selecting in pane

[Martin Řehák]

Hello,

I got core while pressing enter to do a text selection in tmux 1.8 on Solaris.
Here is the backtrace:

***@unix:~$ mdb tmux.core
Loading modules: [ libc.so.1 ld.so.1 ]

$C

fffffd8304fc0b51 tty_puts+4(91325052f0, 0, 10007a848, 913c60d090, bb6c, 0)
fffffd8304fc0c01 tty_cmd_setselection+0x7c(91325052f0, fffffd8304fc1610, 8c91, 913c60d090, aaaaaaab, 8c91)
fffffd8304fc0cb1 tty_write+0x12c(100058d80, fffffd8304fc1610, 0, 10400, 100212840, 10148)
fffffd8304fc0d61 screen_write_setselection+0x48(fffffd8304fc1710, 913c6043f0, 8c8f, 100058, 91305bdbc0, 913c90b850)
fffffd8304fc0e61 window_copy_copy_buffer+0x48(91305bdbc0, ffffffffffffffff, 913c6043f0, 8c8f, 10007a, fffffd8304fc1710)
fffffd8304fc0f21 window_copy_copy_selection+0x20(91305bdbc0, ffffffffffffffff, 10007a, 32, 32, 10005db10)
fffffd8304fc0fe1 window_copy_key+0x9e0(91305bdbc0, 32, 9130579f20, 1, 913c90b8c8, 913c90b850)
fffffd8304fc1211 tty_keys_next+0x39c(913b88fef0, d, 1, 10000, 1, d)
fffffd8304fc12e1 tty_read_callback+4(9130cb2cb0, 913b88fef0, 9130cb2cb8, 34, ffff0c00, 1)
fffffd8304fc1391 libevent-1.4.so.2.2.0`bufferevent_readcb+0x1a0(9130cb2cb8, 9130c90e10, 9130cb2cb0, 0, 7fc08a3d20000,
9130c90e10)
fffffd8304fc1451 libevent-1.4.so.2.2.0`event_process_active+0xd8(913054bf00, 9130cb2cb8, 9130545c20, 1b, 7fc08a3d20000
, 1)
fffffd8304fc1511 libevent-1.4.so.2.2.0`event_base_loop+0x238(913054bf00, 10624c00, 0, e94c5a2, 7fc08a3e00000,
7fc08a3e00a38)
fffffd8304fc15f1 server_loop+0x40(0, 913057b3e0, 0, 1, 100202310, 100212840)
fffffd8304fc16a1 server_start+0xb08(100212, 100000, 100212000, 100212000, 100212, 10004b000)
fffffd8304fc1771 client_connect+0x16c(100212948, 4, 100069a80, 4, 100072c00, fffffd8304fc2030)
fffffd8304fc18a1 client_main+0x160(0, fffffd8304fc34d0, 0, 0, 100212000, 0)
fffffd8304fc21c1 main+0xa70(9130545c20, 41c0, 100079, 100079000, 0, fffffd8304fc379b)
fffffd8304fc2c11 _start+0x17c(0, 0, 0, 0, 0, 0)

::status

debugging core file of tmux (64-bit) from unix
file: /usr/bin/tmux
initial argv: tmux
threading model: native threads
status: process terminated by SIGSEGV (Segmentation Fault), addr=0

ttu_puts() got 0 as a second argument. Let me know if you need more info for debugging.

Thank you

[Nicholas Marriott]

Hi

IIRC this is a bug in Solaris libcurses. I think when we found it before
someone reported it to whoever owned Solaris at the time and they said
they weren't going to fix it.

I suggest you just turn off set-clipboard.

Post by Martin Řehák
Hello,
I got core while pressing enter to do a text selection in tmux 1.8 on Solaris.
Loading modules: [ libc.so.1 ld.so.1 ]

$C

fffffd8304fc0b51 tty_puts+4(91325052f0, 0, 10007a848, 913c60d090, bb6c, 0)
fffffd8304fc0c01 tty_cmd_setselection+0x7c(91325052f0, fffffd8304fc1610, 8c91, 913c60d090, aaaaaaab, 8c91)
fffffd8304fc0cb1 tty_write+0x12c(100058d80, fffffd8304fc1610, 0, 10400, 100212840, 10148)
fffffd8304fc0d61 screen_write_setselection+0x48(fffffd8304fc1710, 913c6043f0, 8c8f, 100058, 91305bdbc0, 913c90b850)
fffffd8304fc0e61 window_copy_copy_buffer+0x48(91305bdbc0, ffffffffffffffff, 913c6043f0, 8c8f, 10007a, fffffd8304fc1710)
fffffd8304fc0f21 window_copy_copy_selection+0x20(91305bdbc0, ffffffffffffffff, 10007a, 32, 32, 10005db10)
fffffd8304fc0fe1 window_copy_key+0x9e0(91305bdbc0, 32, 9130579f20, 1, 913c90b8c8, 913c90b850)
fffffd8304fc1211 tty_keys_next+0x39c(913b88fef0, d, 1, 10000, 1, d)
fffffd8304fc12e1 tty_read_callback+4(9130cb2cb0, 913b88fef0, 9130cb2cb8, 34, ffff0c00, 1)
fffffd8304fc1391 libevent-1.4.so.2.2.0`bufferevent_readcb+0x1a0(9130cb2cb8, 9130c90e10, 9130cb2cb0, 0, 7fc08a3d20000,
9130c90e10)
fffffd8304fc1451 libevent-1.4.so.2.2.0`event_process_active+0xd8(913054bf00, 9130cb2cb8, 9130545c20, 1b, 7fc08a3d20000
, 1)
fffffd8304fc1511 libevent-1.4.so.2.2.0`event_base_loop+0x238(913054bf00, 10624c00, 0, e94c5a2, 7fc08a3e00000,
7fc08a3e00a38)
fffffd8304fc15f1 server_loop+0x40(0, 913057b3e0, 0, 1, 100202310, 100212840)
fffffd8304fc16a1 server_start+0xb08(100212, 100000, 100212000, 100212000, 100212, 10004b000)
fffffd8304fc1771 client_connect+0x16c(100212948, 4, 100069a80, 4, 100072c00, fffffd8304fc2030)
fffffd8304fc18a1 client_main+0x160(0, fffffd8304fc34d0, 0, 0, 100212000, 0)
fffffd8304fc21c1 main+0xa70(9130545c20, 41c0, 100079, 100079000, 0, fffffd8304fc379b)
fffffd8304fc2c11 _start+0x17c(0, 0, 0, 0, 0, 0)

::status

debugging core file of tmux (64-bit) from unix
file: /usr/bin/tmux
initial argv: tmux
threading model: native threads
status: process terminated by SIGSEGV (Segmentation Fault), addr=0
ttu_puts() got 0 as a second argument. Let me know if you need more info for debugging.
Thank you
--
Martin Rehak
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
tmux-users mailing list
https://lists.sourceforge.net/lists/listinfo/tmux-users

[Peter Schow]

Post by Nicholas Marriott
Hi
IIRC this is a bug in Solaris libcurses. I think when we found it before
someone reported it to whoever owned Solaris at the time and they said
they weren't going to fix it.

Anyone have a bug number for this?

I maintain tmux for Solaris and will be glad to take a look.

[Martin Řehák]

Hi,

I have filed internal bug. Thank you very much for information.

Regards
--
Martin

Post by Peter Schow

Post by Nicholas Marriott
Hi
IIRC this is a bug in Solaris libcurses. I think when we found it before
someone reported it to whoever owned Solaris at the time and they said
they weren't going to fix it.

Anyone have a bug number for this?
I maintain tmux for Solaris and will be glad to take a look.

------------------------------------------------------------------------------