Mercurial > vim
view pixmaps/error.xpm @ 34257:8a91d18f1789 v9.1.0069
patch 9.1.0069: ScreenLines may not be correctly initialized, causing hang
Commit: https://github.com/vim/vim/commit/fd472655a93fd539c731c8daf3adc4e65ddce341
Author: Olaf Seibert <rhialto@falu.nl>
Date: Thu Feb 1 21:11:16 2024 +0100
patch 9.1.0069: ScreenLines may not be correctly initialized, causing hang
Problem: ScreenLines may not be correctly initialized, causing hang
(Olaf Seibert, after 9.0.0220)
Solution: always initialize ScreneLines when allocating a screen
(Olaf Seibert)
ScreenLines and related structures could be left uninitialized
causing a screen update to run into an infinite loop when using latin1
encoding.
Partly caused because by patch 9.0.0220, which makes mb_ptr2len return
zero for NUL
related: #12671
closes: #13946
Signed-off-by: Olaf Seibert <rhialto@falu.nl>
Signed-off-by: Christian Brabandt <cb@256bit.org>
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Thu, 01 Feb 2024 21:30:02 +0100 |
| parents | 3fc0f57ecb91 |
| children |
line wrap: on
line source
/* XPM */ static char * error_xpm[] = { /* width height ncolors cpp [x_hot y_hot] */ "34 34 4 1 0 0", /* colors */ " s none m none c none", ". s iconColor3 m black c #FF0000", "X s bottomShadowColor m black c #5D6069", "o s iconColor2 m white c #FFFFFF", /* pixels */ " ", " ........ ", " ............ ", " ................ ", " .................. ", " ....................X ", " ......................X ", " ........................X ", " .......o..........o.......X ", " ......ooo........ooo......X ", " ......ooooo......ooooo......X ", " .......ooooo....ooooo.......X ", " .........ooooo..ooooo.........X ", " ..........oooooooooo..........X ", " ...........oooooooo...........XX ", " ............oooooo............XX ", " ............oooooo............XX ", " ...........oooooooo...........XX ", " ..........oooooooooo..........XX ", " .........ooooo..ooooo.........XX ", " .......ooooo....ooooo.......XX ", " ......ooooo......ooooo......XX ", " ......ooo........ooo......XXX ", " .......o..........o.......XX ", " ........................XXX ", " ......................XXX ", " X....................XXX ", " X..................XXX ", " X................XXX ", " XX............XXXX ", " XX........XXXXX ", " XXXXXXXXXXX ", " XXXXXXX ", " "};