Dominique wrote:
> > Patch 8.2.0133
> > Problem: Invalid memory access with search command.
> > Solution: When :normal runs out of characters in bracketed paste mode
> > break
> > out of the loop.(closes #5511)
>
> The test passes, but vim-8.2.133 still crashes when doing:
>
> $ ./vim --clean -e -s -c 'exe "norm /\x80PS"'
> Segmentation fault (core dumped)
>
> Running with valgrind gives:
>
> ==8332== Memcheck, a memory error detector
> ==8332== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
> ==8332== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
> ==8332== Command: ./vim --clean -e -s -c exe\ "norm\ /\\x80PS"
> ==8332==
> ==8332== Invalid read of size 1
> ==8332== at 0x4C32CF2: strlen (in
> /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==8332== by 0x1747A4: bracketed_paste (edit.c:4945)
> ==8332== by 0x1B8E05: getcmdline_int (ex_getln.c:2266)
Ah, that's why I didn't find it with valgrind. Explicitly resetting
t_PE works to reproduce it.
--
"The future's already arrived - it's just not evenly distributed yet."
-- William Gibson
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/202001202012.00KKCreH013620%40masaka.moolenaar.net.
