Christian Brabandt wrote:
> 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.
Thanks. I'll put it somewhere near the top of the todo list.
--
BEDEVERE: Wait. Wait ... tell me, what also floats on water?
ALL: Bread? No, no, no. Apples .... gravy ... very small rocks ...
ARTHUR: A duck.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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.
