Mercurial > vim
diff src/edit.c @ 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 | 3e5166df3004 |
children | 057c26b5c33a |
line wrap: on
line diff
--- a/src/edit.c +++ b/src/edit.c @@ -5013,7 +5013,7 @@ ins_tab(void) mch_memmove(newp + col, ptr + i, curbuf->b_ml.ml_line_len - col - i); - if (curbuf->b_ml.ml_flags & ML_LINE_DIRTY) + if (curbuf->b_ml.ml_flags & (ML_LINE_DIRTY | ML_ALLOCATED)) vim_free(curbuf->b_ml.ml_line_ptr); curbuf->b_ml.ml_line_ptr = newp; curbuf->b_ml.ml_line_len -= i; @@ -5232,10 +5232,10 @@ ins_copychar(linenr_T lnum) } // try to advance to the cursor column + validate_virtcol(); temp = 0; line = ptr = ml_get(lnum); prev_ptr = ptr; - validate_virtcol(); while ((colnr_T)temp < curwin->w_virtcol && *ptr != NUL) { prev_ptr = ptr;