On 27/09/11 13:33, James Vega wrote: > On Fri, Sep 23, 2011 at 08:31:00AM -0700, acampbell wrote: >> This sounds rather like what I am experiencing, tbough not identical. >> I am using vim-7.3 in xmonad. If I start gvim from a terminal it locks >> up, and I get these messages: >> >> ------------------------------------------------------------------------------------ >> E852: The child process failed to start the GUI >> >> [xcb] Unknown sequence number while processing queue >> >> [xcb] Most likely this is a multi-threaded client and XInitThreads has >> not been called >> >> [xcb] Aborting, sorry about that. >> gvim: ../../src/xcb_io.c:273: poll_for_event: Assertion >> `!xcb_xlib_threads_sequence_lost' failed. >> ---------------------------------------------------------------------------- > The fact that you're getting E852 means you have Tim's patch applied. I > saw some similar crashes on one of my systems and the attached patch > seems to fix the problem. Can you see if it also fixes the problem for > you? > > I'm not entirely sure why switching from fread/fwrite to normal > read/write fixes it, especially since I don't see the problem on all of > my systems. I have a feeling it's related to the lseek that the fdopen > does on the pipe fd (which causes a SIGPIPE), though
The only reason I used fdopen() was so that I didn't have to worry about restarting after signals. I didn't know vim already had suitable read/write wrappers for this situation, I would have used them if I had known. I'm happy with James's patch being applied to the official build, if James has tested it already. -- Tim Starling -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
