Ramel Eshed wrote: > > > I'm not sure what exactly you've done in the last few patches, but it > > > seems like the SEGV issue is solved now, Thanks. > > > > Glad to hear that. > > > > > Unfortunately, I have > > > a different issue now when using the gui; Sometimes, when I perform a > > > large search (~9000 results) Vim hangs and never restored. I enabled > > > the channel log and I see the following Netbeans messages even though > > > I'm not using the Netbeans protocol: > > > > > > ERR on 1: messageFromNetbeans(): Cannot read from channel, will close it > > > soon > > > > That's just an old name for what is now a generic function. > > > > > When running Vim in a terminal everything works fine, but for some > > > reason I still see errors in the channel's log. The terminal error is: > > > > > > ERR on 1: channel_select_check(): Cannot read from channel, will close it > > > soon > > > > > > Any idea what went wrong? > > > > Not really. It's possible the job just finished. Do you have a way to > > check for that? > > > > > The gui issue doesn't seem deterministic, so I can't give a way to > > > reproduce it, but you can download my plugin and play with it a bit > > > (It takes me no more than 10 searches in the linux kernel code base > > > until I see the issue). > > > > Let's first find out if the output is truncated or not. You could run > > the same command and redirect the output to a file, then check the > > channel log to see what's the last thing that Vim received. > > You're right. I checked and it seems like the job is finished, I can > see that Vim got all the job's output. That's however what I see at > the end of the log (the first line is the last line of the grep > process): > > /home/ramele/linux-4.6-rc5/block/blk-mq-sysfs.c:457: blk_mq_enable_h [01m > [Kotp [m [Klug(); > ' > 3.396833 : looking for messages on channels > 3.396842 on 0: Invoking channel callback Agrep_cb > 3.397006 on 0: Invoking channel callback Agrep_cb > 3.397174 on 0: Invoking channel callback Agrep_cb > 3.397333 on 0: Invoking channel callback Agrep_cb > 3.397424 ERR on 0: channel_read_fd(): Cannot read from channel, will close > it soon > 3.397433 ERR on 0: channel_read_fd(): Cannot read from channel, will close > it soon > 3.397445 ERR on 0: channel_read_fd(): Cannot read from channel, will close > it soon > 3.397451 ERR on 0: channel_read_fd(): Cannot read from channel, will close > it soon > 3.397462 ERR on 0: channel_read_fd(): Cannot read from channel, will close > it soon > 3.397467 ERR on 0: channel_read_fd(): Cannot read from channel, will close > it soon > 3.397478 ERR on 0: channel_read_fd(): Cannot read from channel, will close > it soon > 3.397484 ERR on 0: channel_read_fd(): Cannot read from channel, will close > it soon > . > . > . > > It seems that Vim hangs in an infinite loop here. For some reason I > didn't see it in the previous log, not sure why (maybe it's related to > some changes I made to simplify the debug). > > I hope that helps you. Let me know if you want me to chack further.
Thanks for finding this. I can avoid giving the error more than once by not trying to read if the channel is about to be closed. However, I still wonder why this happens. Is this only with gvim or also in a terminal? Simplest would be if you could run Vim in a debugger and set a breakpoint where the error is reported a second time. Anyway, I'll make a patch to avoid giving the error multiple times, that might already help, since it will skip trying to read. -- When a fly lands on the ceiling, does it do a half roll or a half loop? /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
