comparison runtime/doc/testing.txt @ 29340:fba9e366ced4 v9.0.0013

patch 9.0.0013: reproducing memory access errors can be difficult Commit: https://github.com/vim/vim/commit/fa4873ccfc10e0f278dc46f39d00136fab059b19 Author: Bram Moolenaar <Bram@vim.org> Date: Thu Jun 30 22:13:59 2022 +0100 patch 9.0.0013: reproducing memory access errors can be difficult Problem: Reproducing memory access errors can be difficult. Solution: When testing, copy each line to allocated memory, so that valgrind can detect accessing memory before and/or after it. Fix uncovered problems.
author Bram Moolenaar <Bram@vim.org>
date Thu, 30 Jun 2022 23:15:03 +0200
parents f8116058ca76
children 339fe2968690
comparison
equal deleted inserted replaced
29339:a023e3008ae3 29340:fba9e366ced4
266 The override is enabled when {val} is non-zero and removed 266 The override is enabled when {val} is non-zero and removed
267 when {val} is zero. 267 when {val} is zero.
268 Current supported values for {name} are: 268 Current supported values for {name} are:
269 269
270 {name} effect when {val} is non-zero ~ 270 {name} effect when {val} is non-zero ~
271 alloc_lines make a copy of every buffer line into allocated
272 memory, so that memory access errors can be found
273 by valgrind
271 autoload `import autoload` will load the script right 274 autoload `import autoload` will load the script right
272 away, not postponed until an item is used 275 away, not postponed until an item is used
273 char_avail disable the char_avail() function 276 char_avail disable the char_avail() function
274 nfa_fail makes the NFA regexp engine fail to force a 277 nfa_fail makes the NFA regexp engine fail to force a
275 fallback to the old engine 278 fallback to the old engine
285 ui_delay time in msec to use in ui_delay(); overrules a 288 ui_delay time in msec to use in ui_delay(); overrules a
286 wait time of up to 3 seconds for messages 289 wait time of up to 3 seconds for messages
287 uptime overrules sysinfo.uptime 290 uptime overrules sysinfo.uptime
288 vterm_title setting the window title by a job running in a 291 vterm_title setting the window title by a job running in a
289 terminal window 292 terminal window
290 ALL clear all overrides ({val} is not used) 293 ALL clear all overrides, except alloc_lines ({val} is
294 not used)
291 295
292 "starting" is to be used when a test should behave like 296 "starting" is to be used when a test should behave like
293 startup was done. Since the tests are run by sourcing a 297 startup was done. Since the tests are run by sourcing a
294 script the "starting" variable is non-zero. This is usually a 298 script the "starting" variable is non-zero. This is usually a
295 good thing (tests run faster), but sometimes changes behavior 299 good thing (tests run faster), but sometimes changes behavior