Christian J. Robinson wrote:
> I don't know if this is related to the crash bug I reported a while
> ago because ch_open() didn't return its own variable type at that
> time. Nevertheless, it was difficult to find the specific sequence
> that would reliably cause a crash without extraneous VimL code
> confusing things.
>
> This is a Perl script and a Vim script. Place them both in the same
> directory and source channelcrash.vim and Vim should crash
> entirely--at least it does for me under Windows.
>
> It appears that the culprit is an unlet on the variable storing the
> descriptor returned by ch_open(), within a message handling callback.
Thanks. I converted this to the channel_test and could reproduce the
crash. Turns out after the callback is invoked the channel pointer is
used even though it was already freed. I'll fix that. Nice catch!
--
hundred-and-one symptoms of being an internet addict:
264. You turn to the teletext page "surfing report" and are surprised that it
is about sizes of waves and a weather forecast for seaside resorts.
/// 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.
