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