On 9 July 2016, Dominique Pellé <[email protected]> wrote:
> LCD 47 <[email protected]> wrote:
>
> > On 9 July 2016, Christian Brabandt <[email protected]> wrote:
> >> On Fr, 08 Jul 2016, LCD 47 wrote:
> >>
> >> > Not recent, but do you remember the problem introduced by
> >> > 1640? It's still with us. _shrug_
> >>
> >> I don't follow. That was a bugfix for a crash and I believe it
> >> fixed a crash that you reported some time ago or so about accessing
> >> invalid memory when loading a quickfix item.
> >
> > Patch 1640 was a fix for an unrelated crash. It also "fixed" a
> > crash I reported earlier, by making it illegal to set loclists from
> > autocmds.
> >
> > As I explained at the time, that was the wrong fix, and it
> > affected a few existing plugins. I suggested a different approach,
> > but by then everybody was too tired of the discussion to try to
> > consider what I was saying. _shrug_
> >
> > /lcd
>
>
> Hi Lcd
>
> Everybody wants to help, but the problem is, nobody knows how to
> reproduce the crash that you describe. Can you post a script that
> makes Vim crash? Or can you try to reproduce it with valgrind to have
> more information.
There is no crash any longer. I have a problem with the fix adopted
for a (now well-understood) crash, not with the crash itself.
/lcd
--
--
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.
