PANIC PANIC PANIC about gocode HOT 10 CLOSED

What's the Go version? What's the gocode version?

Can't reproduce on my machine, works just fine:

from gocode.

hg tip. I tested it with latest on windows.

from gocode.

Also, try this: run gocode daemon by hand in a separate console window. For windows:

start -> run... cmd
gocode close
gocode -s

and then try again. Since it is a daemon panic, it will show you the stack trace, put it here.

from gocode.

panic: runtime error: index out of range
1(runtime.panic): /go/src/pkg/runtime/proc.c:1275
2(runtime.panicstring): /go/src/pkg/runtime/runtime.c:128
3(runtime.panicindex): /go/src/pkg/runtime/runtime.c:85
4(main.utf8MoveBackwards): c:/temp/github/gocode/apropos.go:21
5(main.(*AutoCompleteContext).deduceDecl): c:/temp/github/gocode/apropos.go:130
6(main.(*AutoCompleteContext).Apropos): c:/temp/github/gocode/autocompletecontext.go:216
7(main.Server_AutoComplete): c:/temp/github/gocode/server.go:82
8(main.(*RPCRemote).RPCServer_AutoComplete): c:/temp/github/gocode/rpc.go:27
9(reflect.internalValue.call): c:/go/src/pkg/reflect/value.go:595
10(reflect.Value.Call): c:/go/src/pkg/reflect/value.go:445
11(rpc.(*service).call): c:/go/src/pkg/rpc/server.go:341
12(runtime.goexit): /go/src/pkg/runtime/proc.c:246

from gocode.

Hm, thanks, I've seen that error in the past. Can't remember what was wrong though.. Basically some kind of data is incorrect. This function "utf8MoveBackwards" is called when the editor issues autocompletion and gocode needs to move cursor back to the point where it can do autocompletion. And error originates from the point where no checks were performed, it simply takes the cursor position, moves it back and tries to access the buffer. I guess something of these two must be wrong. The cursor position or the contents of the buffer. Could be a vim script that fails to send the right data or something else.

Well.. I don't know, check these two vars by yourself somewhere around the error, 'file' should contain the buffer of the file you're editting and 'cursor' is an offset in bytes from the beginning of the buffer to the cursor position. If one of these is incorrect try to figure out why.

I'll try to reproduce the bug on my windows machine, but I don't know when I will be there and if it can be reproduced at all.

Also I strongly recommend you to use at least weekly versions. It's hard for me to work on abstract 'hg tip', because at the time when I will get to my windows machine most likely it's different 'hg tip' already.

from gocode.

One reason I can imagine why it may happen, is vim's "line2byte". I think vim needs to be compiled with +byte_offset option.
See vim --version

from gocode.

My vim --version

+arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent 
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments 
+conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con +diff +digraphs 
-dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path 
+find_in_path +float +folding -footer +gettext/dyn -hangul_input +iconv/dyn 
+insert_expand +jumplist +keymap +langmap +libcall +linebreak +lispindent 
+listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape 
+multi_byte_ime/dyn +multi_lang -mzscheme -netbeans_intg +path_extra +perl/dyn 
+persistent_undo -postscript +printer -profile +python/dyn -python3 +quickfix 
+reltime +rightleft +ruby/dyn +scrollbind +signs +smartindent -sniff 
+startuptime +statusline -sun_workshop +syntax +tag_binary +tag_old_static 
-tag_any_white -tcl -tgetent -termresponse +textobjects +title -toolbar 
+user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace 
+wildignore +wildmenu +windows +writebackup -xfontset -xim -xterm_save -xpm_w32

from gocode.

well, it has +byte_offset, that's the only weird feature I use in vim

from gocode.

ok, I'll figure out it later. :)

from gocode.

was fixed by pull request 50

from gocode.