Bram, I tend to abort long running z= commands by pressing <Ctrl-C>. This randomly crashed Vim for me, but until now, I couldn't reliably reproduce it, possibly it is timing dependent or influenced by some setting, I don't know.
However, I could just get a stacktrace as well as some valgrind logfiles
(see attached tar.xz file). Both logfiles are not very helpful. It seems
like Vim is allocating a lot of memory and finally gets killed. The
problem lies in the the add_sound_suggest() function and it seems, wlen
runs over. When gdb caught SEGV, it was at some value of above 21000.
Here is a patch, that makes sure, wlen doesn't increment over MAXWLEN
and fixes it for me. So please include it.
diff --git a/src/spell.c b/src/spell.c
--- a/src/spell.c
+++ b/src/spell.c
@@ -13382,6 +13382,10 @@
wordcount = 0;
for (;;)
{
+ if (wlen > MAXWLEN)
+ /* safety check */
+ break;
+
i = 1;
if (wordcount == orgnr && byts[n + 1] == NUL)
break; /* found end of word */
regards,
Christian
--
Pflicht des Historikers, das Wahre vom Falschen, das Gewisse vom
Ungewissen, das Zweifelhafte vom Verwerflichen zu unterscheiden.
-- Goethe, Maximen und Reflektionen, Nr. 432
--
--
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/groups/opt_out.
gdb_valgrind_log.tar.xz
Description: Binary data
