MESSAGES
Location Code Message
Fails/Info
special-casing-table.h (73)
V011 Presence of #line directives may cause some diagnostic messages to have incorrect file name and line number.
lex.cc (27)
V011 Presence of #line directives may cause some diagnostic messages to have incorrect file name and line number.
oct-parse.h (221)
V011 Presence of #line directives may cause some diagnostic messages to have incorrect file name and line number.
oct-gperf.h (32)
V011 Presence of #line directives may cause some diagnostic messages to have incorrect file name and line number.
lex.cc (1)
V002 Some diagnostic messages may contain incorrect line number in this file.
oct-parse.cc (77)
V011 Presence of #line directives may cause some diagnostic messages to have incorrect file name and line number.
oct-parse.cc (1)
V002 Some diagnostic messages may contain incorrect line number in this file.
ls-oct-text.cc (1)
V002 Some diagnostic messages may contain incorrect line number in this file.
oct-tex-lexer.cc (24)
V011 Presence of #line directives may cause some diagnostic messages to have incorrect file name and line number.
oct-tex-parser.h (51)
V011 Presence of #line directives may cause some diagnostic messages to have incorrect file name and line number.
oct-tex-lexer.cc (1)
V002 Some diagnostic messages may contain incorrect line number in this file.
oct-tex-parser.cc (72)
V011 Presence of #line directives may cause some diagnostic messages to have incorrect file name and line number.
dNDArray.cc (1)
V002 Some diagnostic messages may contain incorrect line number in this file.
fNDArray.cc (1)
V002 Some diagnostic messages may contain incorrect line number in this file.
General Analysis (GA)
areadlink-with-size.c (59)
V547 Expression 'symlink_max < INITIAL_LIMIT_BOUND' is always true.
canonicalize.c (161)
V547 Expression 'prefix_len' is always false.
canonicalize.c (297)
V547 Expression 'pfxlen' is always false.
careadlinkat.c (145)
V547 Expression 'buf_size_max < (18446744073709551615UL)' is always true.
md2.c (60)
V512 A call of the 'memcpy' function will lead to underflow of the buffer 'ctx->X'.
md4.c (245)
V512 A call of the 'memcpy' function will lead to underflow of the buffer 'ctx->buffer'.
md5.c (279)
V512 A call of the 'memcpy' function will lead to underflow of the buffer 'ctx->buffer'.
sha1.c (266)
V512 A call of the 'memcpy' function will lead to underflow of the buffer 'ctx->buffer'.
sha256.c (185)
V785 Constant expression in switch statement.
sha256.c (345)
V512 A call of the 'memcpy' function will lead to underflow of the buffer 'ctx->buffer'.
sha512.c (186)
V785 Constant expression in switch statement.
sha512.c (346)
V512 A call of the 'memcpy' function will lead to underflow of the buffer 'ctx->buffer'.
dirname-lgpl.c (38)
V547 Expression 'prefix_length != 0' is always false.
dirname-lgpl.c (76)
V560 A part of conditional expression is always false: length == 0.
basename-lgpl.c (70)
V560 A part of conditional expression is always false: prefix_len.
filemode.c (170)
V501 There are identical sub-expressions to the left and to the right of the '-' operator: (statp)->st_mode - (statp)->st_mode
filemode.c (174)
V501 There are identical sub-expressions to the left and to the right of the '-' operator: (statp)->st_mode - (statp)->st_mode
filemode.c (176)
V501 There are identical sub-expressions to the left and to the right of the '-' operator: (statp)->st_mode - (statp)->st_mode
filemode.c (174)
V517 The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 174, 176.
filemode.c (172)
V517 The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 172, 178.
filemode.c (170)
V517 The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 170, 174.
gettext.h (154)
V547 Expression 'translation == msg_ctxt_id' is always true.
gettext.h (235)
V547 Expression 'translation != msg_ctxt_id' is always false.
gettext.h (241)
V558 Function returns the pointer to temporary local object.
gettext.h (240)
V547 Expression 'found_translation' is always false.
tmpdir.c (133)
V549 The first argument of 'strcmp' function is equal to the second argument.
u8-to-u32.c (105)
V641 The size of the allocated memory buffer is not a multiple of the element size.
xmalloc.c (61)
V701 realloc() possible leak: when realloc() fails in allocating memory, original pointer 'p' is lost. Consider assigning realloc() to a temporary pointer.
xmalloc.c (86)
V575 The potential null pointer is passed into 'memset' function. Inspect the first argument.
xmalloc.c (113)
V575 The potential null pointer is passed into 'memcpy' function. Inspect the first argument.
mktime.c (142)
V610 Unspecified behavior. Check the shift operator '>>'. The left operand '-one' is negative.
mktime.c (142)
V547 Expression '- one >> 1 == - 1' is always true.
mktime.c (150)
V560 A part of conditional expression is always true: (!((time_t) 0 < (time_t) - 1)).
mktime.c (153)
V547 Expression is always false.
mktime.c (274)
V547 Expression '* t < mktime_min' is always false.
mktime.c (275)
V547 Expression '* t <= mktime_max' is always true.
mktime.c (473)
V560 A part of conditional expression is always true: mktime_min <= gt.
mktime.c (473)
V560 A part of conditional expression is always true: gt <= mktime_max.
mktime.c (506)
V560 A part of conditional expression is always true: mktime_min <= t.
mktime.c (506)
V560 A part of conditional expression is always true: t <= mktime_max.
mktime.c (506)
V560 A part of conditional expression is always false: !(mktime_min <= t && t <= mktime_max).
time_rz.c (71)
V564 The '|' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '||' operator.
time_rz.c (77)
V792 The 'isdst_differ' function located to the right of the operator '|' will be called regardless of the value of the left operand. Perhaps, it is better to use '||'.
vasnprintf.c (4943)
V501 There are identical sub-expressions to the left and to the right of the '/' operator: sizeof (char) / sizeof (char)
vasnprintf.c (4962)
V501 There are identical sub-expressions to the left and to the right of the '/' operator: sizeof (char) / sizeof (char)
vasnprintf.c (4963)
V501 There are identical sub-expressions to the left and to the right of the '/' operator: sizeof (char) / sizeof (char)
vasnprintf.c (4964)
V501 There are identical sub-expressions to the left and to the right of the '/' operator: sizeof (char) / sizeof (char)
vasnprintf.c (5234)
V501 There are identical sub-expressions to the left and to the right of the '/' operator: sizeof (char) / sizeof (char)
vasnprintf.c (5250)
V501 There are identical sub-expressions to the left and to the right of the '/' operator: sizeof (char) / sizeof (char)
vasnprintf.c (5251)
V501 There are identical sub-expressions to the left and to the right of the '/' operator: sizeof (char) / sizeof (char)
idx-vector.h (634)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (654)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (661)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (670)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (708)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (726)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (733)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (742)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (780)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (798)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (805)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (814)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (850)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (865)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (872)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (880)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (922)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (938)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (945)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.h (955)
V522 There might be dereferencing of a potential null pointer 'r'.
lo-mappers.h (63)
V601 The bool type is implicitly cast to the double type.
lo-mappers.h (64)
V601 The bool type is implicitly cast to the float type.
MSparse.cc (549)
V501 There are identical sub-expressions to the left and to the right of the '/' operator: Zero / Zero
Array.h (454)
V512 Instantiation of Array <int>: A call of the 'compute_index' function will lead to overflow of the buffer 'ra_idx.data()'.
chol.h (42)
V730 Not all members of a class are initialized inside the constructor. Consider inspecting: is_upper.
chol.h (57)
V730 Not all members of a class are initialized inside the constructor. Consider inspecting: is_upper.
Array.h (454)
V512 Instantiation of Array < octave_f77_int_type >: A call of the 'compute_index' function will lead to overflow of the buffer 'ra_idx.data()'.
ov-fcn-handle.h (45)
V690 The 'octave_fcn_handle' class implements a copy constructor, but lacks the '=' operator. It is dangerous to use such a class.
input.h (203)
V690 The 'base_reader' class implements a copy constructor, but lacks the '=' operator. It is dangerous to use such a class.
ov-classdef.h (1601)
V522 There might be dereferencing of a potential null pointer.
ov-classdef.h (1610)
V522 There might be dereferencing of a potential null pointer.
call-stack.h (52)
V690 The 'stack_frame' class implements a copy constructor, but lacks the '=' operator. It is dangerous to use such a class.
token.h (166)
V773 The 'm_str' pointer was not released in destructor. A memory leak is possible.
token.h (166)
V773 The 'm_sr' pointer was not released in destructor. A memory leak is possible.
token.h (166)
V773 The 'm_superclass_info' pointer was not released in destructor. A memory leak is possible.
ov-base-mat.h (68)
V773 The 'idx_cache' pointer was not released in destructor. A memory leak is possible.
__glpk__.cc (290)
V636 The expression was implicitly cast from 'long' type to 'double' type. Consider utilizing an explicit type cast to avoid the loss of a fractional part. An example: double A = (double)(X) / Y;.
graphics.h (2914)
V678 An object is used as an argument to its own method. Consider checking the first actual argument of the 'override_defaults' function.
__init_fltk__.cc (1389)
V601 The integer type is implicitly cast to the char type.
__init_fltk__.cc (1855)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
__init_fltk__.cc (742)
V773 The 'm_menubar' pointer was not released in destructor. A memory leak is possible.
audiodevinfo.cc (1363)
V547 Expression 'sample_l32 & 0x00800000' is always false.
audiodevinfo.cc (1366)
V547 Expression 'sample_r32 & 0x00800000' is always false.
audiodevinfo.cc (1441)
V547 Expression 'sample_l32 & 0x00800000' is always false.
audiodevinfo.cc (1444)
V547 Expression 'sample_r32 & 0x00800000' is always false.
audiodevinfo.cc (2233)
V668 There is no sense in testing the 'recorder' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
audiodevinfo.cc (2257)
V547 Expression 'is_function' is always false.
sparse-chol.h (46)
V690 The 'sparse_chol' class implements the '=' operator, but lacks a copy constructor. It is dangerous to use such a class.
chol.cc (253)
V614 Uninitialized variable 'info' used.
chol.cc (266)
V614 Uninitialized variable 'info' used.
chol.cc (286)
V614 Uninitialized variable 'info' used.
chol.cc (299)
V614 Uninitialized variable 'info' used.
chol.cc (414)
V614 Uninitialized variable 'info' used.
chol.cc (425)
V614 Uninitialized variable 'info' used.
chol.cc (441)
V614 Uninitialized variable 'info' used.
chol.cc (452)
V614 Uninitialized variable 'info' used.
gzip.cc (429)
V507 Pointer to local array 'buf_out' is stored outside the scope of this array. Such a pointer will become invalid.
gzip.cc (420)
V507 Pointer to local array 'buf_in' is stored outside the scope of this array. Such a pointer will become invalid.
symbfact.cc (133)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
BaseControl.cc (216)
V522 There might be dereferencing of a potential null pointer 'm'.
ButtonGroup.cc (214)
V522 There might be dereferencing of a potential null pointer 'm'.
Figure.cc (751)
V522 There might be dereferencing of a potential null pointer 'dynamic_cast< QChildEvent * > (xevent)'.
gl-select.h (44)
V730 Not all members of a class are initialized inside the constructor. Consider inspecting: xp, yp.
ListBoxControl.cc (235)
V522 There might be dereferencing of a potential null pointer 'm'.
ListBoxControl.cc (249)
V522 There might be dereferencing of a potential null pointer 'm'.
Panel.cc (190)
V522 There might be dereferencing of a potential null pointer 'm'.
Table.cc (367)
V758 The 'c_str' reference becomes invalid when temporary object returned by a function is destroyed.
Table.cc (367)
V576 Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the intmax_t type is expected.
Table.cc (368)
V758 The 'c_str' reference becomes invalid when temporary object returned by a function is destroyed.
Table.cc (368)
V576 Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the uintmax_t type is expected.
Table.cc (369)
V758 The 'c_str' reference becomes invalid when temporary object returned by a function is destroyed.
Table.cc (369)
V576 Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the intmax_t type is expected.
Table.cc (370)
V758 The 'c_str' reference becomes invalid when temporary object returned by a function is destroyed.
Table.cc (370)
V576 Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the uintmax_t type is expected.
Table.cc (371)
V758 The 'c_str' reference becomes invalid when temporary object returned by a function is destroyed.
Table.cc (371)
V576 Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the intmax_t type is expected.
Table.cc (372)
V758 The 'c_str' reference becomes invalid when temporary object returned by a function is destroyed.
Table.cc (372)
V576 Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the uintmax_t type is expected.
Table.cc (373)
V758 The 'c_str' reference becomes invalid when temporary object returned by a function is destroyed.
Table.cc (373)
V576 Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the intmax_t type is expected.
Table.cc (374)
V758 The 'c_str' reference becomes invalid when temporary object returned by a function is destroyed.
Table.cc (374)
V576 Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the uintmax_t type is expected.
Table.cc (1324)
V560 A part of conditional expression is always true: widget.
Table.cc (1523)
V522 There might be dereferencing of a potential null pointer 'm'.
Table.cc (1561)
V522 There might be dereferencing of a potential null pointer 'k'.
Table.cc (1663)
V522 There might be dereferencing of a potential null pointer 'm'.
ToolBar.cc (137)
V522 There might be dereferencing of a potential null pointer 'ae'.
shared-fcns.h (127)
V560 A part of conditional expression is always true: op == oep.
uniconv-wrappers.c (79)
V575 The potential null pointer is passed into 'memcpy' function. Inspect the first argument. Check lines: 79, 78.
uniconv-wrappers.c (101)
V575 The potential null pointer is passed into 'memcpy' function. Inspect the first argument. Check lines: 101, 100.
ov-range.h (83)
V773 The 'idx_cache' pointer was not released in destructor. A memory leak is possible.
Array.cc (2697)
V1028 Possible overflow. Consider casting operands of the 'dim + 1' operator to the 'octave_idx_type' type, not the result.
oct-sort.cc (656)
V602 Consider inspecting the '(min_gallop > 1)' expression. '>' possibly should be replaced with '>>'.
oct-sort.cc (790)
V602 Consider inspecting the '(min_gallop > 1)' expression. '>' possibly should be replaced with '>>'.
oct-sort.cc (938)
V602 Consider inspecting the '(min_gallop > 1)' expression. '>' possibly should be replaced with '>>'.
oct-sort.cc (1079)
V602 Consider inspecting the '(min_gallop > 1)' expression. '>' possibly should be replaced with '>>'.
oct-errno.cc (702)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
ov-base.cc (1091)
V1016 Expression 'umap < 0' is always false.
ov-bool-mat.cc (317)
V547 Expression '!extract_keyword(is, "columns", nc)' is always false.
ov-bool-mat.cc (317)
V560 A part of conditional expression is always false: nc < 0.
ov-bool-mat.cc (320)
V560 A part of conditional expression is always false: nc > 0.
ov-bool-mat.cc (334)
V560 A part of conditional expression is always true: nc == 0.
ov-base-mat.h (68)
V773 The 'typ' pointer was not released in destructor. A memory leak is possible.
ov-bool.cc (65)
V601 The bool type is implicitly cast to the double type. Inspect the first argument.
ov-bool.cc (237)
V614 Uninitialized buffer 'dimens' used. Consider checking the second actual argument of the 'H5Screate_simple' function.
ov-bool.cc (237)
V519 The 'space_hid' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 235, 237.
ov-cell.cc (847)
V547 Expression '!extract_keyword(is, "columns", nc)' is always false.
ov-cell.cc (847)
V560 A part of conditional expression is always false: nc < 0.
ov-cell.cc (850)
V560 A part of conditional expression is always false: nc > 0.
ov-cell.cc (878)
V560 A part of conditional expression is always true: nc == 0.
ov-class.cc (1216)
V547 Expression '!extract_keyword(is, "length", len)' is always false.
ov-class.cc (1216)
V560 A part of conditional expression is always false: len < 0.
ov-class.cc (1261)
V547 Expression 'len == 0' is always true.
ov-class.cc (1219)
V547 Expression 'len > 0' is always false.
ov-classdef.cc (3485)
V678 An object is used as an argument to its own method. Consider checking the first actual argument of the 'set_class' function.
ov-complex.cc (368)
V614 Uninitialized buffer 'dimens' used. Consider checking the second actual argument of the 'H5Screate_simple' function.
ov-complex.cc (368)
V519 The 'space_hid' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 366, 368.
ov-cx-mat.cc (389)
V547 Expression '!extract_keyword(is, "columns", nc)' is always false.
ov-cx-mat.cc (389)
V560 A part of conditional expression is always false: nc < 0.
ov-cx-mat.cc (392)
V560 A part of conditional expression is always false: nc > 0.
ov-cx-mat.cc (401)
V560 A part of conditional expression is always true: nc == 0.
ov-fcn-handle.cc (780)
V547 Expression 'type_hid < 0' is always false.
ov-fcn-handle.cc (735)
V519 The 'type_hid' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 732, 735.
ov-fcn-handle.cc (1748)
V1004 The 'fh' pointer was used unsafely after it was verified against nullptr. Check lines: 1741, 1748.
ov-fcn-handle.cc (1989)
V522 There might be dereferencing of a potential null pointer 'idx_expr'.
ov-fcn-handle.cc (2046)
V522 There might be dereferencing of a potential null pointer 'elt_id'.
ov-fcn-handle.cc (2073)
V522 There might be dereferencing of a potential null pointer 'head_id'.
ov-fcn-inline.cc (399)
V547 Expression 'type_hid < 0' is always false.
ov-fcn-inline.cc (491)
V767 Suspicious access to element of 'hdims' array by a constant index inside a loop.
ov-float.cc (258)
V614 Uninitialized buffer 'dimens' used. Consider checking the second actual argument of the 'H5Screate_simple' function.
ov-float.cc (258)
V519 The 'space_hid' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 256, 258.
ov-flt-complex.cc (315)
V614 Uninitialized buffer 'dimens' used. Consider checking the second actual argument of the 'H5Screate_simple' function.
ov-flt-complex.cc (315)
V519 The 'space_hid' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 313, 315.
ov-flt-cx-mat.cc (363)
V547 Expression '!extract_keyword(is, "columns", nc)' is always false.
ov-flt-cx-mat.cc (363)
V560 A part of conditional expression is always false: nc < 0.
ov-flt-cx-mat.cc (366)
V560 A part of conditional expression is always false: nc > 0.
ov-flt-cx-mat.cc (375)
V560 A part of conditional expression is always true: nc == 0.
ov-flt-cx-mat.cc (556)
V547 Expression 'retval' is always false.
ov-flt-re-mat.cc (440)
V547 Expression '!extract_keyword(is, "columns", nc)' is always false.
ov-flt-re-mat.cc (440)
V560 A part of conditional expression is always false: nc < 0.
ov-flt-re-mat.cc (443)
V560 A part of conditional expression is always false: nc > 0.
ov-flt-re-mat.cc (452)
V560 A part of conditional expression is always true: nc == 0.
ov-java.h (38)
V690 The 'octave_java' class implements a copy constructor, but lacks the '=' operator. It is dangerous to use such a class.
ov-range.cc (649)
V614 Uninitialized buffer 'dimens' used. Consider checking the second actual argument of the 'H5Screate_simple' function.
ov-range.cc (649)
V519 The 'space_hid' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 647, 649.
ov-re-mat.cc (543)
V547 Expression '!extract_keyword(is, "columns", nc)' is always false.
ov-re-mat.cc (543)
V560 A part of conditional expression is always false: nc < 0.
ov-re-mat.cc (546)
V560 A part of conditional expression is always false: nc > 0.
ov-re-mat.cc (555)
V560 A part of conditional expression is always true: nc == 0.
ov-scalar.cc (278)
V614 Uninitialized buffer 'dimens' used. Consider checking the second actual argument of the 'H5Screate_simple' function.
ov-scalar.cc (278)
V519 The 'space_hid' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 276, 278.
ov-str-mat.cc (404)
V614 Uninitialized variable 'len' used. Consider checking the third actual argument of the 'extract_keyword' function.
ov-str-mat.cc (404)
V547 Expression '!extract_keyword(is, "length", len)' is always false.
ov-struct.cc (785)
V547 Expression 'len == 0' is always true.
ov-struct.cc (1418)
V547 Expression '!extract_keyword(is, "length", len)' is always false.
ov-struct.cc (1418)
V560 A part of conditional expression is always false: len < 0.
ov-struct.cc (1445)
V547 Expression 'len == 0' is always true.
ov-struct.cc (1421)
V547 Expression 'len > 0' is always false.
ov-base-int.cc (744)
V614 Uninitialized buffer 'dimens' used. Consider checking the second actual argument of the 'H5Screate_simple' function.
ov-base-int.cc (744)
V519 The 'space_hid' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 742, 744.
ov-bool-sparse.cc (359)
V614 Uninitialized buffer 'hdims' used. Consider checking the second actual argument of the 'H5Screate_simple' function.
ov-cx-sparse.cc (391)
V614 Uninitialized buffer 'hdims' used. Consider checking the second actual argument of the 'H5Screate_simple' function.
ov-re-sparse.cc (414)
V614 Uninitialized buffer 'hdims' used. Consider checking the second actual argument of the 'H5Screate_simple' function.
bp-table.cc (333)
V547 Expression 'seen_if' is always false.
bp-table.cc (347)
V547 Expression 'seen_if' is always false.
bp-table.cc (535)
V522 There might be dereferencing of a potential null pointer.
pt-cbinop.h (68)
V703 It is odd that the 'm_lhs' field in derived class 'tree_compound_binary_expression' overwrites field in base class 'tree_binary_expression'. Check lines: pt-cbinop.h:68, pt-binop.h:121.
pt-cbinop.h (69)
V703 It is odd that the 'm_rhs' field in derived class 'tree_compound_binary_expression' overwrites field in base class 'tree_binary_expression'. Check lines: pt-cbinop.h:69, pt-binop.h:122.
lex.ll (391)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 391, 391.
lex.ll (406)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 406, 406.
lex.ll (422)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 422, 422.
lex.ll (490)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 490, 490.
lex.ll (584)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 584, 584.
lex.ll (641)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 641, 641.
lex.ll (716)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 716, 716.
lex.ll (775)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 775, 775.
lex.ll (1106)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1106, 1106.
lex.ll (1120)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1120, 1120.
lex.ll (1132)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1132, 1132.
lex.ll (1157)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1157, 1157.
lex.ll (1169)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1169, 1169.
lex.ll (1241)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1241, 1241.
lex.ll (1245)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1245, 1245.
lex.ll (1257)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1257, 1257.
lex.ll (1283)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1283, 1283.
lex.ll (1305)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1305, 1305.
lex.ll (1317)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1317, 1317.
lex.ll (1416)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1416, 1416.
lex.ll (1486)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1486, 1486.
lex.ll (1510)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1510, 1510.
lex.ll (1511)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1511, 1511.
lex.ll (1512)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1512, 1512.
lex.ll (1513)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1513, 1513.
lex.ll (1514)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1514, 1514.
lex.ll (1515)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1515, 1515.
lex.ll (1516)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1516, 1516.
lex.ll (1517)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1517, 1517.
lex.ll (1518)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1518, 1518.
lex.ll (1519)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1519, 1519.
lex.ll (1520)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1520, 1520.
lex.ll (1521)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1521, 1521.
lex.ll (1522)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1522, 1522.
lex.ll (1523)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1523, 1523.
lex.ll (1524)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1524, 1524.
lex.ll (1525)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1525, 1525.
lex.ll (1526)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1526, 1526.
lex.ll (1527)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1527, 1527.
lex.ll (1528)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1528, 1528.
lex.ll (1536)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1536, 1536.
lex.ll (1537)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1537, 1537.
lex.ll (1538)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1538, 1538.
lex.ll (1539)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1539, 1539.
lex.ll (1549)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1549, 1549.
lex.ll (1550)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1550, 1550.
lex.ll (1552)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1552, 1552.
lex.ll (1553)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1553, 1553.
lex.ll (1567)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1567, 1567.
lex.ll (1568)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1568, 1568.
lex.ll (1587)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1587, 1587.
lex.ll (1639)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1639, 1639.
lex.ll (1661)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1661, 1661.
lex.ll (1662)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1662, 1662.
lex.ll (1663)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1663, 1663.
lex.ll (1664)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1664, 1664.
lex.ll (1665)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1665, 1665.
lex.ll (1666)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1666, 1666.
lex.ll (1667)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1667, 1667.
lex.ll (1668)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1668, 1668.
lex.ll (1669)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1669, 1669.
lex.ll (1670)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1670, 1670.
lex.ll (1671)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1671, 1671.
lex.ll (1672)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1672, 1672.
lex.ll (1673)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1673, 1673.
lex.ll (1674)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1674, 1674.
lex.ll (1675)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1675, 1675.
lex.ll (1676)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1676, 1676.
lex.ll (1699)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1699, 1699.
lex.ll (1151)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 1151, 1151.
lex.cc (3629)
V1004 The 'b->yy_ch_buf' pointer was used unsafely after it was verified against nullptr. Check lines: 3625, 3629.
lex.cc (3619)
V1028 Possible overflow. Consider casting operands of the 'b->yy_buf_size + 2' operator to the 'yy_size_t' type, not the result.
lex.cc (3909)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 3898, 3909.
lex.cc (3943)
V1004 The 'b' pointer was used unsafely after it was verified against nullptr. Check lines: 3940, 3943.
lex.cc (3948)
V1028 Possible overflow. Consider casting operands of the 'b->yy_buf_size + 2' operator to the 'yy_size_t' type, not the result.
lex.cc (4062)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 4051, 4062.
lex.cc (4080)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 4076, 4080.
lex.cc (4111)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 4108, 4111.
lex.cc (4157)
V1004 The 'b' pointer was used unsafely after it was verified against nullptr. Check lines: 4154, 4157.
lex.cc (4201)
V1028 Possible overflow. Consider casting operands of the '_yybytes_len + 2' operator to the 'yy_size_t' type, not the result.
lex.cc (4209)
V1004 The 'buf' pointer was used unsafely after it was verified against nullptr. Check lines: 4203, 4209.
lex.cc (4218)
V1004 The 'b' pointer was used unsafely after it was verified against nullptr. Check lines: 4212, 4218.
lex.cc (4273)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 4270, 4273.
lex.cc (4286)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 4283, 4286.
lex.cc (4348)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 4345, 4348.
lex.cc (4363)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 4360, 4363.
lex.ll (2796)
V576 Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the uintmax_t type is expected.
oct-parse.yy (3346)
V668 There is no sense in testing the 'fcn' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
oct-parse.yy (3866)
V522 There might be dereferencing of a potential null pointer 'fcn_def'.
oct-parse.yy (4093)
V522 There might be dereferencing of a potential null pointer 'al'.
pt-arg-list.cc (138)
V522 There might be dereferencing of a potential null pointer 'id'.
pt-arg-list.cc (145)
V522 There might be dereferencing of a potential null pointer 'idx_expr'.
pt-assign.cc (38)
V730 Not all members of a class are initialized inside the constructor. Consider inspecting: m_ans_assign.
pt-bp.cc (449)
V547 Expression 'm_action == list' is always true.
pt-bp.cc (480)
V547 Expression 'm_action == list' is always true.
pt-eval.cc (193)
V773 The function was exited without releasing the 'lxr' pointer. A memory leak is possible.
pt-eval.cc (237)
V522 There might be dereferencing of a potential null pointer 'id'.
pt-eval.cc (1973)
V522 There might be dereferencing of a potential null pointer 'id'.
pt-eval.cc (2791)
V522 There might be dereferencing of a potential null pointer 'id'.
pt-eval.cc (3467)
V522 There might be dereferencing of a potential null pointer.
pt-eval.cc (3529)
V522 There might be dereferencing of a potential null pointer 'fcn'.
pt-eval.cc (3745)
V522 There might be dereferencing of a potential null pointer 'code'.
__magick_read__.cc (417)
V636 The expression was implicitly cast from 'unsigned long long' type to 'double' type. Consider utilizing an explicit type cast to avoid the loss of a fractional part. An example: double A = (double)(X) / Y;.
__qp__.cc (257)
V547 Expression 'pR == 0' is always true.
__qp__.cc (261)
V547 Expression 'pR == 0' is always true.
besselj.cc (133)
V614 Potentially uninitialized variable 'ierr' used.
besselj.cc (223)
V614 Potentially uninitialized variable 'ierr' used.
DAERTFunc.h (86)
V703 It is odd that the 'reset' field in derived class 'DAERTFunc' overwrites field in base class 'DAEFunc'. Check lines: DAERTFunc.h:86, DAEFunc.h:101.
oct-binmap.h (325)
V560 A part of conditional expression is always true: jy_lt_max.
defaults.cc (102)
V560 A part of conditional expression is always true: op == oep.
defun.cc (196)
V522 There might be dereferencing of a potential null pointer 'dld'.
defun.cc (202)
V522 There might be dereferencing of a potential null pointer 'mex'.
display.cc (70)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
dot.cc (300)
V560 A part of conditional expression is always true: match.
error.cc (460)
V764 Possible incorrect order of arguments passed to 'vmessage_with_id' function: 'name' and 'id'.
fcn-info.cc (414)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 379, 414.
fcn-info.cc (631)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 594, 631.
ft-text-renderer.cc (153)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
ft-text-renderer.cc (788)
V560 A part of conditional expression is always false: x0 + c < 0.
ft-text-renderer.cc (376)
V730 Not all members of a class are initialized inside the constructor. Consider inspecting: line_xoffset.
graphics-props.cc (123)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 121, 123.
graphics-props.cc (972)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 970, 972.
graphics-props.cc (974)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 972, 974.
graphics-props.cc (976)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 974, 976.
graphics-props.cc (978)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 976, 978.
graphics-props.cc (980)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 978, 980.
graphics-props.cc (982)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 980, 982.
graphics-props.cc (984)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 982, 984.
graphics-props.cc (986)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 984, 986.
graphics-props.cc (988)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 986, 988.
graphics-props.cc (990)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 988, 990.
graphics-props.cc (992)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 990, 992.
graphics-props.cc (994)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 992, 994.
graphics-props.cc (996)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 994, 996.
graphics-props.cc (998)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 996, 998.
graphics-props.cc (1000)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 998, 1000.
graphics-props.cc (1002)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 1000, 1002.
graphics-props.cc (1004)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 1002, 1004.
graphics-props.cc (1006)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 1004, 1006.
graphics-props.cc (1008)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 1006, 1008.
graphics-props.cc (1010)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 1008, 1010.
graphics-props.cc (1012)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 1010, 1012.
graphics-props.cc (2173)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 2171, 2173.
graphics-props.cc (2175)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 2173, 2175.
graphics-props.cc (2177)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 2175, 2177.
graphics-props.cc (2179)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 2177, 2179.
graphics-props.cc (2181)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 2179, 2181.
graphics-props.cc (3142)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3140, 3142.
graphics-props.cc (3144)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3142, 3144.
graphics-props.cc (3146)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3144, 3146.
graphics-props.cc (3148)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3146, 3148.
graphics-props.cc (3150)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3148, 3150.
graphics-props.cc (3584)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3582, 3584.
graphics-props.cc (3586)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3584, 3586.
graphics-props.cc (3588)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3586, 3588.
graphics-props.cc (3590)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3588, 3590.
graphics-props.cc (3592)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3590, 3592.
graphics-props.cc (3594)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3592, 3594.
graphics-props.cc (3596)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3594, 3596.
graphics-props.cc (3598)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3596, 3598.
graphics-props.cc (3600)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3598, 3600.
graphics-props.cc (3602)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3600, 3602.
graphics-props.cc (3604)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 3602, 3604.
graphics-props.cc (4022)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4020, 4022.
graphics-props.cc (4024)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4022, 4024.
graphics-props.cc (4026)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4024, 4026.
graphics-props.cc (4028)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4026, 4028.
graphics-props.cc (4030)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4028, 4030.
graphics-props.cc (4032)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4030, 4032.
graphics-props.cc (4034)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4032, 4034.
graphics-props.cc (4036)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4034, 4036.
graphics-props.cc (4038)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4036, 4038.
graphics-props.cc (4677)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4675, 4677.
graphics-props.cc (4679)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4677, 4679.
graphics-props.cc (4681)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4679, 4681.
graphics-props.cc (4683)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4681, 4683.
graphics-props.cc (4685)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4683, 4685.
graphics-props.cc (4687)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4685, 4687.
graphics-props.cc (4689)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4687, 4689.
graphics-props.cc (4691)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4689, 4691.
graphics-props.cc (4693)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 4691, 4693.
graphics-props.cc (5333)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5331, 5333.
graphics-props.cc (5335)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5333, 5335.
graphics-props.cc (5337)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5335, 5337.
graphics-props.cc (5339)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5337, 5339.
graphics-props.cc (5341)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5339, 5341.
graphics-props.cc (5343)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5341, 5343.
graphics-props.cc (5345)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5343, 5345.
graphics-props.cc (5347)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5345, 5347.
graphics-props.cc (5349)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5347, 5349.
graphics-props.cc (5824)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5822, 5824.
graphics-props.cc (5826)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5824, 5826.
graphics-props.cc (5828)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5826, 5828.
graphics-props.cc (5830)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5828, 5830.
graphics-props.cc (5832)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5830, 5832.
graphics-props.cc (5834)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5832, 5834.
graphics-props.cc (5836)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5834, 5836.
graphics-props.cc (5838)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5836, 5838.
graphics-props.cc (5840)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 5838, 5840.
graphics-props.cc (6110)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 6108, 6110.
graphics-props.cc (6632)
V581 The conditional expressions of the 'if' statements situated alongside each other are identical. Check lines: 6630, 6632.
graphics.cc (9519)
V656 Variables 'xd', 'yd' are initialized through the call to the same function. It's probably an error or un-optimized code. Consider inspecting the 'idx.dims()' expression. Check lines: 9518, 9519.
graphics.cc (11224)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
graphics.cc (11417)
V730 Not all members of a class are initialized inside the constructor. Consider inspecting: notify_toolkit.
inv.cc (200)
V614 Potentially uninitialized variable 'info' used.
load-save.cc (659)
V1024 The 'is' stream is checked for EOF before reading from it, but is not checked after reading. Potential use of invalid data.
load-save.cc (1049)
V636 The 'val.byte_size() / 1024' expression was implicitly cast from 'size_t' type to 'double' type. Consider utilizing an explicit type cast to avoid the loss of a fractional part. An example: double A = (double)(X) / Y;.
load-save.cc (1510)
V560 A part of conditional expression is always false: append.
ls-hdf5.cc (1011)
V547 Expression 'retval >= 0' is always true.
ls-mat-ascii.cc (273)
V560 A part of conditional expression is always false: nr < 1.
ls-mat-ascii.cc (273)
V560 A part of conditional expression is always false: nc < 1.
ls-mat5.cc (501)
V728 An excessive check can be simplified. The '(A && !B) || (!A && B)' expression is equivalent to the 'bool(A) != bool(B)' expression.
ls-mat5.cc (2013)
V560 A part of conditional expression is always true: nel > 0.
ls-mat5.cc (2013)
V560 A part of conditional expression is always true.
ls-mat5.cc (2013)
V560 A part of conditional expression is always false.
ls-mat5.cc (2183)
V547 Expression '6 > max_namelen' is always false.
ls-oct-text.cc (403)
V560 A part of conditional expression is always true: !fail.
lu.cc (171)
V656 Variables 'thres(0)', 'thres(1)' are initialized through the call to the same function. It's probably an error or un-optimized code. Consider inspecting the 'tmp(0)' expression. Check lines: 170, 171.
mex.cc (289)
V522 There might be dereferencing of a potential null pointer 'dims'. Check lines: 289, 283.
mex.cc (432)
V601 The bool type is implicitly cast to the double type.
mex.cc (681)
V522 There might be dereferencing of a potential null pointer 'dims'. Check lines: 681, 677.
mex.cc (708)
V522 There might be dereferencing of a potential null pointer 'dims'. Check lines: 708, 705.
mex.cc (723)
V522 There might be dereferencing of a potential null pointer 'dims'. Check lines: 723, 721.
mex.cc (733)
V522 There might be dereferencing of a potential null pointer 'dims'. Check lines: 733, 730.
mex.cc (893)
V575 The potential null pointer is passed into 'strcpy' function. Inspect the first argument. Check lines: 893, 892.
mex.cc (1225)
V601 The bool type is implicitly cast to the double type.
mex.cc (1708)
V522 There might be dereferencing of a potential null pointer 'fields'. Check lines: 1708, 1701.
mex.cc (1819)
V522 There might be dereferencing of a potential null pointer 'new_fields'. Check lines: 1819, 1812.
mex.cc (1835)
V522 There might be dereferencing of a potential null pointer 'new_data'. Check lines: 1835, 1815.
mex.cc (1955)
V522 There might be dereferencing of a potential null pointer 'data'. Check lines: 1955, 1947.
mex.cc (3173)
V506 Pointer to local variable 'context' is stored outside the scope of this variable. Such a pointer will become invalid.
oct-hdf5-types.cc (43)
V560 A part of conditional expression is always false: !ok.
oct-hdf5-types.cc (50)
V560 A part of conditional expression is always false: !ok.
oct-stream.cc (893)
V764 Possible incorrect order of arguments passed to 'process_conversion' function: 'type' and 'modifier'.
oct-stream.cc (1272)
V768 The variable 'flags' is of enum type. It is odd that it is used as a variable of a Boolean-type.
oct-stream.cc (2495)
V560 A part of conditional expression is always true: !progress.
oct-stream.cc (2789)
V547 Expression 'width_left' is always true.
oct-stream.cc (2838)
V547 Expression 'width_left' is always true.
oct-stream.cc (2846)
V547 Expression 'width_left' is always true.
oct-stream.cc (2510)
V730 Not all members of a class are initialized inside the constructor. Consider inspecting: delim_len.
oct-tex-lexer.ll (108)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 108, 108.
oct-tex-lexer.ll (118)
V519 The 'yyg->yy_c_buf_p' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 118, 118.
oct-tex-lexer.cc (2216)
V1028 Possible overflow. Consider casting operands of the 'b->yy_buf_size + 2' operator to the 'yy_size_t' type, not the result.
oct-tex-lexer.cc (2503)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 2492, 2503.
oct-tex-lexer.cc (2542)
V1028 Possible overflow. Consider casting operands of the 'b->yy_buf_size + 2' operator to the 'yy_size_t' type, not the result.
oct-tex-lexer.cc (2656)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 2645, 2656.
oct-tex-lexer.cc (2674)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 2670, 2674.
oct-tex-lexer.cc (2795)
V1028 Possible overflow. Consider casting operands of the '_yybytes_len + 2' operator to the 'yy_size_t' type, not the result.
oct-tex-lexer.cc (2867)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 2864, 2867.
oct-tex-lexer.cc (2880)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 2877, 2880.
oct-tex-lexer.cc (2942)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 2939, 2942.
oct-tex-lexer.cc (2957)
V1004 The 'yyg->yy_buffer_stack' pointer was used unsafely after it was verified against nullptr. Check lines: 2954, 2957.
oct-tex-parser.cc (1638)
V557 Array underrun is possible. The value of 'yyn - 20' index could reach -20.
oct-tex-parser.cc (1642)
V557 Array underrun is possible. The value of 'yyn - 20' index could reach -20.
pager.cc (390)
V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions '!m_page_screen_output' and 'm_page_screen_output'.
pager.cc (429)
V668 There is no sense in testing the 'm_external_pager' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
pr-output.cc (415)
V560 A part of conditional expression is always false: inf_or_nan.
pr-output.cc (517)
V560 A part of conditional expression is always false: fw < 5.
pr-output.cc (690)
V560 A part of conditional expression is always false: r_fw < 5.
pr-output.cc (758)
V560 A part of conditional expression is always false: inf_or_nan.
pr-output.cc (909)
V560 A part of conditional expression is always false: r_fw < 5.
pr-output.cc (1840)
V560 A part of conditional expression is always true: j < lim.
pr-output.cc (1956)
V560 A part of conditional expression is always true: j < lim.
pr-output.cc (2094)
V547 Expression 'i < m' is always true.
pr-output.cc (2250)
V560 A part of conditional expression is always true: j < lim.
pr-output.cc (2694)
V547 Expression 'i < m' is always true.
syminfo.cc (531)
V614 Potentially uninitialized variable 'param.balance' used.
utils.cc (188)
V668 There is no sense in testing the 's2' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
utils.cc (1103)
V656 Variables 'dim(0)', 'dim(1)' are initialized through the call to the same function. It's probably an error or un-optimized code. Consider inspecting the 'v(0)' expression. Check lines: 1102, 1103.
zfstream.cc (282)
V1004 The 'buffer' pointer was used unsafely after it was verified against nullptr. Check lines: 271, 282.
CDiagMatrix.cc (250)
V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'r <= c' and 'r > c'.
CDiagMatrix.cc (262)
V1004 The 's' pointer was used unsafely after it was verified against nullptr. Check lines: 259, 262.
CDiagMatrix.cc (269)
V591 Non-void function should return a value.
CDiagMatrix.cc (280)
V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'r >= c' and 'r < c'.
CDiagMatrix.cc (292)
V1004 The 's' pointer was used unsafely after it was verified against nullptr. Check lines: 289, 292.
CDiagMatrix.cc (299)
V591 Non-void function should return a value.
Array.h (454)
V512 Instantiation of Array < F77_INT >: A call of the 'compute_index' function will lead to overflow of the buffer 'ra_idx.data()'.
CSparse.cc (5731)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
CSparse.cc (5744)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
CSparse.cc (5983)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
CSparse.cc (6006)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
CSparse.cc (6286)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
CSparse.cc (6299)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
CSparse.cc (6517)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
CSparse.cc (6540)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
CSparse.cc (7774)
V560 A part of conditional expression is always true: jb_lt_max.
CSparse.cc (7891)
V560 A part of conditional expression is always true: jb_lt_max.
dDiagMatrix.cc (173)
V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'r <= c' and 'r > c'.
dDiagMatrix.cc (185)
V1004 The 's' pointer was used unsafely after it was verified against nullptr. Check lines: 182, 185.
dDiagMatrix.cc (192)
V591 Non-void function should return a value.
dDiagMatrix.cc (203)
V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'r >= c' and 'r < c'.
dDiagMatrix.cc (215)
V1004 The 's' pointer was used unsafely after it was verified against nullptr. Check lines: 212, 215.
dDiagMatrix.cc (222)
V591 Non-void function should return a value.
dSparse.cc (4725)
V614 Uninitialized variable 'anorm' used.
dSparse.cc (5064)
V614 Uninitialized variable 'anorm' used.
dSparse.cc (5418)
V614 Uninitialized variable 'anorm' used.
dSparse.cc (5772)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
dSparse.cc (5785)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
dSparse.cc (5997)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
dSparse.cc (6020)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
dSparse.cc (6270)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
dSparse.cc (6283)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
dSparse.cc (6515)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
dSparse.cc (6538)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
dSparse.cc (7732)
V560 A part of conditional expression is always true: jb_lt_max.
dSparse.cc (7882)
V560 A part of conditional expression is always true: jb_lt_max.
fCDiagMatrix.cc (254)
V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'r <= c' and 'r > c'.
fCDiagMatrix.cc (266)
V1004 The 's' pointer was used unsafely after it was verified against nullptr. Check lines: 263, 266.
fCDiagMatrix.cc (273)
V591 Non-void function should return a value.
fCDiagMatrix.cc (284)
V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'r >= c' and 'r < c'.
fCDiagMatrix.cc (296)
V1004 The 's' pointer was used unsafely after it was verified against nullptr. Check lines: 293, 296.
fCDiagMatrix.cc (303)
V591 Non-void function should return a value.
fDiagMatrix.cc (173)
V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'r <= c' and 'r > c'.
fDiagMatrix.cc (185)
V1004 The 's' pointer was used unsafely after it was verified against nullptr. Check lines: 182, 185.
fDiagMatrix.cc (192)
V591 Non-void function should return a value.
fDiagMatrix.cc (203)
V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions 'r >= c' and 'r < c'.
fDiagMatrix.cc (215)
V1004 The 's' pointer was used unsafely after it was verified against nullptr. Check lines: 212, 215.
fDiagMatrix.cc (222)
V591 Non-void function should return a value.
idx-vector.cc (108)
V591 Non-void function should return a value.
idx-vector.cc (820)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (830)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (853)
V522 There might be dereferencing of a potential null pointer 'rj'.
idx-vector.cc (868)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (869)
V522 There might be dereferencing of a potential null pointer 'rj'.
idx-vector.cc (882)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (886)
V522 There might be dereferencing of a potential null pointer 'rj'.
idx-vector.cc (910)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (910)
V522 There might be dereferencing of a potential null pointer 'rj'.
idx-vector.cc (921)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (924)
V522 There might be dereferencing of a potential null pointer 'rj'.
idx-vector.cc (934)
V522 There might be dereferencing of a potential null pointer 'rj'.
idx-vector.cc (968)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (980)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (989)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (1018)
V522 There might be dereferencing of a potential null pointer 'dynamic_cast< idx_range_rep * > (rep)'.
idx-vector.cc (1046)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (1063)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (1078)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (1085)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (1093)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (1118)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (1187)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (1208)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (1211)
V781 The value of the 'len' variable is checked after it was used. Perhaps there is a mistake in program logic. Check lines: 1211, 1217.
idx-vector.cc (1239)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (1246)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (1253)
V522 There might be dereferencing of a potential null pointer 'r'.
idx-vector.cc (1260)
V522 There might be dereferencing of a potential null pointer 'r'.
MatrixType.cc (485)
V586 The 'delete' operator is called twice for deallocation of the same memory space.
DASPK.cc (62)
V707 Giving short names to global variables is considered to be bad practice. It is suggested to rename 'nn' variable.
DASPK.cc (358)
V560 A part of conditional expression is always true: eiq == 3.
DASPK.cc (403)
V560 A part of conditional expression is always true: eiq == 3.
DASRT.cc (60)
V707 Giving short names to global variables is considered to be bad practice. It is suggested to rename 'nn' variable.
DASSL.cc (57)
V707 Giving short names to global variables is considered to be bad practice. It is suggested to rename 'nn' variable.
gsvd.cc (535)
V560 A part of conditional expression is always false: jobu == 'O'.
gsvd.cc (540)
V560 A part of conditional expression is always false: jobv == 'O'.
gsvd.cc (545)
V560 A part of conditional expression is always false: jobq == 'O'.
Quad.cc (160)
V591 Non-void function should return a value.
Quad.cc (224)
V591 Non-void function should return a value.
Quad.cc (230)
V591 Non-void function should return a value.
Quad.cc (277)
V591 Non-void function should return a value.
Array.h (454)
V512 Instantiation of Array <float>: A call of the 'compute_index' function will lead to overflow of the buffer 'ra_idx.data()'.
eigs-base.cc (349)
V614 Uninitialized variable 'info' used.
eigs-base.cc (386)
V614 Uninitialized variable 'info' used.
eigs-base.cc (1706)
V560 A part of conditional expression is always true: mode == 1.
eigs-base.cc (1724)
V560 A part of conditional expression is always true: mode == 1.
oct-fftw.cc (116)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
oct-fftw.cc (476)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
oct-norm.cc (466)
V764 Possible incorrect order of arguments passed to 'dual_p' function: 'q' and 'p'.
oct-rand.cc (67)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
oct-spparms.cc (47)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
sparse-chol.cc (283)
V506 Pointer to local variable 'dummy' is stored outside the scope of this variable. Such a pointer will become invalid.
svd.cc (350)
V560 A part of conditional expression is always false: jobu == 'O'.
svd.cc (358)
V560 A part of conditional expression is always false: jobv == 'O'.
smx-scm-sm.cc (10)
V501 There are identical sub-expressions to the left and to the right of the '/' operator: Complex() / Complex()
smx-sm-scm.cc (10)
V501 There are identical sub-expressions to the left and to the right of the '/' operator: Complex() / Complex()
lo-sysdep.cc (63)
V1004 The 'tmp' pointer was used unsafely after it was verified against nullptr. Check lines: 60, 63.
lo-sysdep.cc (173)
V575 The potential null pointer is passed into 'sprintf' function. Inspect the first argument. Check lines: 173, 171.
lo-sysinfo.cc (69)
V547 Expression '!retval.empty()' is always false.
oct-env.cc (89)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
cmd-edit.cc (836)
V575 The potential null pointer is passed into 'strcpy' function. Inspect the first argument. Check lines: 836, 834.
cmd-edit.cc (857)
V575 The potential null pointer is passed into 'strcpy' function. Inspect the first argument. Check lines: 857, 855.
cmd-edit.cc (878)
V575 The potential null pointer is passed into 'strcpy' function. Inspect the first argument. Check lines: 878, 876.
cmd-edit.cc (909)
V519 The 'matches' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 908, 909.
cmd-edit.cc (1844)
V601 The integer type is implicitly cast to the char type.
cmd-edit.cc (1737)
V536 Be advised that the utilized constant value is represented by an octal form. Oct: '\033', Dec: 27.
kpse.cc (784)
V560 A part of conditional expression is always true: dir.length() > 0.
kpse.cc (970)
V560 A part of conditional expression is always true: !quoted.
lo-hash.cc (140)
V591 Non-void function should return a value.
lo-regexp.cc (127)
V555 The expression 'new_pos - pos > 0' will work as 'new_pos != pos'.
lo-utils.cc (113)
V575 The potential null pointer is passed into 'fgets' function. Inspect the first argument. Check lines: 113, 104.
lo-utils.cc (129)
V769 The 'buf' pointer in the 'buf + tmp' expression could be nullptr. In such case, resulting value will be senseless and it should not be used. Check lines: 129, 122.
oct-mutex.cc (45)
V524 It is odd that the body of 'unlock' function is fully equivalent to the body of 'lock' function.
singleton-cleanup.cc (48)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
oct-rl-edit.c (201)
V575 The potential null pointer is passed into 'strcpy' function. Inspect the first argument. Check lines: 201, 201.
oct-rl-edit.c (293)
V575 The potential null pointer is passed into 'strcpy' function. Inspect the first argument. Check lines: 293, 293.
oct-rl-edit.c (301)
V575 The potential null pointer is passed into 'strcpy' function. Inspect the first argument. Check lines: 301, 301.
oct-rl-edit.c (321)
V575 The potential null pointer is passed into 'strcpy' function. Inspect the first argument. Check lines: 321, 321.
oct-rl-edit.c (329)
V575 The potential null pointer is passed into 'strcpy' function. Inspect the first argument. Check lines: 329, 329.
oct-rl-edit.c (337)
V575 The potential null pointer is passed into 'strcpy' function. Inspect the first argument. Check lines: 337, 337.
oct-rl-edit.c (435)
V575 The potential null pointer is passed into 'strcpy' function. Inspect the first argument. Check lines: 435, 435.
oct-rl-hist.c (279)
V1028 Possible overflow. Consider casting operands of the 'end - beg + 1' operator to the 'size_t' type, not the result.
oct-rl-hist.c (289)
V575 The potential null pointer is passed into 'sprintf' function. Inspect the first argument. Check lines: 289, 286.
oct-rl-hist.c (294)
V522 There might be dereferencing of a potential null pointer 'retval'. Check lines: 294, 279.
BlockArray.h (32)
V730 Not all members of a class are initialized inside the constructor. Consider inspecting: data.
CharacterColor.h (261)
V640 The code's operational logic does not correspond with its formatting. The second statement will always be executed. It is possible that curly brackets are missing.
History.cpp (83)
V730 Not all members of a class are initialized inside the constructor. Consider inspecting: readWriteBalance.
KeyboardTranslator.cpp (702)
V576 Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the unsigned int type is expected.
ScreenWindow.cpp (31)
V730 Not all members of a class are initialized inside the constructor. Consider inspecting: _screen.
Vt102Emulation.cpp (1164)
V560 A part of conditional expression is always false: m == 5.
Vt102Emulation.cpp (1187)
V560 A part of conditional expression is always false: m == 5.
TerminalView.cpp (856)
V688 The '_clipboard' local variable possesses the same name as one of the class members, which can result in a confusion.
TerminalView.cpp (942)
V519 The '_fixedFont' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 938, 942.
TerminalView.cpp (1669)
V728 An excessive check can be simplified. The '||' operator is surrounded by opposite expressions '_mouseMarks' and '!_mouseMarks'.
documentation.cc (96)
V595 The 'm_help_engine' pointer was utilized before it was verified against nullptr. Check lines: 96, 110.
file-editor.h (412)
V703 It is odd that the 'm_close_action' field in derived class 'file_editor' overwrites field in base class 'label_dock_widget'. Check lines: file-editor.h:412, octave-dock-widget.h:72.
file-editor-tab.cc (236)
V1004 The 'settings' pointer was used unsafely after it was verified against nullptr. Check lines: 226, 236.
file-editor-tab.cc (622)
V668 There is no sense in testing the 'lexer' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
file-editor.cc (449)
V668 There is no sense in testing the 'fileEditorTab' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
file-editor.cc (1330)
V668 There is no sense in testing the 'fileEditorTab' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
octave-gui.cc (42)
V730 Not all members of a class are initialized inside the constructor. Consider inspecting: m_argc, m_argv.
resource-manager.cc (179)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
resource-manager.cc (297)
V668 There is no sense in testing the 'm_settings' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
shortcut-manager.cc (175)
V668 There is no sense in testing the 'instance' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
shortcut-manager.cc (698)
V668 There is no sense in testing the 'osc_settings' pointer against null, as the memory was allocated using the 'new' operator. The exception will be generated in the case of memory allocation error.
workspace-model.cc (42)
V730 It is possible that not all members of a class are initialized inside the constructor. Consider inspecting: m_top_level, m_enable_colors.