Mercurial > vim
view src/testdir/test_job_fails.vim @ 17417:aa4532c1d001 v8.1.1707
patch 8.1.1707: Coverity warns for possibly using a NULL pointer
commit https://github.com/vim/vim/commit/cfdbc5adde49cbab939e8164555ed0b8d9ce000b
Author: Bram Moolenaar <Bram@vim.org>
Date: Wed Jul 17 21:27:52 2019 +0200
patch 8.1.1707: Coverity warns for possibly using a NULL pointer
Problem: Coverity warns for possibly using a NULL pointer.
Solution: Change the logic to make sure no NULL pointer is used.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Wed, 17 Jul 2019 21:30:04 +0200 |
parents | 415185e2c970 |
children | b3e93a05c3ca |
line wrap: on
line source
" This test is in a separate file, because it usually causes reports for memory " leaks under valgrind. That is because when fork/exec fails memory is not " freed. Since the process exists right away it's not a real leak. source shared.vim func Test_job_start_fails() if has('job') let job = job_start('axdfxsdf') if has('unix') call WaitForAssert({-> assert_equal("dead", job_status(job))}) else call WaitForAssert({-> assert_equal("fail", job_status(job))}) endif endif endfunc