Charles E Campbell wrote:
Bram Moolenaar wrote:
Charles Campbell wrote:
Charles Campbell wrote:
[email protected] wrote:
Comment #4 on issue 230 by [email protected]: "Vim: Caught deadly
signal SEGV"
http://code.google.com/p/vim/issues/detail?id=230
The errors in the libfontconfig.so look like a library problem:
reading 4 bytes where there are only 2. Because of alignment this
probably does not cause a crash.
The error below update_screen() is most likely what causes the
crash. Can't see what happens there from this info though.
I tried this problem out: gvim -u junk.vim -U NONE macos (where
"junk.vim" has the two lines the poster mentioned)
* used binary compiled from an older machine: gvim -u junk.vim -U NONE
macos
- got a crash and no status line
- gdb doesn't track gvim after gvim "separates" from the console
(ie. becomes its own process)
- binary wasn't compiled for debugging and was stripped
* recompiled vim for debugging and no stripping
- no crash, has status line
- valgrind reported no problems
I'm going to go and update with the new patches now...
Hmm, apparently I was using an oddball version of vim that wasn't
completely patched. So I've now rebuilt vim 7.4.320; using
valgrind --log-file=gvim.out gvim -u junk.vim -U NONE macos
The attached file contains the log. Vim crashed eventually, but it
took
a lot of j and k motions, sprinkled with the occasional L and G to
get it.
Would one of you tell me how best to apply gdb to gvim? I suppose I
could run gvim and then attach gdb to it after its started.
You have to run the GUI in the foreground. In gdb use "run -f".
Looks like somehow the data structures allocated for the screen don't
match with the screen size. That's weird.
It probably matters what the terminal size is you start with. Was that
24 x 80?
The terminal I used to kick off gvim was 253x37.
I'm using vim 7.4.320 on a Scientific Linux 6.5 system.
My configure command is:
./configure --with-features=huge
--enable-gui=gtk2 --enable-perlinterp
--enable-pythoninterp --enable-cscope
I tried this operation again with different initial terminal sizes.
* terminal: 125x37 -- I get no status line and eventually I get a SIGSEGV
* terminal: 50 x 20 -- I get a status line and haven't seen a SIGSEGV
* I restored the terminal to 125x37, but this time I used the mouse
to grab the corner and expand the gvim screen. I pull it down just one
line and the status line appears, and I haven't been able to get it to
core dump based on cursor movement.
Regards,
Chip
--
--
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
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
