On May 2, 7:32 pm, Kazuo Teramoto <[email protected]> wrote:
> On Sat, May 2, 2009 at 8:09 PM, Kazuo Teramoto <[email protected]> wrote:
> > I'm getting segmentation faults when setting the guidecolumn to any number
>
> > The gdb backtrace output is:
>
> > -------------------------------------------
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x00000000005374fa in showruler (always=0) at screen.c:9482
> > 9482 <le if ((*p_stl != NUL || *curwin->w_p_stl != NUL) &&
> > curwin->w_status_height)
> > (gdb) bt
> > #0 0x00000000005374fa in showruler (always=0) at screen.c:9482
> > #1 0x00000000004a7154 in main_loop (cmdwin=0, noexmode=0) at main.c:1141
> > #2 0x00000000004a6d1f in main (argc=2, argv=0x7fff53767528) at main.c:939
> > -------------------------------------------
>
> More info. The relevant variables:
> --------------------------------------
> (gdb) print p_stl
> $11 = (char_u *) 0x126ebc0 ""
> (gdb) print *p_stl
> $12 = 0 '\0'
> (gdb) print curwin->w_onebuf_opt->wo_stl (curwin->w_p_stl)
> $13 = (char_u *) 0x0
> (gdb) print curwin->w_status_height
> $14 = 0
> -------------------------------------
>
> My C knowledge is limited and my gdb experience too so let me know if
> I can give some more info.
>
> --
> «Dans la vie, rien n'est à craindre, tout est à comprendre»
> Marie Sklodowska Curie.
Are you running on Linux/Unix? I don't have Linux/Unix and I have only
tested with Windows. Can someone else who has access to *nix please
take a look? The crash seems to be in an area outside of the patch
changes but can very well be related to the patch.
Thanks
_Lone
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
