Lcd wrote:
> Scenario:
>
> (1) set a loclist:
>
> call setloclist(0, list)
>
> (2) at some point later replace the list:
>
> call setloclist(0, other_list, 'r')
>
> (3) open the quickfix window
>
> lopen
>
> (4) switch to the quickfix window and press Enter to jump to an error:
>
> .ll
>
> The result is a read from free'd memory; valgrind trace included
> below. It's easy to make Vim crash from there, but the stack trace
> doesn't reveal any additional information.
>
> Sadly, this is not consistently reproducible. I can trigger it in
> syntastic, but I can't seem to get the same result in a simple test
> file.
I have sent out patch 7.4.379. Can you check that this fixes the
problem?
--
If all you have is a hammer, everything looks like a nail.
When your hammer is C++, everything begins to look like a thumb.
-- Steve Hoflich, comp.lang.c++
/// 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/d/optout.
