Christian Brabandt wrote:

> On Mi, 09 Feb 2011, Bram Moolenaar wrote:
> 
> > I can't reproduce it.  The MyTabLine() function is missing.  Also, you
> > need to start vim with "-u NONE" to exclude all kinds of other stuff.
> > 
> > And make sure you run the latest Vim, including patch 7.3.112.
> > The line numbers in your valgrind output don't match my source, please
> > quote the actual source lines.
> > 
> > I also tried the instructions in your other message, didn't work either.
> 
> Sorry, I don't know what is wrong then. All I do, I described in 
> Message-ID: <[email protected]>
> I don't know how to provide more useful information than that:
> 
> :version
> VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Feb  9 2011 19:14:18)
> Included patches: 1-118
> Compiled by chrisbra@r500vm
> Huge version with GTK2 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 +fork() +gettext
> -hangul_input +iconv +insert_expand +jumplist +keymap +langmap +libcall
> +linebreak +lispindent +listcmds +localmap -lua +menu +mksession +modify_fname
> +mouse +mouseshape +mouse_dec +mouse_gpm -mouse_jsbterm +mouse_netterm
> -mouse_sysmouse +mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg
> -osfiletype +path_extra -perl +persistent_undo +postscript +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 +terminfo +termresponse +textobjects 
> +title
>  +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo
> +vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset +xim
> +xsmp_interact +xterm_clipboard -xterm_save
>    system vimrc file: "$VIM/vimrc"
>      user vimrc file: "$HOME/.vimrc"
>       user exrc file: "$HOME/.exrc"
>   system gvimrc file: "$VIM/gvimrc"
>     user gvimrc file: "$HOME/.gvimrc"
>     system menu file: "$VIMRUNTIME/menu.vim"
>   fall-back for $VIM: "/home/chrisbra/local/share/vim"
> Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread 
> -I/usr/
> include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 
> -I/usr/include
> /cairo -I/usr/include/pango-1.0 -I/usr/include/gio-unix-2.0/ 
> -I/usr/include/pixm
> an-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/glib-2.0 
> -I
> /usr/lib/glib-2.0/include     -g -O2 -D_FORTIFY_SOURCE=1
> Linking: gcc   -L/usr/local/lib -Wl,--as-needed -o vim   -pthread 
> -lgtk-x11-2.0
> -lgdk-x11-2.0 -latk-1.0 -lpangoft2-1.0 -lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 
> -lc
> airo -lgio-2.0 -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 
> -lgmodule-2.0 -
> lgthread-2.0 -lrt -lglib-2.0   -lSM -lICE -lXpm -lXt -lX11 -lXdmcp -lSM -lICE 
> -l
> m -lncurses -lnsl  -lselinux -lacl -lattr -lgpm
> 
> System:
> Linux r500vm 2.6.32-5-686 #1 SMP Fri Dec 10 16:12:40 UTC 2010 i686 GNU/Linux
> (Debian Squeeze in a vmware)
> 
> gcc (Debian 4.4.5-8) 4.4.5
> Copyright (C) 2010 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> nterestingly, I get two different results, when running from gdb:
> 1) when compiling with DEBUG:
> (gdb) bt
> #0  0x08057ccf in build_stl_str_hl (wp=0x8219808,
>     out=0xbfffd8e0 " 2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  
> 18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  
> 37  38  39  40  41  42  43  44  45  46  47  48  49  50  51 abLabel("..., 
> outlen=4096,
>     fmt=0x8270c98 "%!MyTabLine()", use_sandbox=0, fillchar=32, maxwidth=80,
>     hltab=0xbfffeb60, tabtab=0xbfffe8e0) at buffer.c:3470
> #1  0x08158f2c in win_redr_custom (wp=0x0, draw_ruler=<value optimized out>)
>     at screen.c:6531
> #2  0x0815a51e in draw_tabline () at screen.c:9713
> #3  0x08166615 in update_screen (type=40) at screen.c:465
> #4  0x080e49f5 in main_loop (cmdwin=0, noexmode=0) at main.c:1161
> #5  0x080e7d75 in main (argc=75, argv=0xbffff174) at main.c:961
> 
> 
> 2) when compiling without DEBUG:
> Program received signal SIGSEGV, Segmentation fault.
> build_stl_str_hl (wp=0x821a808,
>     out=0xbfffd8e0 " 2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  
> 18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  
> 37  38  39  40  41  42  43  44  45  46  47  48  49  50  51  52  53 "..., 
> outlen=4096,
>     fmt=0x8271c98 "%!MyTabLine()", use_sandbox=0, fillchar=32, maxwidth=80,
> ---Type <return> to continue, or q <return> to quit---
>     hltab=0xbfffeb60, tabtab=0xbfffe8e0) at buffer.c:3461
> 3461        for (s = usefmt; *s; )
> (gdb) bt
> #0  build_stl_str_hl (wp=0x821a808,
>     out=0xbfffd8e0 " 2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  
> 18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  
> 37  38  39  40  41  42  43  44  45  46  47  48  49  50  51  52  53 "..., 
> outlen=4096,
>     fmt=0x8271c98 "%!MyTabLine()", use_sandbox=0, fillchar=32, maxwidth=80,
>     hltab=0xbfffeb60, tabtab=0xbfffe8e0) at buffer.c:3461
> #1  0x081590cc in win_redr_custom (wp=0x0, draw_ruler=<value optimized out>)
>     at screen.c:6531
> #2  0x0815a6be in draw_tabline () at screen.c:9713
> #3  0x081667b5 in update_screen (type=40) at screen.c:465
> #4  0x080e4b95 in main_loop (cmdwin=0, noexmode=0) at main.c:1161
> #5  0x080e7f15 in main (argc=75, argv=0xbffff174) at main.c:961
> (gdb)
> 
> But then again, I just don't understand gdb too well.

It's certainly worth learning some gdb commands.

Use the "print" command to find out the value of "usefmt".  It appears
that "s" is invalid, goes over the end of the format.

You can also put a breakpoint in build_stl_str_hl() and step through it
to see what's going on.  Use "next" to step over a function call.

-- 
Your fault: core dumped

 /// Bram Moolenaar -- [email protected] -- 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

Raspunde prin e-mail lui