On Saturday, June 2, 2012 7:15:11 PM UTC+7, Dominique Pelle wrote:
> char101 
>  wrote:
> 
> > Hi,
> >
> > Lately I have been getting rather frequent crash with gvim. It seems to 
> > happen randomly. I do have a debug info of the crash. Unfortunately I 
> > cannot find what is causing the crash by looking at the debug info. Can 
> > anyone help me finding the problem that made gvim crash?
> >
> > Crash info:
> >
> > (c70.1018): Access violation - code c0000005 (!!! second chance !!!)
> > eax=01cfb950 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000 
> > edi=0012e418
> > eip=00438bed esp=0012dab0 ebp=0012df24 iopl=0         nv up ei pl nz na pe 
> > nc
> > cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             
> > efl=00000206
> > gvim!call_user_func+0x8d:
> > 00438bed 8903            mov     dword ptr [ebx],eax  
> > ds:0023:00000000=????????
> > 0:000> ub
> > gvim!call_user_func+0x6c [eval.c @ 22225]:
> > 00438bcc 6808060000      push    608h
> > 00438bd1 e87a7d0600      call    gvim!lalloc (004a0950)
> > 00438bd6 8b0d08db5500    mov     ecx,dword ptr [gvim!current_funccal 
> > (0055db08)]
> > 00438bdc 8b1508df5500    mov     edx,dword ptr [gvim!ex_nesting_level 
> > (0055df08)]
> > 00438be2 8bd8            mov     ebx,eax
> > 00438be4 8b4508          mov     eax,dword ptr [ebp+8]
> > 00438be7 56              push    esi
> > 00438be8 68fc4b5500      push    offset gvim!dbg_breakp (00554bfc)
> >
> > It seems that since ebx is 0, vim is trying to access zero pointer. But I 
> > cannot find which pointer is it.
> >
> > Source code where the crash happen
> >
> >    fc = (funccall_T *)alloc(sizeof(funccall_T));
> >    fc->caller = current_funccal;
> >    current_funccal = fc;
> >    fc->func = fp;
> >    fc->rettv = rettv;
> >    rettv->vval.v_number = 0;
> >    fc->linenr = 0;
> >    fc->returned = FALSE;
> >    fc->level = ex_nesting_level;
> >    /* Check if this function has a breakpoint. */
> >    fc->breakpoint = dbg_find_breakpoint(FALSE, fp->uf_name, (linenr_T)0); 
> > <--- crash here
> >    fc->dbg_tick = debug_tick;
> 
> 
> Which version of Vim are you using?  (output of :version)
> 
> Several patches since official version 7.3 fix crashes.
> Latest version is Vim-7.3.538.

Hi,

I am using the latest version. But the random crash happens since several 
months ago. I don't remember exactly when since it happens randomly. I am also 
getting memory allocation fail randomly too. I does not happens frequently, 
maybe once a week.

This is the outout of version

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jun  2 2012 13:20:10)
MS-Windows 32-bit GUI version
Included patches: 1-538
Compiled by Charles@SOLARIS
Normal version with GUI.  Features included (+) or not (-):
-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_gui +diff +digraphs -dnd -ebcdic 
-emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path +find_in_path 
+float +folding -footer -gettext -hangul_input 
-iconv +insert_expand +jumplist -keymap -langmap +libcall +linebreak 
+lispindent +listcmds +localmap +lua +menu +mksession 
+modify_fname +mouse +mouseshape +multi_byte -multi_lang -mzscheme 
-netbeans_intg -ole +path_extra -perl -persistent_undo 
-printer -profile +python -python3 +quickfix +reltime -rightleft -ruby 
+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 
   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"
  system gvimrc file: "$VIM\gvimrc"
    user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$VIM\_gvimrc"
    system menu file: "$VIMRUNTIME\menu.vim"
Compilation: cl -c /W3 /nologo  -I. -Iproto -DHAVE_PATHDEF -DWIN32         
-DFEAT_AUTOCHDIR -DFEAT_SIGNS -DFEAT_CONCEAL -DWINVER=0x0501 
-D_WIN32_WINNT=0x0501  /Fo.\ObjGUY/ /O2 /GS- /fp:fast /GL -DNDEBUG /arch:SSE2 
/MD -DFEAT_MBYTE -DFEAT_GUI_W32 -DFEAT_LUA -DFEAT_PYTHON -DFEAT_NORMAL 
/Fd.\ObjGUY/ /Zi
Linking: link /RELEASE /nologo /subsystem:windows /OPT:REF /LTCG:STATUS 
oldnames.lib kernel32.lib advapi32.lib shell32.lib gdi32.lib  comdlg32.lib 
ole32.lib uuid.lib /machine:i386 /nodefaultlib /DELAYLOAD:comdlg32.dll 
/DELAYLOAD:ole32.dll DelayImp.lib gdi32.lib version.lib   winspool.lib 
comctl32.lib advapi32.lib shell32.lib  /machine:i386 /nodefaultlib msvcrt.lib   
user32.lib uxtheme.lib comctl32.lib pnglib.lib   
"P:\@editor\vim\app\lua\lib\lua51.lib" 
P:\@editor\vim\app\python\libs\python27.lib /PDB:gvim.pdb -debug

-- 
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

Raspunde prin e-mail lui