On Oct 14, 12:13 pm, frankjas <[EMAIL PROTECTED]> wrote:
> I have been encountering an intermittent coredump ...
>
> I rebuilt vim from source with symbols after I stumbled on a
> reproduceable test case today...
Brilliant.
> follows. It looks like the field uh_next_alt is being corrupted. Often
> in the backtrace it also contains the value 0x11.
>
> I can write up the
> exact steps to reproduce this error for anyone interested/capable of
> debugging this error.
Yes, please. An early step will be to try it with an up to date
version of vim,
which is at 7.2.025, some hundreds of fixes after 7.1.138.
Regards, John
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
