Closed GoogleCodeExporter closed 9 years ago
GoogleCodeExporter
commented
9 years ago I cannot reproduce it. Would you be able to run Vim inside gdb or under
valgrind, to find out where the crash happens?Original comment by brammool...@gmail.com on 11 Jun 2014 at 6:20
GoogleCodeExporter
commented
9 years ago Here is the output from valgrind. The binary is stripped, so I hope it's not
too useless.Original comment by amcn...@google.com on 11 Jun 2014 at 6:36
Attachments:
GoogleCodeExporter
commented
9 years ago I can sometimes reproduce it. This patch fixes the crash for me:
diff --git a/src/window.c b/src/window.c
--- a/src/window.c
+++ b/src/window.c
@@ -4721,6 +4721,8 @@ win_alloc_lines(wp)
win_free_lsize(wp)
win_T *wp;
{
+ if (wp == NULL)
+ return;
vim_free(wp->w_lines);
wp->w_lines = NULL;
}
There is however some other strange going on. Half of the times I run
./vim -N -g -f --noplugin -u /tmp/vimrc file.c
the window opens fine, but Vim seems to get confused about the screensize. The
last line is not drawn correctly. If I do :set number, it jumps from 26 in the
second last line to 32 in the last line.Original comment by chrisbr...@googlemail.com on 11 Jun 2014 at 7:47
GoogleCodeExporter
commented
9 years ago 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.Original comment by brammool...@gmail.com on 12 Jun 2014 at 9:43
GoogleCodeExporter
commented
9 years ago fixed by 7.4.235Original comment by chrisbr...@googlemail.com on 2 Oct 2014 at 7:48
Original issue reported on code.google.com by
amcn...@google.comon 11 Jun 2014 at 4:51