Vim tests hanging on Solaris since patch 394

[Vladimir Marek]

Hi,

While trying to integrate latest vim into Solaris I found out that
the tests no longer finish. After some bisecting I found it it's caused
by patch 394

https://github.com/vim/vim/commit/5903aaf7eb4586cf7e4fa5a219092334b05c89de

Last output on the screen is

Test_map_cmdkey

Executed process has arguments

../vim -f -u unix.vim --gui-dialog-file guidialog -U NONE --noplugin --not-a-term -S runtest.vim test_mapping.vim --cmd au SwapExists * let v:swapchoice = "e"

If I break vim at that moment the stack looks like

7fffbfff65a0 libc.so.1`__pollsys+0xa()
7fffbfff6680 libc.so.1`pselect+0x191(0?, 0?, 0?, 0?, 0?, 0?)
7fffbfff66a0 libc.so.1`select+0x6d(0?, 0?, 0?, 0?, 0?)
7fffbfff67e0 vim`WaitForCharOrMouse+0x16d()
7fffbfff6830 vim`ui_wait_for_chars_or_timer+0xe1()
7fffbfff6860 vim`f_term_wait+0x12d()
7fffbfff6890 call_internal_func+0x64()
7fffbfff6b70 vim`call_func+0x93e()
7fffbfff6d40 vim`get_func_tv+0x21b()
7fffbfff7040 vim`ex_call+0x36d()
7fffbfff72d0 do_one_cmd+0x1919()
7fffbfff7a70 do_cmdline+0x547()
7fffbfff7e80 vim`call_user_func+0xb5e()
7fffbfff7f10 vim`call_user_func_check+0xb2()
7fffbfff81f0 vim`call_func+0x652()
7fffbfff83c0 vim`get_func_tv+0x21b()
7fffbfff86c0 vim`ex_call+0x36d()
7fffbfff8950 do_one_cmd+0x1919()
7fffbfff90f0 do_cmdline+0x547()
7fffbfff9500 vim`call_user_func+0xb5e()
7fffbfff9590 vim`call_user_func_check+0xb2()
7fffbfff9870 vim`call_func+0x652()
7fffbfff9a40 vim`get_func_tv+0x21b()
7fffbfff9d40 vim`ex_call+0x36d()
7fffbfff9fd0 do_one_cmd+0x1919()
7fffbfffa770 do_cmdline+0x547()
7fffbfffab80 vim`call_user_func+0xb5e()
7fffbfffac10 vim`call_user_func_check+0xb2()
7fffbfffaef0 vim`call_func+0x652()
7fffbfffb0c0 vim`get_func_tv+0x21b()
7fffbfffb3c0 vim`ex_call+0x36d()
7fffbfffb650 do_one_cmd+0x1919()
7fffbfffbdf0 do_cmdline+0x547()
7fffbfffbf20 ex_execute+0x345()
7fffbfffc1b0 do_one_cmd+0x1919()
7fffbfffc950 do_cmdline+0x547()
7fffbfffcd60 vim`call_user_func+0xb5e()
7fffbfffcdf0 vim`call_user_func_check+0xb2()
7fffbfffd0d0 vim`call_func+0x652()
7fffbfffd2a0 vim`get_func_tv+0x21b()
7fffbfffd5a0 vim`ex_call+0x36d()
7fffbfffd830 do_one_cmd+0x1919()
7fffbfffdfd0 do_cmdline+0x547()
7fffbfffe140 vim`do_source_ext+0x4ad()
7fffbfffe160 vim`ex_source+0xd6()
7fffbfffe3f0 do_one_cmd+0x1919()
7fffbfffeb90 do_cmdline+0x547()
7fffbfffec80 vim`vim_main2+0xcda()
7fffbfffec90 _start+0x43()


For the moment I just skip including the patch, but it would be great if
the issue could be fixed of course. Is there anything I could try to
debug it deeper? On first sight the change to vim does not seem to be
connected to the tests ...

Thank you for VIM!
--
Vlad