Re: Bug with --remote-tab-silent

[Todd Neal]

Bram Moolenaar wrote:
Alexei Alexandrov wrote:
On 1/17/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
I can't reproduce it.  It could be caused by a plugin.

Does adding "-V10" show some context of the error?

Does anyone else see this?
It reproduces only when the extension of the file is added into
'wildignore'. In my .vimrc I have

set 
wildignore=*.o,*.obj,*.exe,*.lib,*.a,*.dll,*.swp,*.ncb,*.aps,*.opt,*.pdb,*.bak,*~,*.d

and the bug can be reproduced for any of these extensions. And only
with --remote-tab-silent.

OK, I can reproduce it now.  I have *.pyc in 'wildignore' and editing
foo.pyc causes the error message in the remote gvim with --remote-tab
and --remote-tab-silent.  What is worse: with --remote it crashes.
I'll look into it.



I've only looked into it for a bit, but if you start Vim with a command 
line argument (eg. gvim /tmp/foo.txt) You don't get the crash with 
--remote.  If you start it without one (eg. gvim ) then it crashes.

This appears to be caused by

buf = buflist_findnr(ARGLIST[0].ae_fnum);

in ex_drop at ex_cmds.c:6984

I'm not familiar with Vim's source at all, but it looks like ARGLIST is 
empty

(gdb) print (curwin)->w_alist->al_ga
$3 = {ga_len = 0, ga_maxlen = 0, ga_itemsize = 8, ga_growsize = 5,
  ga_data = 0x0}

Todd