view src/testdir/test_job_fails.vim @ 25885:7c640ad754fb v8.2.3476

patch 8.2.3476: renaming a buffer on startup may cause using freed memory Commit: https://github.com/vim/vim/commit/d3710cf01ef6ab1b2f233866ff01dab76686f642 Author: Bram Moolenaar <Bram@vim.org> Date: Mon Oct 4 23:13:13 2021 +0100 patch 8.2.3476: renaming a buffer on startup may cause using freed memory Problem: Renaming a buffer on startup may cause using freed memory. Solution: Check if the buffer is used in a window. (closes https://github.com/vim/vim/issues/8955)
author Bram Moolenaar <Bram@vim.org>
date Tue, 05 Oct 2021 00:15:04 +0200
parents 08940efa6b4e
children
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 exits right away it's not a real leak.

source check.vim

func Test_job_start_fails()
  CheckFeature 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
endfunc

" vim: shiftwidth=2 sts=2 expandtab