Mercurial > vim
view src/testdir/test_vim9_fails.vim @ 28678:a16dae0be398 v8.2.4863
patch 8.2.4863: accessing freed memory in test without the +channel feature
Commit: https://github.com/vim/vim/commit/c9af617ac62b15bfcbbfe8c54071146e2af01f65
Author: Bram Moolenaar <Bram@vim.org>
Date: Wed May 4 16:46:54 2022 +0100
patch 8.2.4863: accessing freed memory in test without the +channel feature
Problem: Accessing freed memory in test without the +channel feature.
(Dominique Pell?)
Solution: Do not generted PUSHCHANNEL or PUSHJOB if they are not
implemented. (closes #10350)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Wed, 04 May 2022 18:00:04 +0200 |
parents | b94ef0b282f1 |
children | 54e36d01847b |
line wrap: on
line source
" Test for Vim9 script with failures, causing memory leaks to be reported. " The leaks happen after a fork() and can be ignored. source check.vim def Test_assignment() if !has('channel') CheckFeature channel else var chan1: channel var job1: job var job2: job = job_start('willfail') endif enddef " Unclear why this test causes valgrind to report problems. def Test_job_info_return_type() if !has('job') CheckFeature job else var job: job = job_start(&shell) var jobs = job_info() assert_equal('list<job>', typename(jobs)) assert_equal('dict<any>', typename(job_info(jobs[0]))) job_stop(job) endif enddef