unable to run cscope

1,266 views
Skip to first unread message

FlashBurn

unread,
Mar 12, 2013, 10:20:45 AM3/12/13
to vim...@googlegroups.com
I have installed cscope(http://cscope.sourceforge.net/) and added cscope_maps.vim (https://github.com/chazy/cscope_maps) as one of my plugins.
I started going through a tutorial on how to use the cscope (http://cscope.sourceforge.net/cscope_vim_tutorial.html), but unfortunately I hit a problem right from the start. Here is the step where I'm stuck:

Put the cursor over a C symbol that is used in several places in your program. Type "CTRL-\ s" (Control-backslash, then just 's') in quick succession, and you should see a menu at the bottom of your Vim window showing you all the uses of the symbol in the program. Select one of them and hit enter, and you'll jump to that use. As with ctags, you can hit "CTRL-t" to jump back to your original location before the search (and you can nest searches and CTRL-t will unwind them one at a time).

When I do that, I'm getting the following error:
E567: No cscope connections. I looked for help for E567 but it just shows me help for cs-find. Has anybody encountered this problem before and managed to fix it?

Any help is appreciated?
Here is how my vim was compiled:

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Mar 4 2013 10:41:26)
MS-Windows 32-bit console version
Included patches: 1-843
Compiled by SHAFIGULINR@USTRA-ISD3
Big version without GUI. Features included (+) or not (-):
+arabic +ex_extra -mouseshape +tag_binary
+autocmd +extra_search +multi_byte_ime/dyn +tag_old_static
-balloon_eval +farsi +multi_lang -tag_any_white
-browse +file_in_path -mzscheme -tcl
++builtin_terms +find_in_path -netbeans_intg -tgetent
+byte_offset +float +path_extra -termresponse
+cindent +folding +perl/dyn +textobjects
+clientserver -footer +persistent_undo +title
+clipboard +gettext/dyn -postscript -toolbar
+cmdline_compl -hangul_input +printer +user_commands
+cmdline_hist +iconv/dyn -profile +vertsplit
+cmdline_info +insert_expand -python +virtualedit
+comments +jumplist +python3/dyn +visual
+conceal +keymap +quickfix +visualextra
+cryptv +langmap +reltime +viminfo
+cscope +libcall +rightleft +vreplace
+cursorbind +linebreak -ruby +wildignore
+cursorshape +lispindent +scrollbind +wildmenu
+dialog_con +listcmds +signs +windows
+diff +localmap +smartindent +writebackup
+digraphs -lua -sniff -xfontset
-dnd +menu +startuptime -xim
-ebcdic +mksession +statusline -xterm_save
+emacs_tags +modify_fname -sun_workshop -xpm_w32
+eval +mouse +syntax
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\_vimrc"
2nd user vimrc file: "$VIM\_vimrc"
user exrc file: "$HOME\_exrc"
2nd user exrc file: "$VIM\_exrc"
Compilation: gcc -Iproto -DWIN32 -DWINVER=0x0500 -D_WIN32_WINNT=0x0500 -DHAVE_PATHDEF -DFEAT_BIG -DHAVE_GETTEXT -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT -DFEAT_OLE -DFEAT_CSCOPE -DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DDYNAMIC_ICONV -pipe -w -march=i386 -Wall -IC:/Perl/lib/Core -DFEAT_PERL -LC:/Perl/lib/Core -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL="perl512.dll" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 -DFEAT_XPM_W32 -I xpm/x86/include -I xpm/x86/../include -O3 -fomit-frame-pointer -freg-struct-return -s
Linking: gcc -Iproto -DWIN32 -DWINVER=0x0500 -D_WIN32_WINNT=0x0500 -DHAVE_PATHDEF -DFEAT_BIG -DHAVE_GETTEXT -DHAVE_LOCALE_H -DDYNAMIC_GETTEXT -DFEAT_OLE -DFEAT_CSCOPE -DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DDYNAMIC_ICONV -pipe -w -march=i386 -Wall -IC:/Perl/lib/Core -DFEAT_PERL -LC:/Perl/lib/Core -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL="perl512.dll" -DFEAT_PYTHON3 -DDYNAMIC_PYTHON3 -DFEAT_XPM_W32 -I xpm/x86/include -I xpm/x86/../include -O3 -fomit-frame-pointer -freg-struct-return -s -mwindows -o gvim.exe -lkernel32 -luser32 -lgdi32 -ladvapi32 -lcomdlg32 -lcomctl32 -lversion -L xpm/x86/lib -lXpm -loleaut32 -lstdc++ -lole32 -luuid

Nazri Ramliy

unread,
Mar 12, 2013, 10:42:48 AM3/12/13
to vim...@googlegroups.com
On Tue, Mar 12, 2013 at 10:20 PM, FlashBurn <rail.sh...@gmail.com> wrote:
> When I do that, I'm getting the following error:
> E567: No cscope connections. I looked for help for E567 but it just shows me help for cs-find. Has anybody encountered this problem before and managed to fix it?

You need to add a "cscope connection", like this:

:cscope add /usr/local/cdb/cscope.out

See :help cs for more examples.

Nazri

FlashBurn

unread,
Mar 12, 2013, 11:45:46 AM3/12/13
to vim...@googlegroups.com

Thank you, it worked.

Reply all
Reply to author
Forward
0 new messages