Created
April 10, 2017 10:23
-
-
Save ZyX-I/20cdeee0cd1812f85ce7afec7e909c82 to your computer and use it in GitHub Desktop.
PVS-studio reports for Neovim
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| www.viva64.com/en/w:1:1: error: Help: The documentation for all analyzer warnings is available here: http://www.viva64.com/en/w/. | |
| ./src/nvim/api/ui.c:57:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c:62:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c:128:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c:140:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c:145:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c:161:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c:175:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c:181:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c:187:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/buffer.h:108:1: error: V501 There are identical sub-expressions '& buf->changedtick_di.di_tv.vval.v_number' to the left and to the right of the '==' operator. | |
| ./src/nvim/api/buffer.c:173:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:189:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:285:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:291:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:306:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:319:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:332:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:342:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:359:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:364:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:377:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:382:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:629:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:680:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:698:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:753:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:757:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c:794:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c:63:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c:96:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c:120:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c:125:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c:130:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c:205:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c:260:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/eval/typval_encode.c.h:616:1: warning: V779 Unreachable code detected. It is possible that an error is present. | |
| ./src/nvim/eval/typval_encode.c.h:819:1: warning: V779 Unreachable code detected. It is possible that an error is present. | |
| ./src/nvim/api/private/helpers.c:563:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c:578:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c:593:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c:661:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c:715:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c:928:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c:216:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c:239:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c:264:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c:320:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c:332:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c:746:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c:753:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c:760:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c:768:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/window.c:66:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/window.c:80:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/window.c:85:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/window.c:134:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/window.c:179:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/digraph.c:1574:1: warning: V764 Possible incorrect order of arguments passed to 'getexactdigraph' function: 'char2' and 'char1'. | |
| ./src/nvim/digraph.c:1680:1: warning: V560 A part of conditional expression is always true: 1. | |
| ./src/nvim/digraph.c:1707:1: warning: V571 Recurring check. The '1' condition was already verified in line 1705. | |
| ./src/nvim/diff.c:89:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/diff.c:580:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/diff.c:1082:1: warning: V519 The 'curwin' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1065, 1082. | |
| ./src/nvim/diff.c:1131:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/diff.c:2379:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/buffer.c:752:1: warning: V560 A part of conditional expression is always false: swap_exists_action == 2. | |
| ./src/nvim/buffer.c:828:1: warning: V519 The 'swap_exists_action' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 791, 828. | |
| ./src/nvim/buffer.c:4409:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/event/libuv_process.c:41:1: warning: V641 The size of the '& proc->in->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/libuv_process.c:46:1: warning: V641 The size of the '& proc->out->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/libuv_process.c:51:1: warning: V641 The size of the '& proc->err->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/edit.c:3425:1: error: V595 The 'ptr' pointer was utilized before it was verified against nullptr. Check lines: 3425, 3433. | |
| ./src/nvim/edit.c:7015:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/edit.c:7021:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/eval/encode.c:256:1: error: V595 The 'state->li->li_tv.vval.v_string' pointer was utilized before it was verified against nullptr. Check lines: 256, 271. | |
| ./src/nvim/eval/typval_encode.c.h:494:1: error: V523 The 'then' statement is equivalent to the 'else' statement. | |
| ./src/nvim/event/process.c:84:1: warning: V641 The size of the '& proc->in->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/process.c:92:1: warning: V641 The size of the '& proc->out->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/process.c:100:1: warning: V641 The size of the '& proc->err->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/socket.c:76:1: warning: V641 The size of the '& watcher->uv.pipe.handle' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/socket.c:127:1: warning: V641 The size of the '& stream->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/stream.c:28:1: warning: V641 The size of the '& stream' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/stream.c:54:1: warning: V641 The size of the '& stream->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/ex_cmds2.c:1390:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/farsi.c:326:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions '!p_ri' and 'p_ri'. | |
| ./src/nvim/ex_cmds.c:4238:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_cmds.c:4364:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_cmds.c:5338:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/eval.c:1108:1: error: V557 Array overrun is possible. The 'prepare_vimvar' function processes value '34'. Inspect the first argument. Check lines: 'eval.c:1144'. | |
| ./src/nvim/eval.c:1145:1: error: V557 Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:1146:1: error: V557 Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:1121:1: error: V557 Array overrun is possible. The 'restore_vimvar' function processes value '34'. Inspect the first argument. Check lines: 'eval.c:1160'. | |
| ./src/nvim/eval.c:2751:1: warning: V560 A part of conditional expression is always true: !eap->skip. | |
| ./src/nvim/eval.c:2772:1: warning: V560 A part of conditional expression is always false: eap->skip. | |
| ./src/nvim/eval.c:3003:1: warning: V547 Expression 'd == ((void *) 0)' is always false. | |
| ./src/nvim/eval.c:6758:1: error: V557 Array overrun is possible. The 'VV_ERRORS' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:6760:1: error: V557 Array overrun is possible. The 'VV_ERRORS' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:6764:1: error: V557 Array overrun is possible. The 'VV_ERRORS' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:6800:1: error: V557 Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:6806:1: error: V557 Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:6809:1: error: V557 Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:7148:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/eval.c:7317:1: error: V583 The '?:' operator, regardless of its conditional expression, always returns one and the same value: * utf_ptr2char. | |
| ./src/nvim/eval.c:1108:1: error: V557 Array overrun is possible. The 'prepare_vimvar' function processes value '34'. Inspect the first argument. Check lines: 'eval.c:8380'. | |
| ./src/nvim/eval.c:1108:1: error: V557 Array overrun is possible. The 'prepare_vimvar' function processes value '35'. Inspect the first argument. Check lines: 'eval.c:8387'. | |
| ./src/nvim/eval.c:8389:1: error: V557 Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:8405:1: error: V557 Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:8407:1: error: V557 Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:8422:1: error: V557 Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:8430:1: error: V557 Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:1121:1: error: V557 Array overrun is possible. The 'restore_vimvar' function processes value '35'. Inspect the first argument. Check lines: 'eval.c:8441'. | |
| ./src/nvim/eval.c:1121:1: error: V557 Array overrun is possible. The 'restore_vimvar' function processes value '34'. Inspect the first argument. Check lines: 'eval.c:8442'. | |
| ./src/nvim/eval.c:8457:1: error: V557 Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:8458:1: error: V557 Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:8459:1: error: V557 Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:8509:1: error: V557 Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:8986:1: warning: V547 Expression 'n == ((void *) 0)' is always false. | |
| ./src/nvim/eval.c:9328:1: error: V557 Array overrun is possible. The 'VV_MOUSE_WIN' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:9329:1: error: V557 Array overrun is possible. The 'VV_MOUSE_WINID' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:9330:1: error: V557 Array overrun is possible. The 'VV_MOUSE_LNUM' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:9331:1: error: V557 Array overrun is possible. The 'VV_MOUSE_COL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:9371:1: error: V557 Array overrun is possible. The 'VV_MOUSE_WIN' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:9372:1: error: V557 Array overrun is possible. The 'VV_MOUSE_WINID' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:9373:1: error: V557 Array overrun is possible. The 'VV_MOUSE_LNUM' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:9374:1: error: V557 Array overrun is possible. The 'VV_MOUSE_COL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:9965:1: error: V557 Array overrun is possible. The 'VV_REG' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:10007:1: error: V557 Array overrun is possible. The 'VV_REG' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:12550:1: error: V536 Be advised that the utilized constant value is represented by an octal form. Oct: 0755, Dec: 493. | |
| ./src/nvim/eval.c:12785:1: error: V523 The 'then' statement is equivalent to the 'else' statement. | |
| ./src/nvim/eval.c:14311:1: error: V590 Consider inspecting this expression. The expression is excessive or contains a misprint. | |
| ./src/nvim/eval.c:14335:1: warning: V547 Expression 'varp != ((void *) 0)' is always true. | |
| ./src/nvim/eval.c:14879:1: warning: V547 Expression 'varp != ((void *) 0)' is always true. | |
| ./src/nvim/eval.c:17164:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/eval.c:18079:1: error: V557 Array overrun is possible. The 'VV_REG' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:18023:1: error: V557 Array overrun is possible. The 'set_vim_var_string' function processes value '31'. Inspect the first argument. Check lines: 'eval.c:18080'. | |
| ./src/nvim/eval.c:18093:1: error: V557 Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:18095:1: error: V557 Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:18108:1: error: V557 Array overrun is possible. The 'VV_THROWPOINT' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:18110:1: error: V557 Array overrun is possible. The 'VV_THROWPOINT' index is pointing beyond array bound. | |
| ./src/nvim/eval.c:19405:1: warning: V560 A part of conditional expression is always true: !eap->skip. | |
| ./src/nvim/eval.c:20994:1: warning: V507 Pointer to local array 'buf' is stored outside the scope of this array. Such a pointer will become invalid. | |
| ./src/nvim/eval.c:21053:1: warning: V614 Potentially uninitialized variable 'wait_start' used. Consider checking the first actual argument of the 'profile_sub_wait' function. | |
| ./src/nvim/eval.c:17954:1: error: V557 Array overrun is possible. The 'get_vim_var_list' function processes value '57'. Inspect the first argument. Check lines: 'eval.c:21736'. | |
| ./src/nvim/eval.c:18023:1: error: V557 Array overrun is possible. The 'set_vim_var_string' function processes value '62'. Inspect the first argument. Check lines: 'eval.c:21780'. | |
| ./src/nvim/eval.c:18023:1: error: V557 Array overrun is possible. The 'set_vim_var_string' function processes value '63'. Inspect the first argument. Check lines: 'eval.c:21781'. | |
| ./src/nvim/eval.c:18023:1: error: V557 Array overrun is possible. The 'set_vim_var_string' function processes value '64'. Inspect the first argument. Check lines: 'eval.c:21782'. | |
| ./src/nvim/fold.c:464:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/fold.c:1160:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/hardcopy.c:2589:1: warning: V519 The 'prt_do_conv' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 2587, 2589. | |
| ./src/nvim/getchar.c:1754:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/getchar.c:1797:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/getchar.c:1854:1: error: V705 It is possible that 'else' block was forgotten or commented out, thus altering the program's operation logics. | |
| ./src/nvim/ex_docmd.c:1099:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_docmd.c:1310:1: warning: V519 The 'p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1309, 1310. | |
| ./src/nvim/ex_docmd.c:1733:1: error: V536 Be advised that the utilized constant value is represented by an octal form. Oct: 0151, Dec: 105. | |
| ./src/nvim/ex_docmd.c:4109:1: warning: V547 Expression 'p != ((void *) 0)' is always true. | |
| ./src/nvim/ex_docmd.c:6006:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_docmd.c:6025:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_docmd.c:6228:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_docmd.c:6966:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_docmd.c:6985:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/fileio.c:746:1: warning: V560 A part of conditional expression is always false: !c. | |
| ./src/nvim/fileio.c:6391:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/main.c:489:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/main.c:663:1: error: V522 Dereferencing of the null pointer 'idx' might take place. The null pointer is passed into 'get_number_arg' function. Inspect the second argument. Check lines: 'main.c:1095'. | |
| ./src/nvim/mark.c:505:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/mark.c:1109:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/memfile.c:110:1: error: V547 Expression 'blocksize <= (2147483647 * 2U + 1U)' is always true. | |
| ./src/nvim/memline.c:621:1: error: V512 A call of the 'memchr' function will lead to underflow of the buffer 'b0p->b0_fname'. | |
| ./src/nvim/memline.c:3374:1: error: V595 The 'name' pointer was utilized before it was verified against nullptr. Check lines: 3374, 3379. | |
| ./src/nvim/message.c:1170:1: error: V517 The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 1170, 1173. | |
| ./src/nvim/message.c:1669:1: warning: V571 Recurring check. The '1' condition was already verified in line 1668. | |
| ./src/nvim/misc1.c:1822:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/misc1.c:1922:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/misc1.c:2158:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/move.c:2144:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/msgpack_rpc/helpers.c:574:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c:579:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c:584:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c:590:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c:596:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c:604:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c:611:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c:616:1: warning: V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/os/env.c:649:1: warning: V507 Pointer to local array 'exe_name' is stored outside the scope of this array. Such a pointer will become invalid. | |
| ./src/nvim/os/fileio.c:71:1: error: V501 There are identical sub-expressions to the left and to the right of the '!=' operator: kNone != kNone | |
| ./src/nvim/ops.c:2789:1: warning: V756 The 'i' counter is not used inside a nested loop. Consider inspecting usage of 'j' counter. | |
| ./src/nvim/ops.c:3818:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/normal.c:655:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c:719:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c:701:1: warning: V519 The 'State' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 699, 701. | |
| ./src/nvim/normal.c:838:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c:853:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c:969:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c:2342:1: error: V564 The '|' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '||' operator. | |
| ./src/nvim/normal.c:2694:1: error: V564 The '|' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '||' operator. | |
| ./src/nvim/normal.c:3518:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/normal.c:4044:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c:4376:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c:4433:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/normal.c:7617:1: error: V705 It is possible that 'else' block was forgotten or commented out, thus altering the program's operation logics. | |
| ./src/nvim/popupmnu.c:131:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/quickfix.c:861:1: warning: V547 Expression 'fmt_ptr != ((void *) 0)' is always true. | |
| ./src/nvim/quickfix.c:1769:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/quickfix.c:1828:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/quickfix.c:1840:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/quickfix.c:1889:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/quickfix.c:2729:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/quickfix.c:3285:1: error: V501 There are identical sub-expressions 'eap->cmdidx == CMD_llast' to the left and to the right of the '||' operator. | |
| ./src/nvim/quickfix.c:3340:1: error: V501 There are identical sub-expressions 'eap->cmdidx == CMD_lpfile' to the left and to the right of the '||' operator. | |
| ./src/nvim/quickfix.c:989:1: error: V522 Dereferencing of the null pointer 'buf' might take place. The null pointer is passed into 'qf_init_ext' function. Inspect the third argument. Check lines: 'quickfix.c:4420'. | |
| ./src/nvim/quickfix.c:4480:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/search.c:615:1: error: V502 Perhaps the '?:' operator works in a different way than it was expected. The '?:' operator has a lower priority than the '&&' operator. | |
| ./build/src/nvim/auto/options.generated.h:2583:1: error: V542 Consider inspecting an odd type cast: 'char' to 'unsigned char *'. | |
| ./src/nvim/option.c:3543:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/option.c:3768:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c:198:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c:213:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c:314:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c:388:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c:410:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c:432:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c:546:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c:575:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c:1020:1: warning: V571 Recurring check. The 'VIsual_active' condition was already verified in line 1019. | |
| ./src/nvim/screen.c:2453:1: warning: V512 A call of the 'memmove' function will lead to underflow of the buffer 'nextline'. | |
| ./src/nvim/screen.c:2591:1: error: V595 The 'cur' pointer was utilized before it was verified against nullptr. Check lines: 2591, 2597. | |
| ./src/nvim/screen.c:2789:1: warning: V560 A part of conditional expression is always true: n_extra == 0. | |
| ./src/nvim/screen.c:4535:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c:4548:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c:4561:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c:5339:1: warning: V560 A part of conditional expression is always false: l_enc_dbcs == 9932. | |
| ./src/nvim/screen.c:5381:1: warning: V560 A part of conditional expression is always false: l_enc_dbcs == 9932. | |
| ./src/nvim/screen.c:5548:1: error: V595 The 'cur' pointer was utilized before it was verified against nullptr. Check lines: 5548, 5559. | |
| ./src/nvim/screen.c:6108:1: warning: V560 A part of conditional expression is always false: l_enc_dbcs == 9932. | |
| ./src/nvim/screen.c:6193:1: warning: V560 A part of conditional expression is always false: l_enc_dbcs == 9932. | |
| ./src/nvim/shada.c:1280:1: warning: V581 The conditional expressions of the 'if' operators situated alongside each other are identical. Check lines: 1276, 1280. | |
| ./src/nvim/spell.c:2433:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/spell.c:3656:1: error: V512 A call of the 'memset' function will lead to underflow of the buffer 'sp'. | |
| ./src/nvim/terminal.c:1135:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/terminal.c:1187:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/tag.c:1229:1: error: V512 A call of the 'memset' function will lead to underflow of the buffer '& search_info'. | |
| ./src/nvim/tag.c:2539:1: warning: V519 The 'p_ic' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 2498, 2539. | |
| ./src/nvim/tui/tui.c:1070:1: warning: V641 The size of the '& data->output_handle' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/syntax.c:1000:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/syntax.c:1087:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/syntax.c:2183:1: error: V763 Parameter 'cur_si' is always rewritten in function body before being used. | |
| ./src/nvim/spellfile.c:2403:1: warning: V547 Expression 'aff_entry->ae_flags == ((void *) 0)' is always true. Pointer 'aff_entry->ae_flags' == NULL. | |
| ./src/nvim/undo.c:2407:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c:167:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c:456:1: warning: V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/window.c:1072:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c:1104:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c:1788:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c:3752:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c:4085:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c:4104:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c:4538:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c:5265:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c:5909:1: error: V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/regexp.c:2403:1: warning: V536 Be advised that the utilized constant value is represented by an octal form. Oct: '\033', Dec: 27. | |
| ./src/nvim/regexp.c:2928:1: error: V517 The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 2928, 2931. | |
| ./src/nvim/regexp.c:3057:1: error: V536 Be advised that the utilized constant value is represented by an octal form. Oct: 040, Dec: 32. | |
| ./src/nvim/regexp.c:6952:1: error: V595 The 'retval' pointer was utilized before it was verified against nullptr. Check lines: 6952, 6956. | |
| ./src/nvim/regexp_nfa.c:2778:1: error: V517 The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 2778, 2780. | |
| ./src/nvim/regexp_nfa.c:4416:1: warning: V536 Be advised that the utilized constant value is represented by an octal form. Oct: '\033', Dec: 27. | |
| ./test/functional/fixtures/tty-test.c:90:1: warning: V641 The size of the '& out' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./test/functional/fixtures/tty-test.c:151:1: warning: V641 The size of the '& tty' buffer is not a multiple of the element size of the type 'uv_stream_t'. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| www.viva64.com/en/w 1 err Help: The documentation for all analyzer warnings is available here: http://www.viva64.com/en/w/. | |
| ./src/nvim/api/ui.c 57 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c 62 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c 128 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c 140 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c 145 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c 161 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c 175 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c 181 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/ui.c 187 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/buffer.h 108 err V501 There are identical sub-expressions '& buf->changedtick_di.di_tv.vval.v_number' to the left and to the right of the '==' operator. | |
| ./src/nvim/api/buffer.c 173 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 189 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 285 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 291 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 306 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 319 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 332 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 342 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 359 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 364 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 377 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 382 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 629 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 680 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 698 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 753 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 757 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/buffer.c 794 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c 63 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c 96 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c 120 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c 125 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c 130 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c 205 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c 260 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/eval/typval_encode.c.h 616 warn V779 Unreachable code detected. It is possible that an error is present. | |
| ./src/nvim/eval/typval_encode.c.h 819 warn V779 Unreachable code detected. It is possible that an error is present. | |
| ./src/nvim/api/private/helpers.c 563 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c 578 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c 593 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c 661 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c 715 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/private/helpers.c 928 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c 216 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c 239 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c 264 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c 320 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c 332 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c 746 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c 753 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c 760 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/vim.c 768 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/window.c 66 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/window.c 80 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/window.c 85 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/window.c 134 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/api/window.c 179 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/digraph.c 1574 warn V764 Possible incorrect order of arguments passed to 'getexactdigraph' function: 'char2' and 'char1'. | |
| ./src/nvim/digraph.c 1680 warn V560 A part of conditional expression is always true: 1. | |
| ./src/nvim/digraph.c 1707 warn V571 Recurring check. The '1' condition was already verified in line 1705. | |
| ./src/nvim/diff.c 89 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/diff.c 580 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/diff.c 1082 warn V519 The 'curwin' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1065, 1082. | |
| ./src/nvim/diff.c 1131 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/diff.c 2379 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/buffer.c 752 warn V560 A part of conditional expression is always false: swap_exists_action == 2. | |
| ./src/nvim/buffer.c 828 warn V519 The 'swap_exists_action' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 791, 828. | |
| ./src/nvim/buffer.c 4409 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/event/libuv_process.c 41 warn V641 The size of the '& proc->in->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/libuv_process.c 46 warn V641 The size of the '& proc->out->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/libuv_process.c 51 warn V641 The size of the '& proc->err->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/edit.c 3425 err V595 The 'ptr' pointer was utilized before it was verified against nullptr. Check lines: 3425, 3433. | |
| ./src/nvim/edit.c 7015 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/edit.c 7021 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/eval/encode.c 256 err V595 The 'state->li->li_tv.vval.v_string' pointer was utilized before it was verified against nullptr. Check lines: 256, 271. | |
| ./src/nvim/eval/typval_encode.c.h 494 err V523 The 'then' statement is equivalent to the 'else' statement. | |
| ./src/nvim/event/process.c 84 warn V641 The size of the '& proc->in->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/process.c 92 warn V641 The size of the '& proc->out->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/process.c 100 warn V641 The size of the '& proc->err->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/socket.c 76 warn V641 The size of the '& watcher->uv.pipe.handle' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/socket.c 127 warn V641 The size of the '& stream->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/stream.c 28 warn V641 The size of the '& stream' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/event/stream.c 54 warn V641 The size of the '& stream->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/ex_cmds2.c 1390 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/farsi.c 326 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions '!p_ri' and 'p_ri'. | |
| ./src/nvim/ex_cmds.c 4238 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_cmds.c 4364 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_cmds.c 5338 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/eval.c 1108 err V557 Array overrun is possible. The 'prepare_vimvar' function processes value '34'. Inspect the first argument. Check lines: 'eval.c:1144'. | |
| ./src/nvim/eval.c 1145 err V557 Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 1146 err V557 Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 1121 err V557 Array overrun is possible. The 'restore_vimvar' function processes value '34'. Inspect the first argument. Check lines: 'eval.c:1160'. | |
| ./src/nvim/eval.c 2751 warn V560 A part of conditional expression is always true: !eap->skip. | |
| ./src/nvim/eval.c 2772 warn V560 A part of conditional expression is always false: eap->skip. | |
| ./src/nvim/eval.c 3003 warn V547 Expression 'd == ((void *) 0)' is always false. | |
| ./src/nvim/eval.c 6758 err V557 Array overrun is possible. The 'VV_ERRORS' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 6760 err V557 Array overrun is possible. The 'VV_ERRORS' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 6764 err V557 Array overrun is possible. The 'VV_ERRORS' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 6800 err V557 Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 6806 err V557 Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 6809 err V557 Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 7148 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/eval.c 7317 err V583 The '?:' operator, regardless of its conditional expression, always returns one and the same value: * utf_ptr2char. | |
| ./src/nvim/eval.c 1108 err V557 Array overrun is possible. The 'prepare_vimvar' function processes value '34'. Inspect the first argument. Check lines: 'eval.c:8380'. | |
| ./src/nvim/eval.c 1108 err V557 Array overrun is possible. The 'prepare_vimvar' function processes value '35'. Inspect the first argument. Check lines: 'eval.c:8387'. | |
| ./src/nvim/eval.c 8389 err V557 Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 8405 err V557 Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 8407 err V557 Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 8422 err V557 Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 8430 err V557 Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 1121 err V557 Array overrun is possible. The 'restore_vimvar' function processes value '35'. Inspect the first argument. Check lines: 'eval.c:8441'. | |
| ./src/nvim/eval.c 1121 err V557 Array overrun is possible. The 'restore_vimvar' function processes value '34'. Inspect the first argument. Check lines: 'eval.c:8442'. | |
| ./src/nvim/eval.c 8457 err V557 Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 8458 err V557 Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 8459 err V557 Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 8509 err V557 Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 8986 warn V547 Expression 'n == ((void *) 0)' is always false. | |
| ./src/nvim/eval.c 9328 err V557 Array overrun is possible. The 'VV_MOUSE_WIN' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 9329 err V557 Array overrun is possible. The 'VV_MOUSE_WINID' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 9330 err V557 Array overrun is possible. The 'VV_MOUSE_LNUM' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 9331 err V557 Array overrun is possible. The 'VV_MOUSE_COL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 9371 err V557 Array overrun is possible. The 'VV_MOUSE_WIN' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 9372 err V557 Array overrun is possible. The 'VV_MOUSE_WINID' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 9373 err V557 Array overrun is possible. The 'VV_MOUSE_LNUM' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 9374 err V557 Array overrun is possible. The 'VV_MOUSE_COL' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 9965 err V557 Array overrun is possible. The 'VV_REG' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 10007 err V557 Array overrun is possible. The 'VV_REG' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 12550 err V536 Be advised that the utilized constant value is represented by an octal form. Oct: 0755, Dec: 493. | |
| ./src/nvim/eval.c 12785 err V523 The 'then' statement is equivalent to the 'else' statement. | |
| ./src/nvim/eval.c 14311 err V590 Consider inspecting this expression. The expression is excessive or contains a misprint. | |
| ./src/nvim/eval.c 14335 warn V547 Expression 'varp != ((void *) 0)' is always true. | |
| ./src/nvim/eval.c 14879 warn V547 Expression 'varp != ((void *) 0)' is always true. | |
| ./src/nvim/eval.c 17164 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/eval.c 18079 err V557 Array overrun is possible. The 'VV_REG' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 18023 err V557 Array overrun is possible. The 'set_vim_var_string' function processes value '31'. Inspect the first argument. Check lines: 'eval.c:18080'. | |
| ./src/nvim/eval.c 18093 err V557 Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 18095 err V557 Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 18108 err V557 Array overrun is possible. The 'VV_THROWPOINT' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 18110 err V557 Array overrun is possible. The 'VV_THROWPOINT' index is pointing beyond array bound. | |
| ./src/nvim/eval.c 19405 warn V560 A part of conditional expression is always true: !eap->skip. | |
| ./src/nvim/eval.c 20994 warn V507 Pointer to local array 'buf' is stored outside the scope of this array. Such a pointer will become invalid. | |
| ./src/nvim/eval.c 21053 warn V614 Potentially uninitialized variable 'wait_start' used. Consider checking the first actual argument of the 'profile_sub_wait' function. | |
| ./src/nvim/eval.c 17954 err V557 Array overrun is possible. The 'get_vim_var_list' function processes value '57'. Inspect the first argument. Check lines: 'eval.c:21736'. | |
| ./src/nvim/eval.c 18023 err V557 Array overrun is possible. The 'set_vim_var_string' function processes value '62'. Inspect the first argument. Check lines: 'eval.c:21780'. | |
| ./src/nvim/eval.c 18023 err V557 Array overrun is possible. The 'set_vim_var_string' function processes value '63'. Inspect the first argument. Check lines: 'eval.c:21781'. | |
| ./src/nvim/eval.c 18023 err V557 Array overrun is possible. The 'set_vim_var_string' function processes value '64'. Inspect the first argument. Check lines: 'eval.c:21782'. | |
| ./src/nvim/fold.c 464 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/fold.c 1160 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/hardcopy.c 2589 warn V519 The 'prt_do_conv' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 2587, 2589. | |
| ./src/nvim/getchar.c 1754 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/getchar.c 1797 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/getchar.c 1854 err V705 It is possible that 'else' block was forgotten or commented out, thus altering the program's operation logics. | |
| ./src/nvim/ex_docmd.c 1099 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_docmd.c 1310 warn V519 The 'p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1309, 1310. | |
| ./src/nvim/ex_docmd.c 1733 err V536 Be advised that the utilized constant value is represented by an octal form. Oct: 0151, Dec: 105. | |
| ./src/nvim/ex_docmd.c 4109 warn V547 Expression 'p != ((void *) 0)' is always true. | |
| ./src/nvim/ex_docmd.c 6006 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_docmd.c 6025 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_docmd.c 6228 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_docmd.c 6966 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/ex_docmd.c 6985 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/fileio.c 746 warn V560 A part of conditional expression is always false: !c. | |
| ./src/nvim/fileio.c 6391 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/main.c 489 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/main.c 663 err V522 Dereferencing of the null pointer 'idx' might take place. The null pointer is passed into 'get_number_arg' function. Inspect the second argument. Check lines: 'main.c:1095'. | |
| ./src/nvim/mark.c 505 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/mark.c 1109 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/memfile.c 110 err V547 Expression 'blocksize <= (2147483647 * 2U + 1U)' is always true. | |
| ./src/nvim/memline.c 621 err V512 A call of the 'memchr' function will lead to underflow of the buffer 'b0p->b0_fname'. | |
| ./src/nvim/memline.c 3374 err V595 The 'name' pointer was utilized before it was verified against nullptr. Check lines: 3374, 3379. | |
| ./src/nvim/message.c 1170 err V517 The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 1170, 1173. | |
| ./src/nvim/message.c 1669 warn V571 Recurring check. The '1' condition was already verified in line 1668. | |
| ./src/nvim/misc1.c 1822 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/misc1.c 1922 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/misc1.c 2158 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/move.c 2144 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/msgpack_rpc/helpers.c 574 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c 579 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c 584 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c 590 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c 596 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c 604 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c 611 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/msgpack_rpc/helpers.c 616 warn V618 It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str); | |
| ./src/nvim/os/env.c 649 warn V507 Pointer to local array 'exe_name' is stored outside the scope of this array. Such a pointer will become invalid. | |
| ./src/nvim/os/fileio.c 71 err V501 There are identical sub-expressions to the left and to the right of the '!=' operator: kNone != kNone | |
| ./src/nvim/ops.c 2789 warn V756 The 'i' counter is not used inside a nested loop. Consider inspecting usage of 'j' counter. | |
| ./src/nvim/ops.c 3818 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/normal.c 655 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c 719 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c 701 warn V519 The 'State' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 699, 701. | |
| ./src/nvim/normal.c 838 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c 853 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c 969 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c 2342 err V564 The '|' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '||' operator. | |
| ./src/nvim/normal.c 2694 err V564 The '|' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '||' operator. | |
| ./src/nvim/normal.c 3518 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/normal.c 4044 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c 4376 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/normal.c 4433 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/normal.c 7617 err V705 It is possible that 'else' block was forgotten or commented out, thus altering the program's operation logics. | |
| ./src/nvim/popupmnu.c 131 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/quickfix.c 861 warn V547 Expression 'fmt_ptr != ((void *) 0)' is always true. | |
| ./src/nvim/quickfix.c 1769 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/quickfix.c 1828 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/quickfix.c 1840 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/quickfix.c 1889 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/quickfix.c 2729 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/quickfix.c 3285 err V501 There are identical sub-expressions 'eap->cmdidx == CMD_llast' to the left and to the right of the '||' operator. | |
| ./src/nvim/quickfix.c 3340 err V501 There are identical sub-expressions 'eap->cmdidx == CMD_lpfile' to the left and to the right of the '||' operator. | |
| ./src/nvim/quickfix.c 989 err V522 Dereferencing of the null pointer 'buf' might take place. The null pointer is passed into 'qf_init_ext' function. Inspect the third argument. Check lines: 'quickfix.c:4420'. | |
| ./src/nvim/quickfix.c 4480 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/search.c 615 err V502 Perhaps the '?:' operator works in a different way than it was expected. The '?:' operator has a lower priority than the '&&' operator. | |
| ./build/src/nvim/auto/options.generated.h 2583 err V542 Consider inspecting an odd type cast: 'char' to 'unsigned char *'. | |
| ./src/nvim/option.c 3543 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/option.c 3768 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c 198 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c 213 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c 314 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c 388 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c 410 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c 432 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c 546 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c 575 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c 1020 warn V571 Recurring check. The 'VIsual_active' condition was already verified in line 1019. | |
| ./src/nvim/screen.c 2453 warn V512 A call of the 'memmove' function will lead to underflow of the buffer 'nextline'. | |
| ./src/nvim/screen.c 2591 err V595 The 'cur' pointer was utilized before it was verified against nullptr. Check lines: 2591, 2597. | |
| ./src/nvim/screen.c 2789 warn V560 A part of conditional expression is always true: n_extra == 0. | |
| ./src/nvim/screen.c 4535 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c 4548 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c 4561 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/screen.c 5339 warn V560 A part of conditional expression is always false: l_enc_dbcs == 9932. | |
| ./src/nvim/screen.c 5381 warn V560 A part of conditional expression is always false: l_enc_dbcs == 9932. | |
| ./src/nvim/screen.c 5548 err V595 The 'cur' pointer was utilized before it was verified against nullptr. Check lines: 5548, 5559. | |
| ./src/nvim/screen.c 6108 warn V560 A part of conditional expression is always false: l_enc_dbcs == 9932. | |
| ./src/nvim/screen.c 6193 warn V560 A part of conditional expression is always false: l_enc_dbcs == 9932. | |
| ./src/nvim/shada.c 1280 warn V581 The conditional expressions of the 'if' operators situated alongside each other are identical. Check lines: 1276, 1280. | |
| ./src/nvim/spell.c 2433 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/spell.c 3656 err V512 A call of the 'memset' function will lead to underflow of the buffer 'sp'. | |
| ./src/nvim/terminal.c 1135 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/terminal.c 1187 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/tag.c 1229 err V512 A call of the 'memset' function will lead to underflow of the buffer '& search_info'. | |
| ./src/nvim/tag.c 2539 warn V519 The 'p_ic' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 2498, 2539. | |
| ./src/nvim/tui/tui.c 1070 warn V641 The size of the '& data->output_handle' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./src/nvim/syntax.c 1000 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/syntax.c 1087 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/syntax.c 2183 err V763 Parameter 'cur_si' is always rewritten in function body before being used. | |
| ./src/nvim/spellfile.c 2403 warn V547 Expression 'aff_entry->ae_flags == ((void *) 0)' is always true. Pointer 'aff_entry->ae_flags' == NULL. | |
| ./src/nvim/undo.c 2407 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c 167 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c 456 warn V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. | |
| ./src/nvim/window.c 1072 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c 1104 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c 1788 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c 3752 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c 4085 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c 4104 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c 4538 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c 5265 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/window.c 5909 err V501 There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab | |
| ./src/nvim/regexp.c 2403 warn V536 Be advised that the utilized constant value is represented by an octal form. Oct: '\\033', Dec: 27. | |
| ./src/nvim/regexp.c 2928 err V517 The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 2928, 2931. | |
| ./src/nvim/regexp.c 3057 err V536 Be advised that the utilized constant value is represented by an octal form. Oct: 040, Dec: 32. | |
| ./src/nvim/regexp.c 6952 err V595 The 'retval' pointer was utilized before it was verified against nullptr. Check lines: 6952, 6956. | |
| ./src/nvim/regexp_nfa.c 2778 err V517 The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 2778, 2780. | |
| ./src/nvim/regexp_nfa.c 4416 warn V536 Be advised that the utilized constant value is represented by an octal form. Oct: '\\033', Dec: 27. | |
| ./test/functional/fixtures/tty-test.c 90 warn V641 The size of the '& out' buffer is not a multiple of the element size of the type 'uv_stream_t'. | |
| ./test/functional/fixtures/tty-test.c 151 warn V641 The size of the '& tty' buffer is not a multiple of the element size of the type 'uv_stream_t'. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| <?xml version="1.0"?> | |
| <NewDataSet> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>Help:</ErrorCode> | |
| <Message>The documentation for all analyzer warnings is available here: http://www.viva64.com/en/w/.</Message> | |
| <Line>1</Line> | |
| <File>www.viva64.com/en/w</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>57</Line> | |
| <File>./src/nvim/api/ui.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>62</Line> | |
| <File>./src/nvim/api/ui.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>128</Line> | |
| <File>./src/nvim/api/ui.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>140</Line> | |
| <File>./src/nvim/api/ui.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>145</Line> | |
| <File>./src/nvim/api/ui.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>161</Line> | |
| <File>./src/nvim/api/ui.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>175</Line> | |
| <File>./src/nvim/api/ui.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>181</Line> | |
| <File>./src/nvim/api/ui.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>187</Line> | |
| <File>./src/nvim/api/ui.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions '& buf->changedtick_di.di_tv.vval.v_number' to the left and to the right of the '==' operator.</Message> | |
| <Line>108</Line> | |
| <File>./src/nvim/buffer.h</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>173</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>189</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>285</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>291</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>306</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>319</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>332</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>342</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>359</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>364</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>377</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>382</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>629</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>680</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>698</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>753</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>757</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>794</Line> | |
| <File>./src/nvim/api/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>63</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>96</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>120</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>125</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>130</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>205</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>260</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V779</ErrorCode> | |
| <Message>Unreachable code detected. It is possible that an error is present.</Message> | |
| <Line>616</Line> | |
| <File>./src/nvim/eval/typval_encode.c.h</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V779</ErrorCode> | |
| <Message>Unreachable code detected. It is possible that an error is present.</Message> | |
| <Line>819</Line> | |
| <File>./src/nvim/eval/typval_encode.c.h</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>563</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>578</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>593</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>661</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>715</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>928</Line> | |
| <File>./src/nvim/api/private/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>216</Line> | |
| <File>./src/nvim/api/vim.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>239</Line> | |
| <File>./src/nvim/api/vim.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>264</Line> | |
| <File>./src/nvim/api/vim.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>320</Line> | |
| <File>./src/nvim/api/vim.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>332</Line> | |
| <File>./src/nvim/api/vim.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>746</Line> | |
| <File>./src/nvim/api/vim.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>753</Line> | |
| <File>./src/nvim/api/vim.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>760</Line> | |
| <File>./src/nvim/api/vim.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>768</Line> | |
| <File>./src/nvim/api/vim.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>66</Line> | |
| <File>./src/nvim/api/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>80</Line> | |
| <File>./src/nvim/api/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>85</Line> | |
| <File>./src/nvim/api/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>134</Line> | |
| <File>./src/nvim/api/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>179</Line> | |
| <File>./src/nvim/api/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V764</ErrorCode> | |
| <Message>Possible incorrect order of arguments passed to 'getexactdigraph' function: 'char2' and 'char1'.</Message> | |
| <Line>1574</Line> | |
| <File>./src/nvim/digraph.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V560</ErrorCode> | |
| <Message>A part of conditional expression is always true: 1.</Message> | |
| <Line>1680</Line> | |
| <File>./src/nvim/digraph.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V571</ErrorCode> | |
| <Message>Recurring check. The '1' condition was already verified in line 1705.</Message> | |
| <Line>1707</Line> | |
| <File>./src/nvim/digraph.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>89</Line> | |
| <File>./src/nvim/diff.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>580</Line> | |
| <File>./src/nvim/diff.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V519</ErrorCode> | |
| <Message>The 'curwin' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1065, 1082.</Message> | |
| <Line>1082</Line> | |
| <File>./src/nvim/diff.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1131</Line> | |
| <File>./src/nvim/diff.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>2379</Line> | |
| <File>./src/nvim/diff.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V560</ErrorCode> | |
| <Message>A part of conditional expression is always false: swap_exists_action == 2.</Message> | |
| <Line>752</Line> | |
| <File>./src/nvim/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V519</ErrorCode> | |
| <Message>The 'swap_exists_action' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 791, 828.</Message> | |
| <Line>828</Line> | |
| <File>./src/nvim/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>4409</Line> | |
| <File>./src/nvim/buffer.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& proc->in->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>41</Line> | |
| <File>./src/nvim/event/libuv_process.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& proc->out->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>46</Line> | |
| <File>./src/nvim/event/libuv_process.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& proc->err->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>51</Line> | |
| <File>./src/nvim/event/libuv_process.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V595</ErrorCode> | |
| <Message>The 'ptr' pointer was utilized before it was verified against nullptr. Check lines: 3425, 3433.</Message> | |
| <Line>3425</Line> | |
| <File>./src/nvim/edit.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. </Message> | |
| <Line>7015</Line> | |
| <File>./src/nvim/edit.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. </Message> | |
| <Line>7021</Line> | |
| <File>./src/nvim/edit.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V595</ErrorCode> | |
| <Message>The 'state->li->li_tv.vval.v_string' pointer was utilized before it was verified against nullptr. Check lines: 256, 271.</Message> | |
| <Line>256</Line> | |
| <File>./src/nvim/eval/encode.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V523</ErrorCode> | |
| <Message>The 'then' statement is equivalent to the 'else' statement.</Message> | |
| <Line>494</Line> | |
| <File>./src/nvim/eval/typval_encode.c.h</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& proc->in->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>84</Line> | |
| <File>./src/nvim/event/process.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& proc->out->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>92</Line> | |
| <File>./src/nvim/event/process.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& proc->err->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>100</Line> | |
| <File>./src/nvim/event/process.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& watcher->uv.pipe.handle' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>76</Line> | |
| <File>./src/nvim/event/socket.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& stream->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>127</Line> | |
| <File>./src/nvim/event/socket.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& stream' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>28</Line> | |
| <File>./src/nvim/event/stream.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& stream->uv.pipe' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>54</Line> | |
| <File>./src/nvim/event/stream.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1390</Line> | |
| <File>./src/nvim/ex_cmds2.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions '!p_ri' and 'p_ri'. </Message> | |
| <Line>326</Line> | |
| <File>./src/nvim/farsi.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>4238</Line> | |
| <File>./src/nvim/ex_cmds.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>4364</Line> | |
| <File>./src/nvim/ex_cmds.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>5338</Line> | |
| <File>./src/nvim/ex_cmds.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'prepare_vimvar' function processes value '34'. Inspect the first argument. Check lines: 'eval.c:1144'.</Message> | |
| <Line>1108</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound.</Message> | |
| <Line>1145</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound.</Message> | |
| <Line>1146</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'restore_vimvar' function processes value '34'. Inspect the first argument. Check lines: 'eval.c:1160'.</Message> | |
| <Line>1121</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V560</ErrorCode> | |
| <Message>A part of conditional expression is always true: !eap->skip.</Message> | |
| <Line>2751</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V560</ErrorCode> | |
| <Message>A part of conditional expression is always false: eap->skip.</Message> | |
| <Line>2772</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V547</ErrorCode> | |
| <Message>Expression 'd == ((void *) 0)' is always false.</Message> | |
| <Line>3003</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_ERRORS' index is pointing beyond array bound.</Message> | |
| <Line>6758</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_ERRORS' index is pointing beyond array bound.</Message> | |
| <Line>6760</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_ERRORS' index is pointing beyond array bound.</Message> | |
| <Line>6764</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound.</Message> | |
| <Line>6800</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound.</Message> | |
| <Line>6806</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound.</Message> | |
| <Line>6809</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>7148</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V583</ErrorCode> | |
| <Message>The '?:' operator, regardless of its conditional expression, always returns one and the same value: * utf_ptr2char.</Message> | |
| <Line>7317</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'prepare_vimvar' function processes value '34'. Inspect the first argument. Check lines: 'eval.c:8380'.</Message> | |
| <Line>1108</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'prepare_vimvar' function processes value '35'. Inspect the first argument. Check lines: 'eval.c:8387'.</Message> | |
| <Line>1108</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound.</Message> | |
| <Line>8389</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound.</Message> | |
| <Line>8405</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound.</Message> | |
| <Line>8407</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound.</Message> | |
| <Line>8422</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound.</Message> | |
| <Line>8430</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'restore_vimvar' function processes value '35'. Inspect the first argument. Check lines: 'eval.c:8441'.</Message> | |
| <Line>1121</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'restore_vimvar' function processes value '34'. Inspect the first argument. Check lines: 'eval.c:8442'.</Message> | |
| <Line>1121</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound.</Message> | |
| <Line>8457</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_KEY' index is pointing beyond array bound.</Message> | |
| <Line>8458</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound.</Message> | |
| <Line>8459</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_VAL' index is pointing beyond array bound.</Message> | |
| <Line>8509</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V547</ErrorCode> | |
| <Message>Expression 'n == ((void *) 0)' is always false.</Message> | |
| <Line>8986</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_MOUSE_WIN' index is pointing beyond array bound.</Message> | |
| <Line>9328</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_MOUSE_WINID' index is pointing beyond array bound.</Message> | |
| <Line>9329</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_MOUSE_LNUM' index is pointing beyond array bound.</Message> | |
| <Line>9330</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_MOUSE_COL' index is pointing beyond array bound.</Message> | |
| <Line>9331</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_MOUSE_WIN' index is pointing beyond array bound.</Message> | |
| <Line>9371</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_MOUSE_WINID' index is pointing beyond array bound.</Message> | |
| <Line>9372</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_MOUSE_LNUM' index is pointing beyond array bound.</Message> | |
| <Line>9373</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_MOUSE_COL' index is pointing beyond array bound.</Message> | |
| <Line>9374</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_REG' index is pointing beyond array bound.</Message> | |
| <Line>9965</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_REG' index is pointing beyond array bound.</Message> | |
| <Line>10007</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V536</ErrorCode> | |
| <Message>Be advised that the utilized constant value is represented by an octal form. Oct: 0755, Dec: 493.</Message> | |
| <Line>12550</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V523</ErrorCode> | |
| <Message>The 'then' statement is equivalent to the 'else' statement.</Message> | |
| <Line>12785</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V590</ErrorCode> | |
| <Message>Consider inspecting this expression. The expression is excessive or contains a misprint.</Message> | |
| <Line>14311</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V547</ErrorCode> | |
| <Message>Expression 'varp != ((void *) 0)' is always true.</Message> | |
| <Line>14335</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V547</ErrorCode> | |
| <Message>Expression 'varp != ((void *) 0)' is always true.</Message> | |
| <Line>14879</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>17164</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_REG' index is pointing beyond array bound.</Message> | |
| <Line>18079</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'set_vim_var_string' function processes value '31'. Inspect the first argument. Check lines: 'eval.c:18080'.</Message> | |
| <Line>18023</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound.</Message> | |
| <Line>18093</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_EXCEPTION' index is pointing beyond array bound.</Message> | |
| <Line>18095</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_THROWPOINT' index is pointing beyond array bound.</Message> | |
| <Line>18108</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'VV_THROWPOINT' index is pointing beyond array bound.</Message> | |
| <Line>18110</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V560</ErrorCode> | |
| <Message>A part of conditional expression is always true: !eap->skip.</Message> | |
| <Line>19405</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V507</ErrorCode> | |
| <Message>Pointer to local array 'buf' is stored outside the scope of this array. Such a pointer will become invalid.</Message> | |
| <Line>20994</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V614</ErrorCode> | |
| <Message>Potentially uninitialized variable 'wait_start' used. Consider checking the first actual argument of the 'profile_sub_wait' function.</Message> | |
| <Line>21053</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'get_vim_var_list' function processes value '57'. Inspect the first argument. Check lines: 'eval.c:21736'.</Message> | |
| <Line>17954</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'set_vim_var_string' function processes value '62'. Inspect the first argument. Check lines: 'eval.c:21780'.</Message> | |
| <Line>18023</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'set_vim_var_string' function processes value '63'. Inspect the first argument. Check lines: 'eval.c:21781'.</Message> | |
| <Line>18023</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V557</ErrorCode> | |
| <Message>Array overrun is possible. The 'set_vim_var_string' function processes value '64'. Inspect the first argument. Check lines: 'eval.c:21782'.</Message> | |
| <Line>18023</Line> | |
| <File>./src/nvim/eval.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>464</Line> | |
| <File>./src/nvim/fold.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1160</Line> | |
| <File>./src/nvim/fold.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V519</ErrorCode> | |
| <Message>The 'prt_do_conv' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 2587, 2589.</Message> | |
| <Line>2589</Line> | |
| <File>./src/nvim/hardcopy.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. </Message> | |
| <Line>1754</Line> | |
| <File>./src/nvim/getchar.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. </Message> | |
| <Line>1797</Line> | |
| <File>./src/nvim/getchar.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V705</ErrorCode> | |
| <Message>It is possible that 'else' block was forgotten or commented out, thus altering the program's operation logics.</Message> | |
| <Line>1854</Line> | |
| <File>./src/nvim/getchar.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1099</Line> | |
| <File>./src/nvim/ex_docmd.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V519</ErrorCode> | |
| <Message>The 'p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1309, 1310.</Message> | |
| <Line>1310</Line> | |
| <File>./src/nvim/ex_docmd.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V536</ErrorCode> | |
| <Message>Be advised that the utilized constant value is represented by an octal form. Oct: 0151, Dec: 105.</Message> | |
| <Line>1733</Line> | |
| <File>./src/nvim/ex_docmd.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V547</ErrorCode> | |
| <Message>Expression 'p != ((void *) 0)' is always true.</Message> | |
| <Line>4109</Line> | |
| <File>./src/nvim/ex_docmd.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>6006</Line> | |
| <File>./src/nvim/ex_docmd.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>6025</Line> | |
| <File>./src/nvim/ex_docmd.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>6228</Line> | |
| <File>./src/nvim/ex_docmd.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>6966</Line> | |
| <File>./src/nvim/ex_docmd.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>6985</Line> | |
| <File>./src/nvim/ex_docmd.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V560</ErrorCode> | |
| <Message>A part of conditional expression is always false: !c.</Message> | |
| <Line>746</Line> | |
| <File>./src/nvim/fileio.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>6391</Line> | |
| <File>./src/nvim/fileio.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>489</Line> | |
| <File>./src/nvim/main.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V522</ErrorCode> | |
| <Message>Dereferencing of the null pointer 'idx' might take place. The null pointer is passed into 'get_number_arg' function. Inspect the second argument. Check lines: 'main.c:1095'.</Message> | |
| <Line>663</Line> | |
| <File>./src/nvim/main.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>505</Line> | |
| <File>./src/nvim/mark.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1109</Line> | |
| <File>./src/nvim/mark.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V547</ErrorCode> | |
| <Message>Expression 'blocksize <= (2147483647 * 2U + 1U)' is always true.</Message> | |
| <Line>110</Line> | |
| <File>./src/nvim/memfile.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V512</ErrorCode> | |
| <Message>A call of the 'memchr' function will lead to underflow of the buffer 'b0p->b0_fname'.</Message> | |
| <Line>621</Line> | |
| <File>./src/nvim/memline.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V595</ErrorCode> | |
| <Message>The 'name' pointer was utilized before it was verified against nullptr. Check lines: 3374, 3379.</Message> | |
| <Line>3374</Line> | |
| <File>./src/nvim/memline.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V517</ErrorCode> | |
| <Message>The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 1170, 1173.</Message> | |
| <Line>1170</Line> | |
| <File>./src/nvim/message.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V571</ErrorCode> | |
| <Message>Recurring check. The '1' condition was already verified in line 1668.</Message> | |
| <Line>1669</Line> | |
| <File>./src/nvim/message.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1822</Line> | |
| <File>./src/nvim/misc1.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1922</Line> | |
| <File>./src/nvim/misc1.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>2158</Line> | |
| <File>./src/nvim/misc1.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>2144</Line> | |
| <File>./src/nvim/move.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>574</Line> | |
| <File>./src/nvim/msgpack_rpc/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>579</Line> | |
| <File>./src/nvim/msgpack_rpc/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>584</Line> | |
| <File>./src/nvim/msgpack_rpc/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>590</Line> | |
| <File>./src/nvim/msgpack_rpc/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>596</Line> | |
| <File>./src/nvim/msgpack_rpc/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>604</Line> | |
| <File>./src/nvim/msgpack_rpc/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>611</Line> | |
| <File>./src/nvim/msgpack_rpc/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V618</ErrorCode> | |
| <Message>It's dangerous to call the 'snprintf' function in such a manner, as the line being passed could contain format specification. The example of the safe code: printf("%s", str);</Message> | |
| <Line>616</Line> | |
| <File>./src/nvim/msgpack_rpc/helpers.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V507</ErrorCode> | |
| <Message>Pointer to local array 'exe_name' is stored outside the scope of this array. Such a pointer will become invalid.</Message> | |
| <Line>649</Line> | |
| <File>./src/nvim/os/env.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '!=' operator: kNone != kNone</Message> | |
| <Line>71</Line> | |
| <File>./src/nvim/os/fileio.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V756</ErrorCode> | |
| <Message>The 'i' counter is not used inside a nested loop. Consider inspecting usage of 'j' counter.</Message> | |
| <Line>2789</Line> | |
| <File>./src/nvim/ops.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>3818</Line> | |
| <File>./src/nvim/ops.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. </Message> | |
| <Line>655</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. </Message> | |
| <Line>719</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V519</ErrorCode> | |
| <Message>The 'State' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 699, 701.</Message> | |
| <Line>701</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. </Message> | |
| <Line>838</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. </Message> | |
| <Line>853</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. </Message> | |
| <Line>969</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V564</ErrorCode> | |
| <Message>The '|' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '||' operator.</Message> | |
| <Line>2342</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V564</ErrorCode> | |
| <Message>The '|' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '||' operator.</Message> | |
| <Line>2694</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>3518</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. </Message> | |
| <Line>4044</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. </Message> | |
| <Line>4376</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>4433</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V705</ErrorCode> | |
| <Message>It is possible that 'else' block was forgotten or commented out, thus altering the program's operation logics.</Message> | |
| <Line>7617</Line> | |
| <File>./src/nvim/normal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>131</Line> | |
| <File>./src/nvim/popupmnu.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V547</ErrorCode> | |
| <Message>Expression 'fmt_ptr != ((void *) 0)' is always true.</Message> | |
| <Line>861</Line> | |
| <File>./src/nvim/quickfix.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1769</Line> | |
| <File>./src/nvim/quickfix.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1828</Line> | |
| <File>./src/nvim/quickfix.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1840</Line> | |
| <File>./src/nvim/quickfix.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1889</Line> | |
| <File>./src/nvim/quickfix.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>2729</Line> | |
| <File>./src/nvim/quickfix.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions 'eap->cmdidx == CMD_llast' to the left and to the right of the '||' operator.</Message> | |
| <Line>3285</Line> | |
| <File>./src/nvim/quickfix.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions 'eap->cmdidx == CMD_lpfile' to the left and to the right of the '||' operator.</Message> | |
| <Line>3340</Line> | |
| <File>./src/nvim/quickfix.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V522</ErrorCode> | |
| <Message>Dereferencing of the null pointer 'buf' might take place. The null pointer is passed into 'qf_init_ext' function. Inspect the third argument. Check lines: 'quickfix.c:4420'.</Message> | |
| <Line>989</Line> | |
| <File>./src/nvim/quickfix.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>4480</Line> | |
| <File>./src/nvim/quickfix.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V502</ErrorCode> | |
| <Message>Perhaps the '?:' operator works in a different way than it was expected. The '?:' operator has a lower priority than the '&&' operator.</Message> | |
| <Line>615</Line> | |
| <File>./src/nvim/search.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V542</ErrorCode> | |
| <Message>Consider inspecting an odd type cast: 'char' to 'unsigned char *'.</Message> | |
| <Line>2583</Line> | |
| <File>./build/src/nvim/auto/options.generated.h</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>3543</Line> | |
| <File>./src/nvim/option.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>3768</Line> | |
| <File>./src/nvim/option.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>198</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>213</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>314</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>388</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>410</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>432</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>546</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>575</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V571</ErrorCode> | |
| <Message>Recurring check. The 'VIsual_active' condition was already verified in line 1019.</Message> | |
| <Line>1020</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V512</ErrorCode> | |
| <Message>A call of the 'memmove' function will lead to underflow of the buffer 'nextline'.</Message> | |
| <Line>2453</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V595</ErrorCode> | |
| <Message>The 'cur' pointer was utilized before it was verified against nullptr. Check lines: 2591, 2597.</Message> | |
| <Line>2591</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V560</ErrorCode> | |
| <Message>A part of conditional expression is always true: n_extra == 0.</Message> | |
| <Line>2789</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>4535</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>4548</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>4561</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V560</ErrorCode> | |
| <Message>A part of conditional expression is always false: l_enc_dbcs == 9932.</Message> | |
| <Line>5339</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V560</ErrorCode> | |
| <Message>A part of conditional expression is always false: l_enc_dbcs == 9932.</Message> | |
| <Line>5381</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V595</ErrorCode> | |
| <Message>The 'cur' pointer was utilized before it was verified against nullptr. Check lines: 5548, 5559.</Message> | |
| <Line>5548</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V560</ErrorCode> | |
| <Message>A part of conditional expression is always false: l_enc_dbcs == 9932.</Message> | |
| <Line>6108</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V560</ErrorCode> | |
| <Message>A part of conditional expression is always false: l_enc_dbcs == 9932.</Message> | |
| <Line>6193</Line> | |
| <File>./src/nvim/screen.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V581</ErrorCode> | |
| <Message>The conditional expressions of the 'if' operators situated alongside each other are identical. Check lines: 1276, 1280.</Message> | |
| <Line>1280</Line> | |
| <File>./src/nvim/shada.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>2433</Line> | |
| <File>./src/nvim/spell.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V512</ErrorCode> | |
| <Message>A call of the 'memset' function will lead to underflow of the buffer 'sp'.</Message> | |
| <Line>3656</Line> | |
| <File>./src/nvim/spell.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1135</Line> | |
| <File>./src/nvim/terminal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1187</Line> | |
| <File>./src/nvim/terminal.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V512</ErrorCode> | |
| <Message>A call of the 'memset' function will lead to underflow of the buffer '& search_info'.</Message> | |
| <Line>1229</Line> | |
| <File>./src/nvim/tag.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V519</ErrorCode> | |
| <Message>The 'p_ic' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 2498, 2539.</Message> | |
| <Line>2539</Line> | |
| <File>./src/nvim/tag.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& data->output_handle' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>1070</Line> | |
| <File>./src/nvim/tui/tui.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1000</Line> | |
| <File>./src/nvim/syntax.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1087</Line> | |
| <File>./src/nvim/syntax.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V763</ErrorCode> | |
| <Message>Parameter 'cur_si' is always rewritten in function body before being used.</Message> | |
| <Line>2183</Line> | |
| <File>./src/nvim/syntax.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V547</ErrorCode> | |
| <Message>Expression 'aff_entry->ae_flags == ((void *) 0)' is always true. Pointer 'aff_entry->ae_flags' == NULL.</Message> | |
| <Line>2403</Line> | |
| <File>./src/nvim/spellfile.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>2407</Line> | |
| <File>./src/nvim/undo.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>167</Line> | |
| <File>./src/nvim/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V728</ErrorCode> | |
| <Message>An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'p_lrm' and '!p_lrm'. </Message> | |
| <Line>456</Line> | |
| <File>./src/nvim/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1072</Line> | |
| <File>./src/nvim/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1104</Line> | |
| <File>./src/nvim/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>1788</Line> | |
| <File>./src/nvim/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>3752</Line> | |
| <File>./src/nvim/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>4085</Line> | |
| <File>./src/nvim/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>4104</Line> | |
| <File>./src/nvim/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>4538</Line> | |
| <File>./src/nvim/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>5265</Line> | |
| <File>./src/nvim/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V501</ErrorCode> | |
| <Message>There are identical sub-expressions to the left and to the right of the '==' operator: (curtab) == curtab</Message> | |
| <Line>5909</Line> | |
| <File>./src/nvim/window.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V536</ErrorCode> | |
| <Message>Be advised that the utilized constant value is represented by an octal form. Oct: '\033', Dec: 27.</Message> | |
| <Line>2403</Line> | |
| <File>./src/nvim/regexp.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V517</ErrorCode> | |
| <Message>The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 2928, 2931.</Message> | |
| <Line>2928</Line> | |
| <File>./src/nvim/regexp.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V536</ErrorCode> | |
| <Message>Be advised that the utilized constant value is represented by an octal form. Oct: 040, Dec: 32.</Message> | |
| <Line>3057</Line> | |
| <File>./src/nvim/regexp.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V595</ErrorCode> | |
| <Message>The 'retval' pointer was utilized before it was verified against nullptr. Check lines: 6952, 6956.</Message> | |
| <Line>6952</Line> | |
| <File>./src/nvim/regexp.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>1</Level> | |
| <ErrorType>error</ErrorType> | |
| <ErrorCode>V517</ErrorCode> | |
| <Message>The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 2778, 2780.</Message> | |
| <Line>2778</Line> | |
| <File>./src/nvim/regexp_nfa.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V536</ErrorCode> | |
| <Message>Be advised that the utilized constant value is represented by an octal form. Oct: '\033', Dec: 27.</Message> | |
| <Line>4416</Line> | |
| <File>./src/nvim/regexp_nfa.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& out' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>90</Line> | |
| <File>./test/functional/fixtures/tty-test.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| <PVS-Studio_Analysis_Log> | |
| <Level>2</Level> | |
| <ErrorType>warning</ErrorType> | |
| <ErrorCode>V641</ErrorCode> | |
| <Message>The size of the '& tty' buffer is not a multiple of the element size of the type 'uv_stream_t'.</Message> | |
| <Line>151</Line> | |
| <File>./test/functional/fixtures/tty-test.c</File> | |
| </PVS-Studio_Analysis_Log> | |
| </NewDataSet> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment