Group |
Location |
Level |
Code |
Message |
General Analysis |
agg_curves.h:377 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_distance_tolerance_square. |
General Analysis |
agg_curves.h:97 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_distance_tolerance_square. |
General Analysis |
agg_image_accessors.h:236 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_x. |
General Analysis |
agg_path_storage_integer.h:217 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_scale. |
General Analysis |
agg_rasterizer_scanline_aa.h:125 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_scan_y. |
General Analysis |
agg_scanline_bin.h:186 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_y. |
General Analysis |
agg_scanline_bin.h:57 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_y. |
General Analysis |
agg_scanline_p.h:222 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_y. |
General Analysis |
agg_scanline_p.h:60 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_y. |
General Analysis |
agg_scanline_storage_aa.h:610 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_dx. |
General Analysis |
agg_scanline_storage_bin.h:402 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_dx. |
General Analysis |
agg_scanline_u.h:347 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_y. |
General Analysis |
agg_scanline_u.h:128 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_y. |
General Analysis |
agg_span_image_filter.h:110 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_rx, m_ry, m_rx_inv, m_ry_inv. |
General Analysis |
agg_span_image_filter_rgba.h:898 |
High |
V570 |
The 'fg[order_type::R]' variable is assigned to itself. |
General Analysis |
agg_span_image_filter_rgba.h:898 |
High |
V501 |
There are identical sub-expressions to the left and to the right of the '>' operator: fg[order_type::R] > fg[order_type::R] |
General Analysis |
agg_span_image_filter_rgba.h:899 |
High |
V501 |
There are identical sub-expressions to the left and to the right of the '>' operator: fg[order_type::G] > fg[order_type::G] |
General Analysis |
agg_span_image_filter_rgba.h:900 |
High |
V501 |
There are identical sub-expressions to the left and to the right of the '>' operator: fg[order_type::B] > fg[order_type::B] |
General Analysis |
agg_span_image_filter_rgba.h:899 |
High |
V570 |
The 'fg[order_type::G]' variable is assigned to itself. |
General Analysis |
agg_span_image_filter_rgba.h:900 |
High |
V570 |
The 'fg[order_type::B]' variable is assigned to itself. |
General Analysis |
agg_span_interpolator_linear.h:128 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_src_x, m_src_y, m_pos, m_len. |
General Analysis |
ALMLayout.h:196 |
High |
V762 |
It is possible a virtual function was overridden incorrectly. See second argument of function 'Archive' in derived class 'DefaultPolicy' and base class 'BArchivable'. |
General Analysis |
PackageAttributeValue.h:52 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: encoding. |
General Analysis |
PackageAttributeValue.h:54 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: encoding. |
General Analysis |
Referenceable.h:228 |
High |
V591 |
Non-void function should return a value. |
General Analysis |
Referenceable.h:233 |
High |
V591 |
Non-void function should return a value. |
General Analysis |
Referenceable.h:239 |
High |
V591 |
Non-void function should return a value. |
General Analysis |
ValueLocation.h:45 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: size, bitSize, bitOffset. |
General Analysis |
MinMaxHeap.h:112 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMinTree. |
General Analysis |
AddressUtilities.h:244 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fAddressStorage. |
General Analysis |
Strings.h:30 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
EntryFilter.h:26 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNextFilter. |
General Analysis |
RWLockManager.h:25 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: status. |
General Analysis |
Thread.h:354 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fThreadID. |
General Analysis |
Requests.h:519 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: size. |
General Analysis |
Requests.h:750 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: size. |
General Analysis |
Requests.h:606 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: request. |
General Analysis |
Requests.h:683 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: ioctlError. |
General Analysis |
Requests.h:694 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: flags. |
General Analysis |
Requests.h:768 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: mode. |
General Analysis |
Requests.h:758 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: bytesRead. |
General Analysis |
Requests.h:785 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: target. |
General Analysis |
Requests.h:1623 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: node. |
General Analysis |
Requests.h:511 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: vnid. |
General Analysis |
Requests.h:909 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fileCookie. |
General Analysis |
Requests.h:474 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: info. |
General Analysis |
Requests.h:570 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: reenter. |
General Analysis |
Requests.h:345 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: queryCookie. |
General Analysis |
Requests.h:834 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: mode. |
General Analysis |
Requests.h:337 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: indexDirCookie. |
General Analysis |
Requests.h:329 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: attrCookie. |
General Analysis |
Requests.h:321 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: attrDirCookie. |
General Analysis |
Requests.h:313 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: dirCookie. |
General Analysis |
Requests.h:305 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fileCookie. |
General Analysis |
Requests.h:297 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: node. |
General Analysis |
Requests.h:289 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: volume. |
General Analysis |
Requests.h:266 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: error. |
General Analysis |
Requests.h:556 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: reenter. |
General Analysis |
Requests.h:501 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: traverseLink. |
General Analysis |
Requests.h:854 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: st. |
General Analysis |
Requests.h:1060 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: count. |
General Analysis |
Requests.h:1435 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: st. |
General Analysis |
Requests.h:1526 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: listener. |
General Analysis |
Requests.h:1500 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: count. |
General Analysis |
Requests.h:1459 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: queryCookie. |
General Analysis |
Requests.h:901 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: openMode. |
General Analysis |
Requests.h:1372 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: count. |
General Analysis |
Requests.h:1330 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: indexDirCookie. |
General Analysis |
Requests.h:1264 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: st. |
General Analysis |
Requests.h:1250 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: bytesWritten. |
General Analysis |
Requests.h:1774 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: enabled. |
General Analysis |
Requests.h:1229 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: bytesRead. |
General Analysis |
Requests.h:1789 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: size. |
General Analysis |
Requests.h:1827 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: bytesRead. |
General Analysis |
Requests.h:1849 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: bytesWritten. |
General Analysis |
Requests.h:1882 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: size. |
General Analysis |
Requests.h:1188 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: attrCookie. |
General Analysis |
Requests.h:1178 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: openMode. |
General Analysis |
Requests.h:1170 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: attrCookie. |
General Analysis |
Requests.h:1092 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: attrDirCookie. |
General Analysis |
Requests.h:1133 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: count. |
General Analysis |
Requests.h:1915 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: status. |
General Analysis |
Requests.h:1019 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: dirCookie. |
General Analysis |
Requests.h:982 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: mode. |
General Analysis |
Requests.h:970 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: bytesWritten. |
General Analysis |
Requests.h:950 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: bytesRead. |
General Analysis |
Requests.h:960 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: pos. |
General Analysis |
Requests.h:1736 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: removed. |
General Analysis |
Requests.h:1748 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: size. |
General Analysis |
i2c.c:276 |
High |
V564 |
The '|' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '||' operator. |
General Analysis |
commands.h:95 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: color. |
General Analysis |
commands.h:83 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: source_left, source_top. |
General Analysis |
commands.h:106 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: background_color, foreground_color, pattern. |
General Analysis |
commands.h:51 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: dest_left, dest_top, dest_right, dest_bottom. |
General Analysis |
mode.cpp:426 |
High |
V595 |
The 'mode' pointer was utilized before it was verified against nullptr. Check lines: 426, 429. |
General Analysis |
Ports.cpp:994 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMaxLanes. |
General Analysis |
Ports.cpp:68 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCurrentMode, fEDIDInfo. |
General Analysis |
tvp3026.c:212 |
High |
V654 |
The condition 'nogscale >= 0' of loop is always true. |
General Analysis |
InitAccelerant.c:192 |
High |
V547 |
Expression 'result != ((int) 0)' is always false. |
General Analysis |
nv_crtc.c:836 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
nv_crtc.c:834 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
nv_crtc.c:846 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
nv_crtc.c:832 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
nv_crtc2.c:806 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
nv_crtc2.c:796 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
nv_crtc2.c:794 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
nv_crtc2.c:792 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
InitAccelerant.c:192 |
High |
V547 |
Expression 'result != ((int) 0)' is always false. |
General Analysis |
multimon.c:251 |
High |
V590 |
Consider inspecting this expression. The expression is excessive or contains a misprint. |
General Analysis |
overlay.c:852 |
High |
V712 |
Be advised that compiler may delete this cycle or make it infinity. Use volatile variable(s) or synchronization primitives to avoid this. |
General Analysis |
SetDisplayMode.c:521 |
High |
V547 |
Expression 'err2 == ((int) 0)' is always true. |
General Analysis |
SetDisplayMode.c:519 |
High |
V547 |
Expression 'err1 == ((int) 0)' is always true. |
General Analysis |
crtc.c:625 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
crtc2.c:637 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
crtc2.c:639 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
crtc2.c:651 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
crtc2.c:641 |
High |
V616 |
The 'curadd' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
i2c.c:111 |
High |
V547 |
Expression 'count > 100' is always false. |
General Analysis |
info.c:48 |
High |
V547 |
Expression 'result == (- 1)' is always true. |
General Analysis |
InitAccelerant.c:180 |
High |
V547 |
Expression 'result != ((int) 0)' is always false. |
General Analysis |
SetDisplayMode.c:492 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
ExtendedPartitionAddOn.cpp:154 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fPrimaryPartition. |
General Analysis |
TeamMonitorWindow.cpp:693 |
High |
V595 |
The 'fInfoTextView' pointer was utilized before it was verified against nullptr. Check lines: 693, 699. |
General Analysis |
MouseInputDevice.cpp:166 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTouchpadSettings. |
General Analysis |
TabletInputDevice.cpp:145 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSettings. |
General Analysis |
TabletDevice.cpp:37 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fDataBytes, fWheelX, fWheelY, fLastClickTime, fJitterX, fJitterY. |
General Analysis |
CommandActuators.cpp:198 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
CommandActuators.cpp:1680 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
CommandActuators.cpp:1021 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
dscontrol.c:307 |
High |
V724 |
Converting type 'UINT16' to type 'BOOLEAN' can lead to a loss of high-order bits. Non-zero value can become 'FALSE'. |
General Analysis |
dswexec.c:361 |
High |
V595 |
The 'OutOp' pointer was utilized before it was verified against nullptr. Check lines: 361, 382. |
General Analysis |
dswload.c:609 |
High |
V595 |
The 'Op->Common.Value.Arg' pointer was utilized before it was verified against nullptr. Check lines: 609, 631. |
General Analysis |
evglock.c:390 |
High |
V724 |
Converting type 'int' to type 'BOOLEAN' can lead to a loss of high-order bits. Non-zero value can become 'FALSE'. |
General Analysis |
evglock.c:464 |
High |
V724 |
Converting type 'int' to type 'BOOLEAN' can lead to a loss of high-order bits. Non-zero value can become 'FALSE'. |
General Analysis |
hwgpe.c:266 |
High |
V784 |
The size of the bit mask is less than the size of the first operand. This will cause the loss of higher bits. |
General Analysis |
nssearch.c:449 |
High |
V547 |
Expression 'Status == (ACPI_STATUS) 0x0000' is always true. |
General Analysis |
EmbeddedController.cpp:287 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors and destructors. |
General Analysis |
NamespaceDump.cpp:104 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:113 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:101 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:118 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:119 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:120 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:123 |
High |
645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:107 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:126 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:132 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:135 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:138 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:141 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:144 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:129 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
NamespaceDump.cpp:110 |
High |
V645 |
The 'strncat' function call could lead to the 'output' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
agp_gart.cpp:417 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNext. |
General Analysis |
agp_gart.cpp:1157 |
High |
V547 |
Expression 'reservedBase < 0' is always false. Unsigned type value is never < 0. |
General Analysis |
ATAModule.cpp:27 |
High |
V773 |
The function was exited without releasing the 'channel' pointer. A memory leak is possible. |
General Analysis |
ATARequest.cpp:124 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer 'fCCB->sense'. |
General Analysis |
ps2_elantech.cpp:186 |
High |
V547 |
Expression '(packet[0] & 0x10) == 1' is always false. |
General Analysis |
busses.cpp:136 |
High |
V547 |
Expression 'res < ((int) 0)' is always false. |
General Analysis |
devices.cpp:181 |
High |
V547 |
Expression is always false. |
General Analysis |
Device.cpp:258 |
High |
V522 |
Dereferencing of the null pointer 'currentInterface' might take place. |
General Analysis |
Device.cpp:555 |
High |
V773 |
Visibility scope of the 'pipe' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Pipe.cpp:337 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTransferStatus, fActualLength. |
General Analysis |
Transfer.cpp:16 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fData. |
General Analysis |
VirtioDevice.cpp:285 |
High |
V645 |
The 'strncat' function call could lead to the 'features_string' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
VirtioDevice.cpp:284 |
High |
V645 |
The 'strncat' function call could lead to the 'features_string' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
VirtioDevice.cpp:283 |
High |
V645 |
The 'strncat' function call could lead to the 'features_string' buffer overflow. The bounds should not contain the size of the buffer, but a number of characters it can hold. |
General Analysis |
VirtioModule.cpp:27 |
High |
V773 |
The function was exited without releasing the 'device' pointer. A memory leak is possible. |
General Analysis |
ahci_controller.cpp:19 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fRegs, fRegsArea. |
General Analysis |
ahci_port.cpp:50 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSpinlock, fMaxTrimRangeBlocks, fFIS, fCommandList, fCommandTable, fPRDTable. |
General Analysis |
ahci_port.cpp:1075 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer 'fCommandTable->cfis'. |
General Analysis |
xhci.cpp:1657 |
High |
V547 |
Expression 'endpoint > 1' is always true. |
General Analysis |
xhci.cpp:1572 |
High |
V774 |
The 'device' pointer was used after the memory was released. |
General Analysis |
virtio_pci.cpp:511 |
High |
V595 |
The 'sPCIx86Module' pointer was utilized before it was verified against nullptr. Check lines: 511, 515. |
General Analysis |
gcc3+.cpp:930 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fUnqualifiedNode. |
General Analysis |
ac97.c:486 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
ac97.c:759 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
ac97.c:759 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
ac97.c:759 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
ac97.c:441 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
ac97.c:441 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
ac97.c:441 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
ac97.c:316 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
auich.c:463 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
auich.c:822 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
auich.c:467 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
auich.c:467 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
auich.c:641 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
auich.c:734 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
multi.c:388 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
multi.c:451 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
multi.c:441 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
multi.c:401 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
auvia.c:472 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
auvia.c:482 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
auvia.c:537 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
auvia.c:556 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
auvia.c:609 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
multi.c:393 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
multi.c:406 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
multi.c:446 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
multi.c:456 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
Settings.cpp:90 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'sprintf' function. The memsize type argument is expected. |
General Analysis |
Settings.cpp:90 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'sprintf' function. The memsize type argument is expected. |
General Analysis |
Settings.cpp:90 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'sprintf' function. The memsize type argument is expected. |
General Analysis |
echo.cpp:611 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
echo.cpp:394 |
High |
V547 |
Expression 'stream->pipe >= 0' is always true. Unsigned type value is always >= 0. |
General Analysis |
echo.cpp:170 |
High |
V547 |
Expression 'stream->pipe >= 0' is always true. Unsigned type value is always >= 0. |
General Analysis |
echo.cpp:828 |
High |
V614 |
Potentially uninitialized pointer 'name' used. Consider checking the second actual argument of the 'AssignResources' function. |
General Analysis |
C3g.cpp:94 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_fPhantomPower. |
General Analysis |
CChannelMask.cpp:170 |
High |
V629 |
Consider inspecting the '1 << wStartPipeIndex' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
CChannelMask.cpp:140 |
High |
V629 |
Consider inspecting the '1 << wPipeIndex' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
CChannelMask.cpp:470 |
High |
V629 |
Consider inspecting the '1 << wPipeIndex' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
CChannelMask.cpp:483 |
High |
V629 |
Consider inspecting the '1 << wPipeIndex' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
CChannelMask.cpp:501 |
High |
V629 |
Consider inspecting the '1 << wPipeIndex' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
CDspCommObject.cpp:158 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CDspCommObject.cpp:1856 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CDspCommObject.cpp:162 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CEchoGals_mixer.cpp:1607 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CEchoGals_mixer.cpp:1555 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CEchoGals_mixer.cpp:1270 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CEchoGals_mixer.cpp:1245 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CEchoGals_mixer.cpp:1257 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-25' is negative. |
General Analysis |
CEchoGals_mixer.cpp:533 |
High |
V562 |
It's odd to compare a bool type value with a value of 18: 0x12 == IsProfessionalSpdif(). |
General Analysis |
CEchoGals_mixer.cpp:1650 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CEchoGals_transport.cpp:244 |
High |
V570 |
The 'wPipeIndex' variable is assigned to itself. |
General Analysis |
CLineLevel.cpp:305 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CLineLevel.cpp:205 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-25' is negative. |
General Analysis |
CLineLevel.cpp:327 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CLineLevel.cpp:316 |
High |
V547 |
Expression '0x00 == Status' is always true. |
General Analysis |
CLineLevel.cpp:185 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-25' is negative. |
General Analysis |
CLineLevel.cpp:304 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CLineLevel.cpp:184 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-25' is negative. |
General Analysis |
CMidiInQ.cpp:50 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_dwFill, m_dwBufferSizeMask, m_dwNumClients. |
General Analysis |
CMonitorCtrl.cpp:279 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CMonitorCtrl.cpp:295 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CMonitorCtrl.cpp:300 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CMonitorCtrl.cpp:309 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CMonitorCtrl.cpp:285 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CMonitorCtrl.cpp:278 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CMonitorCtrl.cpp:294 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CMonitorCtrl.cpp:249 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CMonitorCtrl.cpp:143 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CMonitorCtrl.cpp:138 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CMonitorCtrl.cpp:250 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CMonitorCtrl.cpp:310 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:332 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:324 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:322 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:317 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:133 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:278 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:334 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:384 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:277 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:141 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:316 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:376 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
CPipeOutCtrl.cpp:383 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-128' is negative. |
General Analysis |
emuxki.c:2168 |
High |
V502 |
Perhaps the '?:' operator works in a different way than it was expected. The '?:' operator has a lower priority than the '+' operator. |
General Analysis |
emuxki.c:2948 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
emuxki.c:2275 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
emuxki.c:272 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
emuxki.c:2194 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
emuxki.c:2150 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
emuxki.c:1776 |
High |
V547 |
Expression 'index < 0' is always false. Unsigned type value is never < 0. |
General Analysis |
emuxki.c:1313 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
emuxki.c:289 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
emuxki.c:1328 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
multi.c:518 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
multi.c:531 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
multi.c:816 |
High |
V1031 |
The 'memcpy' function is not declared. Passing data to or from this function can be affected. |
General Analysis |
multi.c:571 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
multi.c:581 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'debug_printf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:70 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'sprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1074 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1513 |
High |
V576 |
Incorrect format. Consider checking the ninth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1513 |
High |
V576 |
Incorrect format. Consider checking the eighth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1513 |
High |
V576 |
Incorrect format. Consider checking the seventh actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1513 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1074 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1513 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:612 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:612 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:735 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:735 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:740 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:740 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:740 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:750 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:750 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:821 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:848 |
High |
V576 |
Incorrect format. Consider checking the eighth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:910 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:934 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:938 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:969 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:996 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1000 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1513 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1029 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1029 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1033 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1040 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1048 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:598 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:333 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1078 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:250 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1374 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1374 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1385 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1368 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1349 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1204 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:250 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1155 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1180 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1133 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1385 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1513 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1513 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1085 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1082 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:228 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'sprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:230 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'sprintf' function. The memsize type argument is expected. |
General Analysis |
hda_codec.cpp:1133 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
hda_controller.cpp:1224 |
High |
V595 |
The 'gPCIx86Module' pointer was utilized before it was verified against nullptr. Check lines: 1224, 1231. |
General Analysis |
h2upper.cpp:75 |
High |
V557 |
Array overrun is possible. The 'BT_SCO' index is pointing beyond array bound. |
General Analysis |
usb_modeswitch.cpp:361 |
High |
V583 |
The '?:' operator, regardless of its conditional expression, always returns one and the same value: 500000. |
General Analysis |
nvme_ctrlr.c:200 |
High |
V519 |
The variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 199, 200. |
General Analysis |
scsi_cd.cpp:1104 |
High |
V568 |
It's odd that 'sizeof()' operator evaluates the size of a pointer to a class, but not the size of the 'deviceInquiry' class object. |
General Analysis |
scsi_disk.cpp:544 |
High |
V568 |
It's odd that 'sizeof()' operator evaluates the size of a pointer to a class, but not the size of the 'deviceInquiry' class object. |
General Analysis |
nbd.c:815 |
High |
V547 |
Expression 'err < ((int) 0)' is always false. |
General Analysis |
driver.cpp:647 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:637 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:574 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:342 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:574 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:317 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:305 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:293 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:431 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:331 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:342 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:457 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:499 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:314 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
power.cpp:122 |
High |
V547 |
Expression 'depth > 1' is always false. |
General Analysis |
power.cpp:124 |
High |
V547 |
Expression 'depth > 2' is always false. |
General Analysis |
agp.c:136 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
agp.c:110 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
agp.c:110 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
agp.c:175 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:156 |
High |
V576 |
Incorrect format. Consider checking the seventh actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:156 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:156 |
High |
V576 |
Incorrect format. Consider checking the eighth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:156 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:107 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:156 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:968 |
High |
V590 |
Consider inspecting this expression. The expression is excessive or contains a misprint. |
General Analysis |
bios.c:1011 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:952 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:952 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:952 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:810 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:810 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:744 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:744 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:179 |
High |
V576 |
Incorrect format. Consider checking the seventh actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:179 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:179 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:969 |
High |
V590 |
Consider inspecting this expression. The expression is excessive or contains a misprint. |
General Analysis |
bios.c:179 |
High |
V576 |
Incorrect format. Consider checking the eighth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
bios.c:179 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
CP_setup.c:711 |
High |
V547 |
Expression 'di->num_crtc != 2' is always false. |
General Analysis |
CP_setup.c:142 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
CP_setup.c:142 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
CP_setup.c:142 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
CP_setup.c:142 |
High |
V576 |
Incorrect format. Consider checking the seventh actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
CP_setup.c:348 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
CP_setup.c:412 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
CP_setup.c:556 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
detect.c:723 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.c:83 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.c:97 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.c:220 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.c:220 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.c:242 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.c:507 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.c:90 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:319 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:318 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:320 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:323 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:322 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:324 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:120 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:321 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:108 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:120 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:63 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:63 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:57 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
init.c:108 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mem_controller.c:153 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mem_controller.c:153 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mem_controller.c:151 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mem_controller.c:149 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mem_controller.c:151 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mem_controller.c:149 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
PCI_GART.c:183 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
vip.c:252 |
High |
V529 |
Odd semicolon ';' after 'while' operator. |
General Analysis |
vip.c:426 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
vip.c:250 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
vip.c:233 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
vip.c:108 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
vip.c:108 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
vip.c:233 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
device.cpp:216 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
driver.cpp:678 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:639 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:710 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:712 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:732 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:737 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:537 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:566 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:548 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:535 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:727 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:343 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:270 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:202 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:123 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:739 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:720 |
High |
V547 |
Expression 'biosStatus == ((int) 0)' is always true. |
General Analysis |
radeon_hd.cpp:719 |
High |
V547 |
Expression 'biosStatus == ((int) 0)' is always true. |
General Analysis |
radeon_hd.cpp:452 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
radeon_hd.cpp:749 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
device.cpp:62 |
High |
V547 |
Expression 'status == ((int) 0)' is always true. |
General Analysis |
HIDParser.cpp:295 |
High |
V630 |
The 'realloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
TabletProtocolHandler.cpp:293 |
High |
V564 |
The '&' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '&&' operator. |
General Analysis |
wacom.c:590 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
wacom.c:583 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
wacom.c:429 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
wacom.c:326 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
wacom.c:251 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
wacom.c:238 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
wacom.c:197 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
wacom.c:222 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
wacom.c:188 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
if_age.c:3305 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_age.c:3297 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1949 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1943 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1919 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1917 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1914 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1912 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1945 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1947 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1951 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1953 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1956 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1958 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1904 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1910 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1906 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bfe.c:1908 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
if_bge.c:2419 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer 'sc->bge_ldata.bge_status_block'. |
General Analysis |
if_bge.c:3686 |
High |
V547 |
Expression 'rid != 0' is always false. |
General Analysis |
if_dc.c:2317 |
High |
V512 |
A call of the 'memmove' function will lead to underflow of the buffer 'eaddr'. |
General Analysis |
if_dc.c:2306 |
High |
V512 |
A call of the 'memmove' function will lead to underflow of the buffer '& eaddr'. |
General Analysis |
if_dc.c:1112 |
High |
V512 |
A call of the 'memmove' function will lead to underflow of the buffer 'eaddr'. |
General Analysis |
oce_if.c:802 |
High |
V781 |
The value of the 'vector' variable is checked after it was used. Perhaps there is a mistake in program logic. Check lines: 802, 805. |
General Analysis |
oce_queue.c:782 |
High |
V595 |
The 'mq' pointer was utilized before it was verified against nullptr. Check lines: 782, 786. |
General Analysis |
if_fxp.c:3129 |
High |
V512 |
A call of the 'memset' function will lead to overflow of the buffer 'cbp'. |
General Analysis |
if_fxp.c:1630 |
High |
V557 |
Array underrun is possible. The '-1' index is pointing beyond array bound. |
General Analysis |
e1000_ich8lan.c:1094 |
High |
V629 |
Consider inspecting the '1 << (scale * 5)' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
e1000_ich8lan.c:485 |
High |
V547 |
Expression 'phy->id == e1000_phy_unknown' is always true. |
General Analysis |
e1000_ich8lan.c:5571 |
High |
V654 |
The condition 'retry' of loop is always true. |
General Analysis |
e1000_ich8lan.c:3712 |
High |
V547 |
Expression 'ret_val == 0' is always false. |
General Analysis |
if_rl.c:1721 |
High |
V512 |
A call of the 'memmove' function will lead to underflow of the buffer 'eaddr'. |
General Analysis |
if_re.c:1801 |
High |
V595 |
The 'ifp' pointer was utilized before it was verified against nullptr. Check lines: 1801, 1817. |
General Analysis |
DataRing.h:58 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSpinlock. |
General Analysis |
if_sk.c:3171 |
High |
V595 |
The 'ifp0' pointer was utilized before it was verified against nullptr. Check lines: 3171, 3187. |
General Analysis |
if_sk.c:3179 |
High |
V595 |
The 'ifp1' pointer was utilized before it was verified against nullptr. Check lines: 3179, 3190. |
General Analysis |
ASIXDevice.cpp:502 |
High |
V547 |
Expression '(epd->endpoint_address & 0x00) == 0x00' is always true. |
General Analysis |
DavicomDevice.cpp:587 |
High |
V547 |
Expression '(epd->endpoint_address & 0x00) == 0x00' is always true. |
General Analysis |
virtio_net.cpp:774 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors and destructors. |
General Analysis |
virtio_net.cpp:297 |
High |
V579 |
The memset function receives the pointer and its size as arguments. It is possibly a mistake. Inspect the third argument. |
General Analysis |
virtio_net.cpp:296 |
High |
V579 |
The memset function receives the pointer and its size as arguments. It is possibly a mistake. Inspect the third argument. |
General Analysis |
device.c:72 |
High |
V627 |
Consider inspecting the expression. The argument of sizeof() is the macro which expands to a number. |
General Analysis |
if_an.c:756 |
High |
V575 |
The 'memmove' function processes '0' elements. Inspect the third argument. |
General Analysis |
if_an.c:887 |
High |
V512 |
A call of the 'memmove' function will lead to underflow of the buffer 'bpf_buf'. |
General Analysis |
if_an.c:2071 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer 'tmpstr'. |
General Analysis |
if_an.c:2246 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer 'tmpstr'. |
General Analysis |
if_an.c:2467 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer '& sc->areq'. |
General Analysis |
if_an.c:2992 |
High |
V512 |
A call of the 'memmove' function will lead to underflow of the buffer '& sc->areq'. |
General Analysis |
if_an.c:2419 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer '& sc->areq'. |
General Analysis |
ar9300_attach.c:1604 |
High |
V547 |
Expression is always false. |
General Analysis |
ar9300_eeprom.c:179 |
High |
V547 |
Expression 'nptr < 0' is always true. |
General Analysis |
ar9300_eeprom.c:3063 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The right operand ('i' = [0..35]) is greater than or equal to the length in bits of the promoted left operand. |
General Analysis |
ar9300_mci.c:222 |
High |
V616 |
The '(MCI_GPM_COEX_VERSION_QUERY)' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
ar9300_misc.c:3897 |
High |
V512 |
A call of the 'memcpy' function will lead to overflow of the buffer 'ctl_index + 12'. |
General Analysis |
ar9300_misc.c:3906 |
High |
V512 |
A call of the 'memcpy' function will lead to overflow of the buffer 'ctl_index + 9'. |
General Analysis |
ar9300_misc.c:2902 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
ar9300_paprd.c:366 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '(- 15)' is negative. |
General Analysis |
ar9300_paprd.c:1528 |
High |
V634 |
The priority of the '*' operation is higher than that of the '<<' operation. It's possible that parentheses should be used in the expression. |
General Analysis |
ar9300_paprd.c:1554 |
High |
V634 |
The priority of the '*' operation is higher than that of the '<<' operation. It's possible that parentheses should be used in the expression. |
General Analysis |
ar9300_paprd.c:371 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '(- 10)' is negative. |
General Analysis |
ar9300_paprd.c:358 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '(- 6)' is negative. |
General Analysis |
ar9300_paprd.c:355 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '(- 3)' is negative. |
General Analysis |
ar9300_paprd.c:305 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '(- 15)' is negative. |
General Analysis |
ar9300_paprd.c:303 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '(- 3)' is negative. |
General Analysis |
ar9300_paprd.c:363 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '(- 10)' is negative. |
General Analysis |
ar9300_reset.c:2743 |
High |
V595 |
The 'chan' pointer was utilized before it was verified against nullptr. Check lines: 2743, 2745. |
General Analysis |
ar9300_reset.c:1134 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand is negative ('(freq_offset - 10)' = [-10..6075]). |
General Analysis |
ar9300_xmit.c:450 |
High |
V547 |
Expression 'value < 0' is always false. Unsigned type value is never < 0. |
General Analysis |
ar5210_reset.c:506 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-127' is negative. |
General Analysis |
ar5210_reset.c:506 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-1' is negative. |
General Analysis |
ar5210_reset.c:504 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand '-1' is negative. |
General Analysis |
ar5212_attach.c:490 |
High |
V523 |
The 'then' statement is equivalent to the subsequent code fragment. |
General Analysis |
ar5212_misc.c:964 |
High |
V547 |
Expression 'capability == 2' is always false. |
General Analysis |
ar5212_reset.c:1061 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand is negative ('(qCoff)' = [-16..15]). |
General Analysis |
ar5212_reset.c:1971 |
High |
V629 |
Consider inspecting the '1 << (24 - coef_exp - 1)' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
ar5212_reset.c:1059 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand is negative ('(iCoff)' = [-32..31]). |
General Analysis |
ar5416_attach.c:367 |
High |
V557 |
Array overrun is possible. The '1' index is pointing beyond array bound. |
General Analysis |
ar5416_attach.c:368 |
High |
V557 |
Array overrun is possible. The '1' index is pointing beyond array bound. |
General Analysis |
ar5416_btcoex.c:133 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
ar5416_cal.c:463 |
High |
V763 |
Parameter 'rxchainmask' is always rewritten in function body before being used. |
General Analysis |
ar5416_cal_iq.c:126 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The left operand is negative ('(qCoff)' = [-16..15]). |
General Analysis |
sample.c:1157 |
High |
V547 |
Expression 'sn->static_rix != - 1' is always false. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 65' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 58.5' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 52' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 39' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 6.5' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 65' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 52' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 39' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 26' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 13' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 6.5' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(65) == 58.5' expression. |
General Analysis |
tx_schedules.h:106 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:106 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 78' expression. |
General Analysis |
tx_schedules.h:106 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 117' expression. |
General Analysis |
tx_schedules.h:106 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 156' expression. |
General Analysis |
tx_schedules.h:106 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 195' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 19.5' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 13' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 6.5' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 65' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 52' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 39' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 26' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 13' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 6.5' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 58.5' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 19.5' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 6.5' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 6.5' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 58.5' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 26' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 39' expression. |
General Analysis |
tx_schedules.h:89 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 19.5' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 19.5' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 52' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 58.5' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 52' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 26' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 13' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 13' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 26' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 52' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 65' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 13' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 26' expression. |
General Analysis |
tx_schedules.h:107 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 65' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 58.5' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 52' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 26' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 13' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 58.5' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 19.5' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 6.5' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 6.5' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 65' expression. |
General Analysis |
tx_schedules.h:88 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 19.5' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 6.5' expression. |
General Analysis |
tx_schedules.h:86 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 52' expression. |
General Analysis |
tx_schedules.h:84 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 13' expression. |
General Analysis |
tx_schedules.h:84 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 26' expression. |
General Analysis |
tx_schedules.h:84 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 39' expression. |
General Analysis |
tx_schedules.h:84 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 52' expression. |
General Analysis |
tx_schedules.h:84 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 65' expression. |
General Analysis |
tx_schedules.h:85 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 6.5' expression. |
General Analysis |
tx_schedules.h:85 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 19.5' expression. |
General Analysis |
tx_schedules.h:85 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 58.5' expression. |
General Analysis |
tx_schedules.h:85 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 13' expression. |
General Analysis |
tx_schedules.h:85 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 26' expression. |
General Analysis |
tx_schedules.h:85 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 39' expression. |
General Analysis |
tx_schedules.h:85 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 52' expression. |
General Analysis |
tx_schedules.h:85 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 65' expression. |
General Analysis |
tx_schedules.h:86 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 13' expression. |
General Analysis |
tx_schedules.h:86 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 26' expression. |
General Analysis |
tx_schedules.h:86 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:86 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 52' expression. |
General Analysis |
tx_schedules.h:86 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 65' expression. |
General Analysis |
tx_schedules.h:86 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 13' expression. |
General Analysis |
tx_schedules.h:86 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 26' expression. |
General Analysis |
tx_schedules.h:86 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 39' expression. |
General Analysis |
tx_schedules.h:87 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 39' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(65) == 19.5' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:107 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 175.5' expression. |
General Analysis |
tx_schedules.h:113 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 39' expression. |
General Analysis |
tx_schedules.h:113 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 175.5' expression. |
General Analysis |
tx_schedules.h:113 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 58.5' expression. |
General Analysis |
tx_schedules.h:113 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 19.5' expression. |
General Analysis |
tx_schedules.h:113 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(195) == 175.5' expression. |
General Analysis |
tx_schedules.h:113 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(195) == 58.5' expression. |
General Analysis |
tx_schedules.h:113 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 78' expression. |
General Analysis |
tx_schedules.h:113 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(195) == 19.5' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 175.5' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 58.5' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 19.5' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 175.5' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 175.5' expression. |
General Analysis |
tx_schedules.h:113 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 117' expression. |
General Analysis |
tx_schedules.h:113 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 156' expression. |
General Analysis |
tx_schedules.h:113 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 195' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(2) == 5.5' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 54' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 48' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 36' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 24' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 18' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 12' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 9' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 6' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 11' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 2' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 1' expression. |
General Analysis |
tx_schedules.h:127 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:127 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(2) == 5.5' expression. |
General Analysis |
tx_schedules.h:126 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 58.5' expression. |
General Analysis |
tx_schedules.h:128 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 19.5' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(175.5) == 156' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 58.5' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 6.5' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 156' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 117' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 78' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 195' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 195' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 156' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 117' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 78' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 39' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 6.5' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 19.5' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 19.5' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 58.5' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(175.5) == 117' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(175.5) == 78' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(175.5) == 39' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 195' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 156' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 117' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 78' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 175.5' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 58.5' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 19.5' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 175.5' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 58.5' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 19.5' expression. |
General Analysis |
tx_schedules.h:111 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 175.5' expression. |
General Analysis |
tx_schedules.h:112 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(175.5) == 195' expression. |
General Analysis |
tx_schedules.h:107 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(11) == 5.5' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 2' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 195' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 19.5' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 58.5' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 175.5' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 39' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 78' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 156' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 117' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 195' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 175.5' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 78' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 156' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 117' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 78' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:107 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:107 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 78' expression. |
General Analysis |
tx_schedules.h:107 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 117' expression. |
General Analysis |
tx_schedules.h:107 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 156' expression. |
General Analysis |
tx_schedules.h:107 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 195' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 39' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(65) == 6.5' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 58.5' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 78' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 117' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 156' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 195' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 175.5' expression. |
General Analysis |
tx_schedules.h:108 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 175.5' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 117' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 1' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 156' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 19.5' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 2' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 1' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 5.5' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(2) == 5.5' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 54' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 11' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 48' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 24' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 18' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 12' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 9' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 6' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 11' expression. |
General Analysis |
tx_schedules.h:129 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 36' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 6' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 9' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 12' expression. |
General Analysis |
tx_schedules.h:91 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 65' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 58.5' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 175.5' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 19.5' expression. |
General Analysis |
tx_schedules.h:110 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 58.5' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 1' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 5.5' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 5.5' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(2) == 5.5' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 54' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 48' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 36' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 24' expression. |
General Analysis |
tx_schedules.h:130 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 18' expression. |
General Analysis |
tx_schedules.h:109 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 195' expression. |
General Analysis |
tx_schedules.h:90 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 19.5' expression. |
General Analysis |
tx_schedules.h:134 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 5.5' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 6' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 19.5' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 175.5' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 58.5' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 19.5' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(175.5) == 195' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(175.5) == 156' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(175.5) == 117' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(175.5) == 78' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(175.5) == 39' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 195' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 156' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 58.5' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 117' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 175.5' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 58.5' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 19.5' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 175.5' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 58.5' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 19.5' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 175.5' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 58.5' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 19.5' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 195' expression. |
General Analysis |
tx_schedules.h:196 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 78' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 156' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 175.5' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:214 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 4.5' expression. |
General Analysis |
tx_schedules.h:213 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 4.5' expression. |
General Analysis |
tx_schedules.h:213 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 4.5' expression. |
General Analysis |
tx_schedules.h:212 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 4.5' expression. |
General Analysis |
tx_schedules.h:212 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 27' expression. |
General Analysis |
tx_schedules.h:212 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 24' expression. |
General Analysis |
tx_schedules.h:212 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 18' expression. |
General Analysis |
tx_schedules.h:212 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 12' expression. |
General Analysis |
tx_schedules.h:212 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 9' expression. |
General Analysis |
tx_schedules.h:212 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 6' expression. |
General Analysis |
tx_schedules.h:212 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 3' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:211 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 4.5' expression. |
General Analysis |
tx_schedules.h:198 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 156' expression. |
General Analysis |
tx_schedules.h:198 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 117' expression. |
General Analysis |
tx_schedules.h:198 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 78' expression. |
General Analysis |
tx_schedules.h:198 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 39' expression. |
General Analysis |
tx_schedules.h:198 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 175.5' expression. |
General Analysis |
tx_schedules.h:198 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 58.5' expression. |
General Analysis |
tx_schedules.h:198 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(156) == 19.5' expression. |
General Analysis |
tx_schedules.h:198 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(195) == 175.5' expression. |
General Analysis |
tx_schedules.h:198 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(195) == 58.5' expression. |
General Analysis |
tx_schedules.h:198 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(195) == 19.5' expression. |
General Analysis |
tx_schedules.h:197 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 175.5' expression. |
General Analysis |
tx_schedules.h:198 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 195' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 117' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 78' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 117' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 78' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 175.5' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 195' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 156' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 117' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 78' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 39' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 156' expression. |
General Analysis |
tx_schedules.h:192 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 195' expression. |
General Analysis |
tx_schedules.h:192 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 117' expression. |
General Analysis |
tx_schedules.h:192 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 78' expression. |
General Analysis |
tx_schedules.h:192 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:192 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 175.5' expression. |
General Analysis |
tx_schedules.h:192 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:192 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:191 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 195' expression. |
General Analysis |
tx_schedules.h:191 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 156' expression. |
General Analysis |
tx_schedules.h:191 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 117' expression. |
General Analysis |
tx_schedules.h:191 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 78' expression. |
General Analysis |
tx_schedules.h:191 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:192 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 156' expression. |
General Analysis |
tx_schedules.h:193 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 195' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 19.5' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 58.5' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 195' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 156' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 117' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 78' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 39' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 175.5' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 58.5' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 19.5' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 175.5' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 58.5' expression. |
General Analysis |
tx_schedules.h:195 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(117) == 19.5' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 195' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 156' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 117' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 78' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 175.5' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 195' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 156' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 117' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 78' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 39' expression. |
General Analysis |
tx_schedules.h:194 |
High |
V674 |
The '175.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(78) == 175.5' expression. |
General Analysis |
tx_schedules.h:214 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 4.5' expression. |
General Analysis |
tx_schedules.h:214 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 4.5' expression. |
General Analysis |
tx_schedules.h:215 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 4.5' expression. |
General Analysis |
tx_schedules.h:215 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 4.5' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 4.5' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 2.25' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 1.5' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 12' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 9' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 6' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 3' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 12' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 9' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 6' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 3' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 13.5' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 13.5' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 2.25' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 1.5' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 13.5' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 4.5' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 2.25' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 1.5' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 12' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 9' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 6' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 3' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 13.5' expression. |
General Analysis |
tx_schedules.h:235 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 4.5' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 1.5' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 2.25' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 4.5' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 13.5' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 4.5' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 2.25' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 1.5' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 13.5' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 4.5' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 2.25' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 1.5' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 13.5' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 4.5' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 2.25' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 1.5' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13.5) == 12' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13.5) == 9' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13.5) == 6' expression. |
General Analysis |
tx_schedules.h:237 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13.5) == 3' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 13.5' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 4.5' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 2.25' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 1.5' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 13.5' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 4.5' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 2.25' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 1.5' expression. |
General Analysis |
tx_schedules.h:236 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 13.5' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 4.5' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 58.5' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 2.25' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 12' expression. |
General Analysis |
tx_schedules.h:231 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 6' expression. |
General Analysis |
tx_schedules.h:231 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 3' expression. |
General Analysis |
tx_schedules.h:231 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(2.25) == 12' expression. |
General Analysis |
tx_schedules.h:231 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(2.25) == 9' expression. |
General Analysis |
tx_schedules.h:231 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(2.25) == 6' expression. |
General Analysis |
tx_schedules.h:231 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(2.25) == 3' expression. |
General Analysis |
tx_schedules.h:230 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 12' expression. |
General Analysis |
tx_schedules.h:230 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 9' expression. |
General Analysis |
tx_schedules.h:230 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 6' expression. |
General Analysis |
tx_schedules.h:230 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 3' expression. |
General Analysis |
tx_schedules.h:218 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 4.5' expression. |
General Analysis |
tx_schedules.h:231 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 9' expression. |
General Analysis |
tx_schedules.h:218 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(18) == 4.5' expression. |
General Analysis |
tx_schedules.h:218 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(27) == 4.5' expression. |
General Analysis |
tx_schedules.h:217 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 4.5' expression. |
General Analysis |
tx_schedules.h:217 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 4.5' expression. |
General Analysis |
tx_schedules.h:217 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(18) == 4.5' expression. |
General Analysis |
tx_schedules.h:217 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(24) == 4.5' expression. |
General Analysis |
tx_schedules.h:216 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 4.5' expression. |
General Analysis |
tx_schedules.h:216 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 4.5' expression. |
General Analysis |
tx_schedules.h:216 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 4.5' expression. |
General Analysis |
tx_schedules.h:216 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(18) == 4.5' expression. |
General Analysis |
tx_schedules.h:215 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 4.5' expression. |
General Analysis |
tx_schedules.h:215 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 4.5' expression. |
General Analysis |
tx_schedules.h:218 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(24) == 4.5' expression. |
General Analysis |
tx_schedules.h:231 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 12' expression. |
General Analysis |
tx_schedules.h:232 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 1.5' expression. |
General Analysis |
tx_schedules.h:232 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 2.25' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 9' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 6' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 3' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 13.5' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 4.5' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 2.25' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 1.5' expression. |
General Analysis |
tx_schedules.h:233 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 12' expression. |
General Analysis |
tx_schedules.h:233 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 9' expression. |
General Analysis |
tx_schedules.h:233 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 6' expression. |
General Analysis |
tx_schedules.h:233 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 3' expression. |
General Analysis |
tx_schedules.h:233 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 13.5' expression. |
General Analysis |
tx_schedules.h:233 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 4.5' expression. |
General Analysis |
tx_schedules.h:233 |
High |
V674 |
The '2.25' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 2.25' expression. |
General Analysis |
tx_schedules.h:233 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 1.5' expression. |
General Analysis |
tx_schedules.h:233 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 12' expression. |
General Analysis |
tx_schedules.h:233 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 9' expression. |
General Analysis |
tx_schedules.h:233 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 6' expression. |
General Analysis |
tx_schedules.h:233 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(4.5) == 3' expression. |
General Analysis |
tx_schedules.h:232 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 12' expression. |
General Analysis |
tx_schedules.h:232 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 9' expression. |
General Analysis |
tx_schedules.h:232 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 6' expression. |
General Analysis |
tx_schedules.h:232 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1.5) == 3' expression. |
General Analysis |
tx_schedules.h:232 |
High |
V674 |
The '13.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 13.5' expression. |
General Analysis |
tx_schedules.h:232 |
High |
V674 |
The '4.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 4.5' expression. |
General Analysis |
tx_schedules.h:234 |
High |
V674 |
The '1.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(3) == 1.5' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 2' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 19.5' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 58.5' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 36' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 24' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 18' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 12' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 9' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 6' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 11' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 2' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 1' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 5.5' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 48' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(2) == 5.5' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 48' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 36' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 24' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 18' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 12' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 9' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 6' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 11' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 2' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 1' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(11) == 5.5' expression. |
General Analysis |
tx_schedules.h:157 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 54' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 54' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 24' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 18' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 12' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 9' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 6' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 11' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 2' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 1' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(11) == 5.5' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 5.5' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:158 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(2) == 5.5' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 54' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 36' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 24' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 18' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 12' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 9' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 6' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 11' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 2' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 1' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6) == 5.5' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(9) == 5.5' expression. |
General Analysis |
tx_schedules.h:159 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 48' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(2) == 5.5' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 54' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 48' expression. |
General Analysis |
tx_schedules.h:133 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 5.5' expression. |
General Analysis |
tx_schedules.h:133 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(18) == 5.5' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 54' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 48' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 36' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 24' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 18' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 12' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 9' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 6' expression. |
General Analysis |
tx_schedules.h:133 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(11) == 5.5' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 11' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 1' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(11) == 5.5' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 5.5' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 54' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 48' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 36' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 24' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 18' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 12' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 9' expression. |
General Analysis |
tx_schedules.h:132 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 2' expression. |
General Analysis |
tx_schedules.h:133 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:134 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(24) == 5.5' expression. |
General Analysis |
tx_schedules.h:134 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(18) == 5.5' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 36' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 24' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 18' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 12' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 9' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 6' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 11' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 2' expression. |
General Analysis |
tx_schedules.h:156 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 1' expression. |
General Analysis |
tx_schedules.h:155 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:155 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(2) == 5.5' expression. |
General Analysis |
tx_schedules.h:154 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:137 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:137 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(36) == 5.5' expression. |
General Analysis |
tx_schedules.h:137 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(48) == 5.5' expression. |
General Analysis |
tx_schedules.h:137 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(54) == 5.5' expression. |
General Analysis |
tx_schedules.h:136 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:136 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(24) == 5.5' expression. |
General Analysis |
tx_schedules.h:136 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(36) == 5.5' expression. |
General Analysis |
tx_schedules.h:136 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(48) == 5.5' expression. |
General Analysis |
tx_schedules.h:135 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:135 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(18) == 5.5' expression. |
General Analysis |
tx_schedules.h:135 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(24) == 5.5' expression. |
General Analysis |
tx_schedules.h:135 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(36) == 5.5' expression. |
General Analysis |
tx_schedules.h:134 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 36' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 48' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 54' expression. |
General Analysis |
tx_schedules.h:160 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 58.5' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 19.5' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 6.5' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 6.5' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 58.5' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 19.5' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 6.5' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 65' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 52' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 13' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 39' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 13' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 65' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 52' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 26' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 13' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 58.5' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 19.5' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 6.5' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 26' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 26' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 39' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 52' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 19.5' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 6.5' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 65' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 52' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 39' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 26' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 13' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(65) == 58.5' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(65) == 19.5' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(65) == 6.5' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 58.5' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 19.5' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 6.5' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 58.5' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 19.5' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 6.5' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 58.5' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 19.5' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(52) == 6.5' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 65' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 52' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 39' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 26' expression. |
General Analysis |
tx_schedules.h:175 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(58.5) == 13' expression. |
General Analysis |
tx_schedules.h:174 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 65' expression. |
General Analysis |
tx_schedules.h:173 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(39) == 6.5' expression. |
General Analysis |
tx_schedules.h:176 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 6.5' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 65' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 39' expression. |
General Analysis |
tx_schedules.h:169 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 52' expression. |
General Analysis |
tx_schedules.h:169 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 39' expression. |
General Analysis |
tx_schedules.h:169 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 26' expression. |
General Analysis |
tx_schedules.h:169 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 13' expression. |
General Analysis |
tx_schedules.h:165 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:165 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(36) == 5.5' expression. |
General Analysis |
tx_schedules.h:165 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(48) == 5.5' expression. |
General Analysis |
tx_schedules.h:165 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(54) == 5.5' expression. |
General Analysis |
tx_schedules.h:164 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:164 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(24) == 5.5' expression. |
General Analysis |
tx_schedules.h:164 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(36) == 5.5' expression. |
General Analysis |
tx_schedules.h:169 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 65' expression. |
General Analysis |
tx_schedules.h:164 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(48) == 5.5' expression. |
General Analysis |
tx_schedules.h:163 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(18) == 5.5' expression. |
General Analysis |
tx_schedules.h:163 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(24) == 5.5' expression. |
General Analysis |
tx_schedules.h:163 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(36) == 5.5' expression. |
General Analysis |
tx_schedules.h:162 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:162 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 5.5' expression. |
General Analysis |
tx_schedules.h:162 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(18) == 5.5' expression. |
General Analysis |
tx_schedules.h:162 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(24) == 5.5' expression. |
General Analysis |
tx_schedules.h:161 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:161 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(11) == 5.5' expression. |
General Analysis |
tx_schedules.h:161 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(12) == 5.5' expression. |
General Analysis |
tx_schedules.h:161 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(18) == 5.5' expression. |
General Analysis |
tx_schedules.h:163 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(1) == 5.5' expression. |
General Analysis |
tx_schedules.h:170 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 6.5' expression. |
General Analysis |
tx_schedules.h:170 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 19.5' expression. |
General Analysis |
tx_schedules.h:170 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(13) == 58.5' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 26' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 13' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 65' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 52' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 26' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 13' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '58.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 58.5' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 19.5' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(26) == 6.5' expression. |
General Analysis |
tx_schedules.h:171 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 65' expression. |
General Analysis |
tx_schedules.h:171 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 52' expression. |
General Analysis |
tx_schedules.h:171 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 39' expression. |
General Analysis |
tx_schedules.h:171 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 26' expression. |
General Analysis |
tx_schedules.h:171 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 13' expression. |
General Analysis |
tx_schedules.h:171 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 65' expression. |
General Analysis |
tx_schedules.h:171 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 52' expression. |
General Analysis |
tx_schedules.h:171 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 39' expression. |
General Analysis |
tx_schedules.h:171 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 26' expression. |
General Analysis |
tx_schedules.h:171 |
High |
V674 |
The '19.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(19.5) == 13' expression. |
General Analysis |
tx_schedules.h:170 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 65' expression. |
General Analysis |
tx_schedules.h:170 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 52' expression. |
General Analysis |
tx_schedules.h:170 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 39' expression. |
General Analysis |
tx_schedules.h:170 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 26' expression. |
General Analysis |
tx_schedules.h:170 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 13' expression. |
General Analysis |
tx_schedules.h:172 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 52' expression. |
General Analysis |
tx_schedules.h:131 |
High |
V674 |
The '5.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(5.5) == 11' expression. |
General Analysis |
tx_schedules.h:86 |
High |
V674 |
The '6.5' literal of the 'double' type is compared to a value of the 'int' type. Consider inspecting the '(6.5) == 65' expression. |
General Analysis |
if_ath.c:4803 |
High |
V781 |
The value of the 'bf->bf_state.bfs_tx_queue' variable is checked after it was used. Perhaps there is a mistake in program logic. Check lines: 4803, 4811. |
General Analysis |
if_ath.c:6875 |
High |
V595 |
The 'ni' pointer was utilized before it was verified against nullptr. Check lines: 6875, 6880. |
General Analysis |
if_ath_btcoex.c:369 |
High |
V547 |
Expression 'ret != 0' is always true. |
General Analysis |
if_ath_btcoex_mci.c:290 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
if_ath_btcoex_mci.c:622 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
if_ath_btcoex_mci.c:238 |
High |
V547 |
Expression 'nevent == ATH_COEX_EVENT_BT_NOOP' is always true. |
General Analysis |
if_ath_tx.c:3951 |
High |
V547 |
Expression 't == 0' is always true. |
General Analysis |
if_ath_tx.c:4963 |
High |
V547 |
Expression 'ts.ts_status == 0' is always true. |
General Analysis |
if_ath_tx.c:3967 |
High |
V547 |
Expression 't == 0' is always true. |
General Analysis |
if_bwi.c:1372 |
High |
V595 |
The 'ni' pointer was utilized before it was verified against nullptr. Check lines: 1372, 1380. |
General Analysis |
if_iwm.c:3788 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
if_iwm.c:3945 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'device_printf' function. The pointer to string of char type symbols is expected. |
General Analysis |
if_iwm_scan.c:395 |
High |
V547 |
Expression 'remain < sizeof (* wh) + 2' is always false. |
General Analysis |
if_ipw.c:1871 |
High |
V590 |
Consider inspecting this expression. The expression is excessive or contains a misprint. |
General Analysis |
if_iwn.c:6679 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer 'sc->rxon'. |
General Analysis |
if_iwn.c:5681 |
High |
V547 |
Expression '(rssi) > (phy->rssi[0])' is always false. Unsigned type value is never < 0. |
General Analysis |
if_iwn.c:6854 |
High |
V763 |
Parameter 'c' is always rewritten in function body before being used. |
General Analysis |
if_malo.c:341 |
High |
V547 |
Expression 'opmode == IEEE80211_M_STA' is always true. |
General Analysis |
if_malohal.c:413 |
High |
V522 |
Dereferencing of the null pointer 'data' might take place. The null pointer is passed into 'malo_hal_send_main' function. Inspect the second argument. Check lines: 413, 472. |
General Analysis |
if_malohal.c:350 |
High |
V522 |
Dereferencing of the null pointer 'data' might take place. The null pointer is passed into 'malo_hal_send_helper' function. Inspect the third argument. Check lines: 350, 394. |
General Analysis |
if_malohal.c:523 |
High |
V547 |
Expression 'opmode != 0x5A' is always false. |
General Analysis |
if_mwl.c:2444 |
High |
V610 |
Unspecified behavior. Check the shift operator '>>'. The left operand is negative ('....' = [-119..119]). |
General Analysis |
if_mwl.c:2443 |
High |
V610 |
Unspecified behavior. Check the shift operator '>>'. The left operand is negative ('....' = [-119..119]). |
General Analysis |
if_mwl.c:2442 |
High |
V610 |
Unspecified behavior. Check the shift operator '>>'. The left operand is negative ('....' = [-119..119]). |
General Analysis |
rt2860.c:1097 |
High |
V781 |
The value of the 'wcid' variable is checked after it was used. Perhaps there is a mistake in program logic. Check lines: 1097, 1100. |
General Analysis |
if_rtwn.c:760 |
High |
V616 |
The 'tid' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
if_rtwn_rx.c:307 |
High |
V569 |
Truncation of constant value -95. The value range of unsigned char type: [0, 255]. |
General Analysis |
rtwn_pci_rx.c:199 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer 'pc->pc_rx_buf'. |
General Analysis |
SerialDevice.cpp:17 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fActualLengthRead, fStatusRead, fActualLengthWrite, fStatusWrite, fActualLengthInterrupt, fStatusInterrupt. |
General Analysis |
SerialDevice.cpp:573 |
High |
V547 |
Expression 'status < ((int) 0)' is always false. |
General Analysis |
acpi_battery.cpp:363 |
High |
V547 |
Expression 'max_len < ((int) 0)' is always false. Unsigned type value is never < 0. |
General Analysis |
BlockAllocator.cpp:702 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BlockAllocator.cpp:505 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNumGroups, fBlocksPerGroup, fNumBlocks. |
General Analysis |
BlockAllocator.cpp:223 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNumBits. |
General Analysis |
BlockAllocator.cpp:702 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1900 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2038 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1889 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1889 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1856 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1900 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1856 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1849 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2055 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1849 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1431 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1299 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2135 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1856 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1222 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2322 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:353 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:711 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:711 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:782 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:782 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:790 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:790 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:801 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:823 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:829 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:829 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:829 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:873 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1146 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1146 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1171 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1171 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1299 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:1222 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2335 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2335 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2482 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2482 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2482 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2495 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2495 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2495 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2530 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2530 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2537 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2537 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2537 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2537 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2544 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2544 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2544 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2544 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:3009 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2482 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2459 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2459 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2459 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:353 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2341 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2341 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2350 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2350 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2370 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2370 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2390 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2322 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2390 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2403 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2403 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2435 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2435 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2444 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2444 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2444 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2459 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2403 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:353 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:801 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:2011 |
High |
V512 |
A call of the 'memmove' function will lead to overflow of the buffer 'duplicate'. |
General Analysis |
BPlusTree.cpp:606 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHeader. |
General Analysis |
BPlusTree.cpp:276 |
High |
V512 |
A call of the 'memcpy' function will lead to the 'fNode' buffer becoming out of range. |
General Analysis |
BPlusTree.cpp:1603 |
High |
V773 |
The function was exited without releasing the 'newKey' pointer. A memory leak is possible. |
General Analysis |
BPlusTree.cpp:319 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:319 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
BPlusTree.cpp:319 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
CheckVisitor.cpp:32 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: control. |
General Analysis |
CheckVisitor.cpp:468 |
High |
V547 |
Expression is always false. |
General Analysis |
CheckVisitor.cpp:254 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
CheckVisitor.cpp:254 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
CheckVisitor.cpp:338 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
CheckVisitor.cpp:363 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
CheckVisitor.cpp:107 |
High |
V547 |
Expression 'Control().stats.freed < 0' is always false. Unsigned type value is never < 0. |
General Analysis |
CheckVisitor.cpp:650 |
High |
V576 |
Incorrect format. Consider checking the seventh actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
CheckVisitor.cpp:675 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
CheckVisitor.cpp:650 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:90 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:157 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:156 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:155 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:106 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:104 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:96 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:251 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:71 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:56 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:55 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:70 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Debug.cpp:258 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_kprintf' function. The memsize type argument is expected. |
General Analysis |
Inode.cpp:162 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fRun. |
General Analysis |
Inode.cpp:1889 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Inode.cpp:1545 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Inode.cpp:1540 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Inode.cpp:1522 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Inode.cpp:1518 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Inode.cpp:439 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
Inode.cpp:2020 |
High |
V629 |
Consider inspecting the 'runLength << fVolume->BlockShift()' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Inode.cpp:270 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
Inode.cpp:435 |
High |
V547 |
Expression 'status == ((- 0x7fffffff - 1) + 14)' is always false. |
General Analysis |
Inode.cpp:2903 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
Inode.cpp:451 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
Inode.cpp:2895 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
Journal.cpp:168 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTransactionID. |
General Analysis |
Journal.cpp:399 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTimestamp, fTransactionID. |
General Analysis |
Journal.cpp:522 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
kernel_interface.cpp:2379 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
kernel_interface.cpp:190 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
kernel_interface.cpp:292 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
kernel_interface.cpp:299 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
kernel_interface.cpp:542 |
High |
V629 |
Consider inspecting the '(uint32) run.Length() << blockShift' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
kernel_interface.cpp:308 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
kernel_interface.cpp:2380 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
kernel_interface.cpp:1505 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
kernel_interface.cpp:542 |
High |
V629 |
Consider inspecting the '(uint32_t) run.Length() << blockShift' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
kernel_interface.cpp:306 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
Query.cpp:672 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
Query.cpp:616 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
Volume.cpp:363 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
Volume.cpp:363 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
DebugSupport.cpp:54 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Volume.cpp:32 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fVnodeOps, fName. |
General Analysis |
BTree.cpp:566 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLogicalRoot. |
General Analysis |
BTree.cpp:576 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLogicalRoot, fRootLevel. |
General Analysis |
BTree.cpp:556 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLogicalRoot. |
General Analysis |
ExtentAllocator.cpp:352 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fKey. |
General Analysis |
Inode.cpp:303 |
High |
V781 |
The value of the 'bytesRead' variable is checked after it was used. Perhaps there is a mistake in program logic. Check lines: 303, 305. |
General Analysis |
Inode.cpp:47 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLock. |
General Analysis |
Inode.cpp:63 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNode. |
General Analysis |
cdda.cpp:369 |
High |
V595 |
The 'lastPack' pointer was utilized before it was verified against nullptr. Check lines: 369, 384. |
General Analysis |
kernel_interface.cpp:1457 |
High |
V1028 |
Possible overflow. Consider casting operands, not the result. |
General Analysis |
kernel_interface.cpp:1394 |
High |
V641 |
The size of the allocated memory buffer is not a multiple of the element size. |
General Analysis |
kernel_interface.cpp:625 |
High |
V641 |
The size of the allocated memory buffer is not a multiple of the element size. |
General Analysis |
kernel_interface.cpp:565 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fDiscID. |
General Analysis |
DirectoryIterator.cpp:281 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
kernel_interface.cpp:99 |
High |
V1028 |
Possible overflow. Consider casting operands, not the result. |
General Analysis |
Volume.cpp:266 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fDevice, fSuperBlock, fBlockSize, fEntriesPerBlock, fBlockCache. |
General Analysis |
BlockAllocator.cpp:91 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCurrentTransaction. |
General Analysis |
BlockAllocator.cpp:536 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFirstBlock. |
General Analysis |
BlockAllocator.cpp:582 |
High |
V547 |
Expression 'id < ((int) 0)' is always true. |
General Analysis |
ext2.h:782 |
High |
V568 |
It's odd that 'sizeof()' operator evaluates the size of a pointer to a class, but not the size of the 'this' class object. |
General Analysis |
ext2.h:149 |
High |
V570 |
The 'readOnlyFeatures' variable is assigned to itself. |
General Analysis |
HTree.cpp:51 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashVersion. |
General Analysis |
HTreeEntryIterator.cpp:50 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLimit, fCount. |
General Analysis |
HTreeEntryIterator.cpp:28 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLimit, fCount. |
General Analysis |
Inode.cpp:66 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fUnlinked, fHasExtraAttributes, fNode. |
General Analysis |
Journal.cpp:128 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fOwner. |
General Analysis |
dir.c:914 |
High |
V547 |
Expression is always false. |
General Analysis |
dir.c:801 |
High |
V547 |
Expression is always false. |
General Analysis |
encodings.cpp:1028 |
High |
V557 |
Array overrun is possible. The '1' index is pointing beyond array bound. |
General Analysis |
encodings.cpp:986 |
High |
V610 |
Unspecified behavior. Check the shift operator '>>'. The left operand '(int32) 0xE5000000' is negative. |
General Analysis |
encodings.cpp:1059 |
High |
V610 |
Unspecified behavior. Check the shift operator '>>'. The left operand '(int32) 0xE5000000' is negative. |
General Analysis |
encodings.cpp:993 |
High |
V570 |
The 'unicode' variable is assigned to itself. |
General Analysis |
file.c:140 |
High |
V595 |
The 'node' pointer was utilized before it was verified against nullptr. Check lines: 140, 146. |
General Analysis |
iter.c:26 |
High |
V547 |
Expression 'sector < 0' is always false. Unsigned type value is never < 0. |
General Analysis |
mkdos.cpp:160 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:160 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:540 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:160 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:156 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:156 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:156 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:552 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:160 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:164 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
mkdos.cpp:156 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:274 |
High |
V646 |
Consider inspecting the application's logic. It's possible that 'else' keyword is missing. |
General Analysis |
mkdos.cpp:170 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
mkdos.cpp:185 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:222 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
mkdos.cpp:498 |
High |
V547 |
Expression 'numFATs > 1' is always true. |
General Analysis |
mkdos.cpp:338 |
High |
V547 |
Expression 'status < ((int) 0)' is always false. |
General Analysis |
mkdos.cpp:501 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:333 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
mkdos.cpp:434 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
iso9660_identify.cpp:130 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: max_blocks. |
General Analysis |
attribute_overlay.cpp:520 |
High |
V641 |
The size of the allocated memory buffer is not a multiple of the element size. |
General Analysis |
RootVolume.cpp:23 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fServerManager. |
General Analysis |
ServerManager.cpp:48 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fUpdate. |
General Analysis |
ServerManager.cpp:150 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fServerInfos. |
General Analysis |
ShareAttrDir.cpp:243 |
High |
V595 |
The 'iterators' pointer was utilized before it was verified against nullptr. Check lines: 243, 256. |
General Analysis |
ShareVolume.cpp:148 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fRootNode. |
General Analysis |
BlockingQueue.h:178 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
RequestMemberArray.h:106 |
High |
V630 |
Instantiation of RequestMemberArray < AttributeInfo >: The 'realloc' function is used to allocate memory for an array of objects which are classes containing constructors and destructors. |
General Analysis |
RequestMemberArray.h:106 |
High |
V630 |
Instantiation of RequestMemberArray < StringData >: The 'realloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
Requests.h:1202 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: count. |
General Analysis |
Requests.h:304 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: bigEndian. |
General Analysis |
Requests.h:476 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: openMode. |
General Analysis |
Requests.h:492 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: cookie. |
General Analysis |
Requests.h:508 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: cookie. |
General Analysis |
Requests.h:406 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: mask. |
General Analysis |
Requests.h:284 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: volumeID. |
General Analysis |
Requests.h:684 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: maxSize. |
General Analysis |
Requests.h:747 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: mode. |
General Analysis |
Requests.h:460 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: cookie. |
General Analysis |
Requests.h:817 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: cookie. |
General Analysis |
Requests.h:869 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: resolveLink. |
General Analysis |
Requests.h:328 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: flags. |
General Analysis |
Requests.h:980 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: count. |
General Analysis |
Requests.h:277 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: error. |
General Analysis |
Requests.h:291 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: error. |
General Analysis |
Requests.h:1234 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: entryInfoValid. |
General Analysis |
Requests.h:1174 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: cookie. |
General Analysis |
Requests.h:1282 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: entryInfoValid. |
General Analysis |
Requests.h:947 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: cookie. |
General Analysis |
Requests.h:424 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: nodeInfoValid. |
General Analysis |
ClientConnection.cpp:2893 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
ClientConnection.cpp:2371 |
High |
V547 |
Expression 'result == ((int) 0)' is always true. |
General Analysis |
ClientConnection.cpp:958 |
High |
V547 |
Expression 'result == ((int) 0)' is always true. |
General Analysis |
ClientConnection.cpp:596 |
High |
V595 |
The 'volume' pointer was utilized before it was verified against nullptr. Check lines: 596, 606. |
General Analysis |
ClientConnection.cpp:729 |
High |
V595 |
The 'node' pointer was utilized before it was verified against nullptr. Check lines: 729, 739. |
General Analysis |
NodeHandle.cpp:231 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fValid. |
General Analysis |
NodeMonitoringEvent.cpp:12 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: opcode. |
General Analysis |
PortConnectionListener.cpp:72 |
High |
V773 |
The 'channel' pointer was assigned values twice without releasing the memory. A memory leak is possible. |
General Analysis |
Blocker.cpp:16 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: userData. |
General Analysis |
DebugSupport.cpp:54 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
RequestFlattener.cpp:30 |
High |
V614 |
Uninitialized buffer 'buffer' used. Consider checking the first actual argument of the 'Write' function. |
General Analysis |
RequestUnflattener.cpp:35 |
High |
V522 |
Dereferencing of the null pointer 'mustFree' might take place. |
General Analysis |
Cookie.cpp:16 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fClientId, fStateSeq. |
General Analysis |
DirectoryCache.cpp:79 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fChange, fExpireTime. |
General Analysis |
FileSystem.cpp:26 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fExpireType, fSupAttrs, fFsId, fDevId. |
General Analysis |
Inode.cpp:78 |
High |
V773 |
The function was exited without releasing the 'inode' pointer. A memory leak is possible. |
General Analysis |
Inode.cpp:24 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fType, fChange. |
General Analysis |
InodeDir.cpp:353 |
High |
V547 |
Expression 'result == ((int) 0)' is always true. |
General Analysis |
MetadataCache.cpp:17 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fStatCache. |
General Analysis |
NFS4Server.cpp:241 |
High |
V547 |
Expression 'fUseCount == 0' is always true. |
General Analysis |
NFS4Server.cpp:20 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fThread, fClientId. |
General Analysis |
OpenState.cpp:19 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fClientID, fMode, fStateID, fStateSeq. |
General Analysis |
ReplyBuilder.cpp:49 |
High |
V595 |
The 'fReply' pointer was utilized before it was verified against nullptr. Check lines: 49, 52. |
General Analysis |
ReplyInterpreter.cpp:46 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fData. |
General Analysis |
RequestBuilder.cpp:810 |
High |
V595 |
The 'fRequest' pointer was utilized before it was verified against nullptr. Check lines: 810, 812. |
General Analysis |
RequestBuilder.cpp:713 |
High |
V568 |
It's odd that the argument of sizeof() operator is the 'server->ID().InAddrSize()' expression. |
General Analysis |
RequestBuilder.cpp:716 |
High |
V568 |
It's odd that the argument of sizeof() operator is the 'local.InAddrSize()' expression. |
General Analysis |
RequestInterpreter.cpp:17 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLastOperation. |
General Analysis |
RootInode.cpp:18 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fInfoCache. |
General Analysis |
RPCAuth.cpp:68 |
High |
V575 |
The null pointer is passed into 'getgroups' function. Inspect the second argument. |
General Analysis |
RPCCallbackServer.cpp:26 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fThread. |
General Analysis |
attributes.c:566 |
High |
V575 |
The null pointer is passed into 'free' function. Inspect the first argument. |
General Analysis |
attrib.c:6871 |
High |
V610 |
Unspecified behavior. Check the shift operator '>>'. The left operand is negative ('....' = [-221..255]). |
General Analysis |
compress.c:1535 |
High |
V629 |
Consider inspecting the 'freecnt << vol->cluster_size_bits' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
compress.c:1419 |
High |
V629 |
Consider inspecting the 'freed << vol->cluster_size_bits' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
compress.c:1306 |
High |
V629 |
Consider inspecting the 'freed << vol->cluster_size_bits' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
compress.c:724 |
High |
V595 |
The 'na' pointer was utilized before it was verified against nullptr. Check lines: 724, 726. |
General Analysis |
dir.c:254 |
High |
V595 |
The 'dir_ni' pointer was utilized before it was verified against nullptr. Check lines: 254, 268. |
General Analysis |
ea.c:80 |
High |
V614 |
Uninitialized variable 'dummy' used. Consider checking the fifth actual argument of the 'ntfs_attr_add' function. |
General Analysis |
inode.c:1155 |
High |
V774 |
The 'al' pointer was used after the memory was reallocated. |
General Analysis |
mft.c:1010 |
High |
V629 |
Consider inspecting the 'vol->mft_record_size << 4' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
mft.c:1180 |
High |
V595 |
The 'ctx' pointer was utilized before it was verified against nullptr. Check lines: 1180, 1186. |
General Analysis |
mft.c:829 |
High |
V595 |
The 'ctx' pointer was utilized before it was verified against nullptr. Check lines: 829, 835. |
General Analysis |
mft.c:1505 |
High |
V595 |
The 'base_ni' pointer was utilized before it was verified against nullptr. Check lines: 1505, 1518. |
General Analysis |
object_id.c:395 |
High |
V614 |
Uninitialized variable 'dummy' used. Consider checking the fifth actual argument of the 'ntfs_attr_add' function. |
General Analysis |
reparse.c:1142 |
High |
V614 |
Uninitialized variable 'dummy' used. Consider checking the fifth actual argument of the 'ntfs_attr_add' function. |
General Analysis |
reparse.c:400 |
High |
V595 |
The 'drive' pointer was utilized before it was verified against nullptr. Check lines: 400, 413. |
General Analysis |
unistr.c:1115 |
High |
V547 |
Expression 'cnt == - 1' is always true. |
General Analysis |
unistr.c:974 |
High |
V547 |
Expression 'cnt == - 1' is always true. |
General Analysis |
unistr.c:715 |
High |
V547 |
Expression 'byte >= 0xC0' is always true. |
General Analysis |
mkntfs.c:2988 |
High |
V547 |
Expression 'i < 0' is always false. |
General Analysis |
mkntfs.c:4291 |
High |
V774 |
The 'bs' pointer was used after the memory was released. |
General Analysis |
mkntfs.c:3917 |
High |
V763 |
Parameter 'm' is always rewritten in function body before being used. |
General Analysis |
mkntfs.c:4259 |
High |
V512 |
A call of the 'memcpy' function will lead to overflow of the buffer 'bs'. |
General Analysis |
mkntfs.c:4308 |
High |
V774 |
The 'bs' pointer was used after the memory was released. |
General Analysis |
mkntfs.c:1334 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
mkntfs.c:1132 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
volume_util.c:68 |
High |
V595 |
The 'vol' pointer was utilized before it was verified against nullptr. Check lines: 68, 74. |
General Analysis |
volume_util.c:67 |
High |
V595 |
The 'ns' pointer was utilized before it was verified against nullptr. Check lines: 67, 74. |
General Analysis |
volume_util.c:91 |
High |
V547 |
Expression 'readed < ((int) 0)' is always false. Unsigned type value is never < 0. |
General Analysis |
Index.cpp:18 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashLink. |
General Analysis |
Query.cpp:30 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: index. |
General Analysis |
Node.cpp:16 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNameHashTableNext, fIDHashTableNext. |
General Analysis |
NodeListener.cpp:28 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashLink. |
General Analysis |
Package.cpp:514 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFileNameHashTableNext. |
General Analysis |
PackageData.h:63 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer '& fData'. |
General Analysis |
PackageNode.cpp:17 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fModifiedTime. |
General Analysis |
StringPool.h:141 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashNext. |
General Analysis |
PackageSettings.cpp:25 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashNext. |
General Analysis |
PackageSettings.h:22 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashNext. |
General Analysis |
Volume.cpp:1395 |
High |
V773 |
The function was exited without releasing the 'unpackingNode' pointer. A memory leak is possible. |
General Analysis |
Volume.cpp:165 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMountType, fMountPoint. |
General Analysis |
Block.cpp:425 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Block.cpp:425 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
Block.cpp:425 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Block.cpp:287 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
Block.cpp:354 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Block.cpp:354 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
Block.cpp:354 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
BlockCache.cpp:53 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCacheHandle. |
General Analysis |
BlockCache.cpp:71 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
DirItem.h:162 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
DirItem.h:162 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
DirItem.h:99 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
DirItem.h:99 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
DirItem.h:99 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
DirItem.h:99 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
DirItem.h:99 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
DirItem.h:144 |
High |
V595 |
The 'name' pointer was utilized before it was verified against nullptr. Check lines: 144, 148. |
General Analysis |
hashes.cpp:143 |
High |
V547 |
Expression 'len >= 8' is always false. |
General Analysis |
hashes.cpp:96 |
High |
V547 |
Expression 'len >= 16' is always false. |
General Analysis |
hashes.cpp:160 |
High |
V571 |
Recurring check. The 'if (len >= 4)' condition was already verified in line 140. |
General Analysis |
hashes.cpp:122 |
High |
V547 |
Expression 'len >= 12' is always false. |
General Analysis |
Item.cpp:209 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
Item.cpp:209 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Item.cpp:209 |
High |
V576 |
Incorrect format. Consider checking the seventh actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Item.cpp:209 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Item.cpp:209 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Iterators.cpp:518 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Iterators.cpp:1530 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'u'. |
General Analysis |
kernel_interface.cpp:128 |
High |
V595 |
The 'volume' pointer was utilized before it was verified against nullptr. Check lines: 128, 138. |
General Analysis |
kernel_interface.cpp:575 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Key.h:263 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'u'. |
General Analysis |
Key.h:263 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Key.h:263 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
StatItem.h:240 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
StatItem.h:240 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
SuperBlock.cpp:51 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Tree.cpp:71 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Volume.cpp:366 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Volume.cpp:366 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Volume.cpp:587 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Volume.cpp:349 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
Volume.cpp:349 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'dprintf' function. The memsize type argument is expected. |
General Analysis |
DebugSupport.cpp:54 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Array.h:43 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'sprintf' function. The memsize type argument is expected. |
General Analysis |
Array.h:69 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'sprintf' function. The memsize type argument is expected. |
General Analysis |
Icb.cpp:223 |
High |
V629 |
Consider inspecting the 'logicalBlock << fVolume->BlockShift()' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
UdfString.cpp:102 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCs0Length. |
General Analysis |
UdfStructures.h:1408 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: _tag. |
General Analysis |
UdfStructures.h:829 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: _tag. |
General Analysis |
Volume.cpp:20 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fPrimaryVolumeDescriptor. |
General Analysis |
FileSystem.cpp:161 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNodeListeners. |
General Analysis |
FileSystem.cpp:92 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashTableLink. |
General Analysis |
FileSystem.cpp:334 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
FileSystem.h:37 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: hash_link. |
General Analysis |
KernelRequestHandler.cpp:366 |
High |
V614 |
Potentially uninitialized pointer 'node' used. |
General Analysis |
Volume.cpp:2051 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Volume.cpp:295 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fVolumeOps. |
General Analysis |
Volume.cpp:61 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: hash_link. |
General Analysis |
Volume.cpp:121 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: idLink, structLink. |
General Analysis |
RequestPort.cpp:141 |
High |
V547 |
Expression 'error != ((int) 0)' is always false. |
General Analysis |
Requests.cpp:408 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSuccess. |
General Analysis |
fs_cache.c:894 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:967 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:974 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:981 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1052 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1057 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1074 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1162 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1290 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1406 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1049 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1785 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1578 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1706 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1759 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1770 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:363 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1807 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1856 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1868 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1873 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:2183 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:1078 |
High |
V597 |
The compiler could delete the 'memset' function call, which is used to flush 'ce' object. The memset_s() function should be used to erase the private data. |
General Analysis |
fs_cache.c:194 |
High |
V595 |
The 'ht->table' pointer was utilized before it was verified against nullptr. Check lines: 194, 202. |
General Analysis |
fs_cache.c:1544 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:308 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:523 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:102 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
fs_cache.c:139 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
FileSystem.cpp:16 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fClientFSType. |
General Analysis |
FUSEEntry.h:88 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: hashLink. |
General Analysis |
FUSEVolume.cpp:2215 |
High |
V773 |
The function was exited without releasing the 'cookie' pointer. A memory leak is possible. |
General Analysis |
HaikuKernelIORequest.h:25 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: hashLink. |
General Analysis |
HaikuKernelNode.h:50 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: hashLink. |
General Analysis |
kernel_emu.cpp:93 |
High |
V519 |
The 'copiedPath[len]' variable is assigned values twice successively. Perhaps this is a mistake. Check lines: 92, 93. |
General Analysis |
UserlandRequestHandler.cpp:732 |
High |
V595 |
The 'writeBuffer' pointer was utilized before it was verified against nullptr. Check lines: 732, 750. |
General Analysis |
UserlandRequestHandler.cpp:1145 |
High |
V614 |
Potentially uninitialized pointer 'fileCookie' used. |
General Analysis |
UserlandRequestHandler.cpp:2307 |
High |
V614 |
Potentially uninitialized pointer 'queryCookie' used. |
General Analysis |
UserlandRequestHandler.cpp:2056 |
High |
V614 |
Potentially uninitialized pointer 'indexDirCookie' used. |
General Analysis |
UserlandRequestHandler.cpp:1770 |
High |
V614 |
Potentially uninitialized pointer 'attrCookie' used. |
General Analysis |
UserlandRequestHandler.cpp:1738 |
High |
V614 |
Potentially uninitialized pointer 'attrCookie' used. |
General Analysis |
UserlandRequestHandler.cpp:1572 |
High |
V614 |
Potentially uninitialized pointer 'attrDirCookie' used. |
General Analysis |
UserlandRequestHandler.cpp:1175 |
High |
V614 |
Potentially uninitialized pointer 'fileCookie' used. |
General Analysis |
UserlandRequestHandler.cpp:240 |
High |
V547 |
Expression 'result == ((int) 0)' is always true. |
General Analysis |
UserlandRequestHandler.cpp:494 |
High |
V614 |
Potentially uninitialized pointer 'node' used. |
General Analysis |
Debug.cpp:72 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
ata_adapter.cpp:151 |
High |
V763 |
Parameter 'force_16bit' is always rewritten in function body before being used. |
General Analysis |
ata_adapter.cpp:179 |
High |
V763 |
Parameter 'force_16bit' is always rewritten in function body before being used. |
General Analysis |
arp.cpp:1030 |
High |
V512 |
A call of the 'memcpy' function will lead to overflow of the buffer 'buffer->destination'. |
General Analysis |
ipv6_datagram.cpp:1030 |
High |
V512 |
A call of the 'memcpy' function will lead to overflow of the buffer 'buffer->destination'. |
General Analysis |
ipv6_datagram.cpp:942 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer 'device->address.data'. |
General Analysis |
ipv4.cpp:1811 |
High |
V512 |
A call of the 'memcpy' function will lead to a buffer overflow. |
General Analysis |
ipv6.cpp:1609 |
High |
V512 |
A call of the 'memcpy' function will lead to a buffer overflow. |
General Analysis |
ipv6.cpp:1635 |
High |
V512 |
A call of the 'memcpy' function will lead to a buffer overflow. |
General Analysis |
ipv6_address.cpp:77 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer 'from'. |
General Analysis |
ipv6_address.cpp:402 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer 'address'. |
General Analysis |
ipv6_address.cpp:62 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer '* to'. |
General Analysis |
ipv6_address.cpp:73 |
High |
V641 |
The size of the allocated memory buffer is not a multiple of the element size. |
General Analysis |
ipv6_address.cpp:58 |
High |
V641 |
The size of the allocated memory buffer is not a multiple of the element size. |
General Analysis |
ipv6_address.cpp:402 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer 'from'. |
General Analysis |
ipv6_address.cpp:100 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer 'address'. |
General Analysis |
ipv6_address.cpp:451 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer 'address'. |
General Analysis |
ipv6_address.cpp:100 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer 'result'. |
General Analysis |
ipv6_address.cpp:77 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer '* to'. |
General Analysis |
UnixAddressManager.h:43 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNextInternalID. |
General Analysis |
UnixEndpoint.cpp:42 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCredentials. |
General Analysis |
datalink.cpp:409 |
High |
V595 |
The 'domain' pointer was utilized before it was verified against nullptr. Check lines: 409, 411. |
General Analysis |
datalink.cpp:412 |
High |
V595 |
The 'protocol' pointer was utilized before it was verified against nullptr. Check lines: 412, 416. |
General Analysis |
link.cpp:84 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBoundType. |
General Analysis |
net_socket.cpp:1658 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
net_socket.cpp:1484 |
High |
V547 |
Expression 'status == ((int) 0)' is always true. |
General Analysis |
routes.cpp:40 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: ref_count. |
General Analysis |
stack.cpp:176 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
efi_gpt.cpp:371 |
High |
V547 |
Expression is always false. |
General Analysis |
efi_gpt.cpp:354 |
High |
V547 |
Expression is always false. |
General Analysis |
PartitionMap.cpp:358 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBlockSize. |
General Analysis |
PartitionMap.cpp:484 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fIndex. |
General Analysis |
PartitionMapWriter.cpp:164 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer 'descriptor'. |
General Analysis |
PartitionMapWriter.cpp:218 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer 'descriptor'. |
General Analysis |
Disc.cpp:265 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer 'raw_command.command'. |
General Analysis |
ConfigView.cpp:161 |
High |
V773 |
Visibility scope of the 'actionField' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
StringMatcher.cpp:12 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: _regExp. |
General Analysis |
NotifierFilter.cpp:93 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
SpamFilter.cpp:48 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHeaderOnly, fLaunchAttemptCount. |
General Analysis |
FolderConfigWindow.cpp:331 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
Commands.cpp:345 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fListener. |
General Analysis |
Commands.cpp:359 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fListener. |
General Analysis |
Commands.h:22 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: size. |
General Analysis |
Response.cpp:438 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLiteralHandler, fNextChar. |
General Analysis |
Response.cpp:659 |
High |
V596 |
The object was created but it is not being used. The 'throw' keyword could be missing: throw ParseException(FOO); |
General Analysis |
IMAPConnectionWorker.cpp:312 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFirstIndex, fLastIndex, fTotalEntries, fTotalBytes. |
General Analysis |
IMAPConnectionWorker.cpp:451 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fUID. |
General Analysis |
IMAPConnectionWorker.cpp:238 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFetchStatus. |
General Analysis |
IMAPFolder.cpp:87 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNodeID, fReadFolderStateThread. |
General Analysis |
IMAPFolder.cpp:414 |
High |
V530 |
The return value of function 'begin' is required to be utilized. |
General Analysis |
IMAPProtocol.cpp:299 |
High |
V773 |
The function was exited without releasing the 'folder' pointer. A memory leak is possible. |
General Analysis |
POP3.cpp:66 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTotalSize. |
General Analysis |
SMTP.cpp:243 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSocket, use_ssl, fStatus. |
General Analysis |
MixerCore.cpp:64 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fEventTime, fEventLatency. |
General Analysis |
MultiAudioNode.cpp:148 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fChannelId, fSamplesSent, fOldBufferInfo. |
General Analysis |
MultiAudioNode.cpp:170 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLatency, fInternalLatency, fBufferPeriod. |
General Analysis |
MultiAudioNode.cpp:128 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fChannelId, fOldBufferInfo. |
General Analysis |
OpenSoundDeviceEngine.cpp:27 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fPlayedFramesCount, fPlayedRealTime. |
General Analysis |
OpenSoundDeviceEngine.cpp:330 |
High |
V576 |
Potentially incorrect format string is passed to the '_debugPrintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
NW80xCamDevice.cpp:162 |
High |
V547 |
Expression 'err < 0' is always true. |
General Analysis |
QuickCamDevice.cpp:127 |
High |
V547 |
Expression 'err < 0' is always true. |
General Analysis |
SonixCamDevice.cpp:640 |
High |
V1028 |
Possible overflow. Consider casting operands of the 'w * h' operator to the 'size_t' type, not the result. |
General Analysis |
CamDevice.cpp:422 |
High |
V570 |
The 'data' variable is assigned to itself. |
General Analysis |
CamDevice.cpp:36 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fDeframer, fDataInput, fFirstParameterID, fPumpThread, fDumpFD. |
General Analysis |
CamDevice.cpp:352 |
High |
V570 |
The 'data' variable is assigned to itself. |
General Analysis |
CamSensor.cpp:10 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFirstParameterID. |
General Analysis |
Producer.cpp:467 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:384 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:918 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
Producer.cpp:892 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
Producer.cpp:364 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:364 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:338 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:292 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:384 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:338 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:467 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:788 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
Producer.cpp:542 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:542 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:357 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:399 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:357 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:222 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:399 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
Producer.cpp:37 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFrame, fFrameBase, fPerformanceTimeBase, fConnectedFormat, fColor, fLastColorChange. |
General Analysis |
Producer.cpp:580 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
VideoView.cpp:21 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fOverlayKeyColor. |
General Analysis |
VSTHost.cpp:280 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fModule. |
General Analysis |
VSTNode.cpp:25 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fWeb, fBlockSize, fMute, fByPass, fMuteLastChanged, fByPassLastChanged. |
General Analysis |
AVCodecDecoder.cpp:82 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFormatConversionFunc, fTempPacket, fLastWidth, fLastHeight, fLastPixfmt. |
General Analysis |
AVFormatWriter.cpp:359 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fStreams. |
General Analysis |
CpuCapabilities.cpp:74 |
High |
V547 |
Expression 'maxStandardFunction >= 1' is always true. |
General Analysis |
HTTPMediaIO.cpp:118 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTotalSize. |
General Analysis |
RawDecoderPlugin.cpp:448 |
High |
V547 |
Expression 'ioDecodedFormat->type == 0' is always false. |
General Analysis |
HostnameView.cpp:109 |
High |
V705 |
It is possible that 'else' block was forgotten or commented out, thus altering the program's operation logics. |
General Analysis |
Lips3.cpp:230 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
Lips3.cpp:195 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
Lips3.cpp:25 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCurrentX, fCurrentY. |
General Analysis |
Lips4.cpp:240 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
Lips4.cpp:24 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCurrentX, fCurrentY. |
General Analysis |
Lips4.cpp:205 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
GPDriver.cpp:312 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PCL5.cpp:218 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
DeltaRowCompression.h:102 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fDeltaRow. |
General Analysis |
PCL6.cpp:181 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PCL6Rasterizer.h:26 |
High |
V611 |
The memory was allocated using 'new T[]' operator but was released using the 'delete' operator. Consider inspecting this code. It's probably better to use 'delete [] fOutBuffer;'. Check lines: 26, 45. |
General Analysis |
PS.cpp:341 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PSEntry.cpp:57 |
High |
V773 |
The function was exited without releasing the 'dialog' pointer. A memory leak is possible. |
General Analysis |
PrinterDriver.cpp:28 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fOrientation. |
General Analysis |
HPJetDirectTransport.cpp:75 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
HPJetDirectTransport.cpp:36 |
High |
V773 |
The function was exited without releasing the 'setup' pointer. A memory leak is possible. |
General Analysis |
HPJetDirectTransport.cpp:62 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
SetupWindow.cpp:87 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fServerAddress, fQueuePort. |
General Analysis |
SetupWindow.cpp:144 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
SetupWindow.cpp:160 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
Ipp.cpp:23 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fState. |
General Analysis |
IppSetupDlg.cpp:78 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: url. |
General Analysis |
IppSetupDlg.cpp:147 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
IppTransport.cpp:135 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
IppTransport.cpp:50 |
High |
V773 |
The function was exited without releasing the 'dlg' pointer. A memory leak is possible. |
General Analysis |
URL.cpp:73 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: __port. |
General Analysis |
LprSetupDlg.cpp:161 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
LprSetupDlg.cpp:90 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fServer, fQueue. |
General Analysis |
LprSetupDlg.cpp:147 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
LprTransport.cpp:56 |
High |
V773 |
The function was exited without releasing the 'dlg' pointer. A memory leak is possible. |
General Analysis |
LprTransport.cpp:134 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
LpsClient.cpp:44 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fInput, fOutput. |
General Analysis |
print_transport.cpp:64 |
High |
V773 |
The function was exited without releasing the 'selector' pointer. A memory leak is possible. |
General Analysis |
Socket.cpp:81 |
High |
V512 |
A call of the 'memcpy' function will lead to overflow of the buffer '& sin.sin_addr'. |
General Analysis |
DebugNow.cpp:39 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fDelta. |
General Analysis |
GLifeView.cpp:24 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_glfDelta, m_iStep. |
General Analysis |
IFS.cpp:106 |
High |
V536 |
Be advised that the utilized constant value is represented by an octal form. Oct: 024, Dec: 20. |
General Analysis |
IFSSaver.cpp:44 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fAdditiveCB, fSpeedS. |
General Analysis |
Nebula.cpp:673 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFactor. |
General Analysis |
ZipOMatic.cpp:180 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
ZipOMaticWindow.cpp:217 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
GIFTranslator.cpp:300 |
High |
V576 |
Potentially incorrect format string is passed to the 'syslog' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
ICNSLoader.cpp:225 |
High |
V547 |
Expression 'bpp == 32' is always true. |
General Analysis |
PCX.cpp:149 |
High |
V512 |
A call of the 'memcpy' function will lead to the '& header.paletteInfo' buffer becoming out of range. |
General Analysis |
RAW.cpp:1796 |
High |
V557 |
Array overrun is possible. The '256 - 1' index is pointing beyond array bound. |
General Analysis |
RAW.cpp:1796 |
High |
V557 |
Array overrun is possible. The '256 + 1' index is pointing beyond array bound. |
General Analysis |
RAW.cpp:1785 |
High |
V557 |
Array overrun is possible. The '1' index is pointing beyond array bound. |
General Analysis |
RAW.cpp:1667 |
High |
V548 |
Consider reviewing type casting. TYPE X[][] is not equivalent to TYPE **X. |
General Analysis |
RAW.cpp:2600 |
High |
V593 |
Consider reviewing the expression of the 'A = B >= C' kind. The expression is calculated as following: 'A = (B >= C)'. |
General Analysis |
RAW.cpp:3502 |
High |
V547 |
Expression '(_Raw().width | _Raw().height) < 0' is always false. Unsigned type value is never < 0. |
General Analysis |
RAW.cpp:1098 |
High |
V634 |
The priority of the '*' operation is higher than that of the '<<' operation. It's possible that parentheses should be used in the expression. |
General Analysis |
RAW.cpp:1789 |
High |
V557 |
Array overrun is possible. The '256' index is pointing beyond array bound. |
General Analysis |
RAW.cpp:1140 |
High |
V634 |
The priority of the '*' operation is higher than that of the '<<' operation. It's possible that parentheses should be used in the expression. |
General Analysis |
SGIImage.cpp:262 |
High |
V595 |
The 'fOffsetTable' pointer was utilized before it was verified against nullptr. Check lines: 262, 279. |
General Analysis |
SGIImage.cpp:274 |
High |
V595 |
The 'fLengthTable' pointer was utilized before it was verified against nullptr. Check lines: 274, 285. |
General Analysis |
SGITranslator.cpp:423 |
High |
V576 |
Incorrect format. A different number of actual arguments is expected while calling 'syslog' function. Expected: 3. Present: 2. |
General Analysis |
TranslatorWindow.cpp:93 |
High |
V773 |
The function was exited without releasing the 'err' pointer. A memory leak is possible. |
General Analysis |
STXTTranslator.cpp:622 |
High |
V654 |
The condition 'bytesRead > 0' of loop is always true. |
General Analysis |
STXTTranslator.cpp:390 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer 'buffer'. |
General Analysis |
TGATranslator.cpp:1142 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer 'footer'. |
General Analysis |
TGATranslator.cpp:320 |
High |
V570 |
The 'imagespec.height' variable is assigned to itself. |
General Analysis |
TGATranslator.cpp:315 |
High |
V570 |
The 'imagespec.width' variable is assigned to itself. |
General Analysis |
TGATranslator.cpp:312 |
High |
V570 |
The 'imagespec.yorigin' variable is assigned to itself. |
General Analysis |
TGATranslator.cpp:309 |
High |
V570 |
The 'imagespec.xorigin' variable is assigned to itself. |
General Analysis |
TGATranslator.cpp:289 |
High |
V570 |
The 'mapspec.length' variable is assigned to itself. |
General Analysis |
TGATranslator.cpp:284 |
High |
V570 |
The 'mapspec.firstentry' variable is assigned to itself. |
General Analysis |
ConfigView.cpp:155 |
High |
V773 |
Visibility scope of the 'presetsField' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ActivityView.cpp:1037 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ActivityView.cpp:1504 |
High |
V595 |
The 'be_control_look' pointer was utilized before it was verified against nullptr. Check lines: 1504, 1526. |
General Analysis |
ActivityWindow.cpp:82 |
High |
V773 |
Visibility scope of the 'view' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ActivityWindow.cpp:385 |
High |
V773 |
Visibility scope of the 'view' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
SystemInfo.cpp:15 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBytesReceived, fBytesSent. |
General Analysis |
AutoRaiseIcon.cpp:535 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
BootManagerController.cpp:235 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
BootManagerController.cpp:36 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCollectPartitionsStatus, fWriteBootMenuStatus, fSaveMBRStatus, fRestoreMBRStatus. |
General Analysis |
BootManagerController.cpp:197 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
BootManagerController.cpp:183 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
LegacyBootMenu.cpp:661 |
High |
V512 |
A call of the 'memcpy' function will lead to the 'source->diskSignature' buffer becoming out of range. |
General Analysis |
LegacyBootMenu.cpp:661 |
High |
V512 |
A call of the 'memcpy' function will lead to overflow of the buffer 'destination->diskSignature'. |
General Analysis |
CharacterMap.cpp:22 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fWindow. |
General Analysis |
CharacterView.cpp:308 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
CharacterWindow.cpp:495 |
High |
V547 |
Expression 'status == ((int) 0)' is always true. |
General Analysis |
cl_view.cpp:354 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
CodyCam.cpp:128 |
High |
V542 |
Consider inspecting an odd type cast: 'bool' to 'char *'. |
General Analysis |
SettingsHandler.cpp:48 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNumAvail, fCurrentArgs. |
General Analysis |
SettingsHandler.cpp:173 |
High |
V739 |
EOF should not be compared with a value of the 'char' type. The 'ch' should be of the 'int' type. |
General Analysis |
VideoConsumer.cpp:47 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFtpThread, fFtpBitmap. |
General Analysis |
AudioBuffer.cpp:85 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_format. |
General Analysis |
AudioFilterNode.cpp:190 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
MediaNodeControlApp.cpp:104 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MediaNodeControlApp.cpp:90 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MediaNodeControlApp.cpp:121 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
LoggingConsumer.cpp:93 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: mSchedulingLatency. |
General Analysis |
DiagramView.cpp:57 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_backgroundColor. |
General Analysis |
DormantNodeListItem.cpp:276 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DormantNodeListItem.cpp:70 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_fontHeight. |
General Analysis |
DormantNodeView.cpp:201 |
High |
V595 |
The 'item' pointer was utilized before it was verified against nullptr. Check lines: 201, 202. |
General Analysis |
InfoView.cpp:128 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_sideBarWidth. |
General Analysis |
MediaJack.cpp:768 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MediaNodePanel.cpp:93 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_labelTruncated, m_mouseOverLabel. |
General Analysis |
MediaNodePanel.cpp:678 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MediaRoutingView.cpp:995 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MediaRoutingView.cpp:971 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MediaWire.cpp:338 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Connection.cpp:65 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_flags. |
General Analysis |
NodeGroup.cpp:277 |
High |
V530 |
The return value of function 'remove' is required to be utilized. |
General Analysis |
NodeSyncThread.cpp:156 |
High |
V654 |
The condition '!done' of loop is always true. |
General Analysis |
ParameterWindow.cpp:167 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ExportContext.cpp:263 |
High |
V547 |
Expression 'm_state == ABORT' is always false. |
General Analysis |
ExportContext.cpp:270 |
High |
V547 |
Expression 'm_state == ABORT' is always false. |
General Analysis |
ExportContext.cpp:248 |
High |
V547 |
Expression 'm_state == ABORT' is always false. |
General Analysis |
ValControl.cpp:600 |
High |
V757 |
It is possible that an incorrect variable is compared with nullptr after type conversion using 'dynamic_cast'. Check lines: 600, 601. |
General Analysis |
ValControl.cpp:406 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHaveBackBuffer, fBackBuffer, fBackBufferView. |
General Analysis |
ValControlDigitSegment.cpp:364 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_negative, m_fontHeight, m_yOffset, m_minusSignWidth, m_flags, m_negativeVisible. |
General Analysis |
ValControlDigitSegment.cpp:60 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_fontHeight. |
General Analysis |
GraphicalUserInterface.cpp:259 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
InspectorWindow.cpp:343 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MemoryView.cpp:40 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHexLeft, fHexRight, fTextLeft, fTextRight. |
General Analysis |
MemoryView.cpp:802 |
High |
V570 |
The 'data' variable is assigned to itself. |
General Analysis |
MemoryView.cpp:165 |
High |
V763 |
Parameter 'rect' is always rewritten in function body before being used. |
General Analysis |
MemoryView.cpp:760 |
High |
V570 |
The 'data' variable is assigned to itself. |
General Analysis |
MemoryView.cpp:1080 |
High |
V570 |
The 'address' variable is assigned to itself. |
General Analysis |
MemoryView.cpp:781 |
High |
V570 |
The 'data' variable is assigned to itself. |
General Analysis |
VariablesViewState.cpp:137 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
VariablesViewStateHistory.cpp:48 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
SourceView.cpp:597 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSourceCode. |
General Analysis |
TeamWindow.cpp:125 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
TeamWindow.cpp:2015 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
VariablesView.cpp:3393 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
VariablesView.cpp:262 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNext. |
General Analysis |
VariablesView.cpp:792 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fContextMenu. |
General Analysis |
VariablesView.cpp:122 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
VariablesView.cpp:909 |
High |
V595 |
The 'fContextMenu' pointer was utilized before it was verified against nullptr. Check lines: 909, 925. |
General Analysis |
TeamsWindow.cpp:45 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCreateConnectionButton. |
General Analysis |
TeamsWindow.cpp:351 |
High |
V547 |
Expression 'status == ((int) 0)' is always true. |
General Analysis |
BreakpointEditWindow.cpp:29 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fConditionInput, fAlwaysRadio, fConditionRadio. |
General Analysis |
SignalDispositionEditWindow.cpp:31 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCurrentDisposition. |
General Analysis |
StartTeamWindow.cpp:163 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
WatchPromptWindow.cpp:28 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fWatchButton, fCancelButton. |
General Analysis |
CalendarMenuWindow.cpp:49 |
High |
V763 |
Parameter 'updateRect' is always rewritten in function body before being used. |
General Analysis |
ExpandoMenuBar.cpp:355 |
High |
V757 |
It is possible that an incorrect variable is compared with nullptr after type conversion using 'dynamic_cast'. Check lines: 355, 357. |
General Analysis |
StatusView.cpp:129 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLastReplicant, fItemList. |
General Analysis |
StatusView.cpp:423 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
TeamMenuItem.cpp:99 |
High |
V595 |
The 'fBarView' pointer was utilized before it was verified against nullptr. Check lines: 99, 107. |
General Analysis |
TimeView.cpp:501 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DevicesView.cpp:348 |
High |
V773 |
The 'newDevice' pointer was assigned values twice without releasing the memory. A memory leak is possible. |
General Analysis |
DevicesView.cpp:342 |
High |
V773 |
The 'newDevice' pointer was assigned values twice without releasing the memory. A memory leak is possible. |
General Analysis |
PropertyListPlain.cpp:25 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: rootView. |
General Analysis |
DiskProbe.cpp:390 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ProbeView.cpp:1096 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ProbeView.cpp:1858 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
ProbeView.cpp:1836 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
TypeEditors.cpp:1124 |
High |
V763 |
Parameter 'rect' is always rewritten in function body before being used. |
General Analysis |
ControlsView.cpp:139 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fVolumeRoster. |
General Analysis |
PieView.cpp:128 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCurrentDir, fClickedFile. |
General Analysis |
Scanner.cpp:27 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fVolumeBytesInUse, fVolumeBytesScanned, fProgress, fLastReport. |
General Analysis |
Snapshot.cpp:28 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: color. |
General Analysis |
Snapshot.cpp:112 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: currentDir. |
General Analysis |
MainWindow.cpp:1238 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MainWindow.cpp:1114 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MainWindow.cpp:841 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MainWindow.cpp:915 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MainWindow.cpp:78 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLastPreparedDevice. |
General Analysis |
MainWindow.cpp:1319 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MainWindow.cpp:1405 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MainWindow.cpp:1034 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
ExpanderWindow.cpp:325 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ExpanderWindow.cpp:437 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ExpanderWindow.cpp:239 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
ExpanderWindow.cpp:455 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ExpanderWindow.cpp:465 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ExpanderWindow.cpp:229 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
ExpanderWindow.cpp:213 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
ExpanderWindow.cpp:660 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
ExpanderWindow.cpp:523 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
ExpanderWindow.cpp:204 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
ObjectView.cpp:185 |
High |
V773 |
Visibility scope of the 'NoResourceAlert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ObjectView.cpp:332 |
High |
V773 |
Visibility scope of the 'NoResourceAlert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Camera.cpp:12 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fOrtho. |
General Analysis |
PackageManager.cpp:164 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PackageManager.cpp:288 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PackageManager.cpp:828 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ServerHelper.cpp:86 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ServerHelper.cpp:184 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ServerHelper.cpp:141 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ServerReferenceDataUpdateProcess.cpp:91 |
High |
V773 |
The function was exited without releasing the 'listener' pointer. A memory leak is possible. |
General Analysis |
ServerReferenceDataUpdateProcess.cpp:111 |
High |
V547 |
Expression 'result == ((int) 0)' is always true. |
General Analysis |
Paragraph.cpp:12 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCachedLength. |
General Analysis |
App.cpp:449 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
App.cpp:470 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
App.cpp:335 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MainWindow.cpp:1304 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MainWindow.cpp:1287 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PackageInfoView.cpp:636 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
UserLoginWindow.cpp:682 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
UserLoginWindow.cpp:544 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
UserLoginWindow.cpp:453 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
BitmapView.cpp:15 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBitmapSize. |
General Analysis |
BitmapSetSaver.cpp:43 |
High |
V773 |
The 'exporter' pointer was assigned values twice without releasing the memory. A memory leak is possible. |
General Analysis |
BitmapSetSaver.cpp:50 |
High |
V773 |
The 'exporter' pointer was assigned values twice without releasing the memory. A memory leak is possible. |
General Analysis |
BitmapSetSaver.cpp:54 |
High |
V773 |
The function was exited without releasing the 'exporter' pointer. A memory leak is possible. |
General Analysis |
Scrollable.cpp:42 |
High |
V522 |
Dereferencing of the null pointer 'fScrollSource' might take place. |
General Analysis |
PropertyListView.cpp:87 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSelectM, fSelectAllMI, fSelectNoneMI, fInvertSelectionMI, fCopyMI, fPasteMI. |
General Analysis |
OptionValueView.cpp:158 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
SavePanel.cpp:80 |
High |
V595 |
The 'background' pointer was utilized before it was verified against nullptr. Check lines: 80, 85. |
General Analysis |
StyleListView.cpp:267 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fAddMI, fDuplicateMI, fResetTransformationMI, fRemoveMI. |
General Analysis |
SwatchGroup.cpp:48 |
High |
V763 |
Parameter 'frame' is always rewritten in function body before being used. |
General Analysis |
TransformerListView.cpp:106 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMenu. |
General Analysis |
Exporter.cpp:121 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MessageExporter.cpp:46 |
High |
V547 |
Expression 'ret == ((int) 0)' is always true. |
General Analysis |
StyledTextImporter.cpp:263 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
DocumentBuilder.h:118 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: opacity. |
General Analysis |
SVGImporter.cpp:88 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
SVGParser.cpp:349 |
High |
V773 |
The exception was thrown without closing the file referenced by the 'fd' handle. A resource leak is possible. |
General Analysis |
MainWindow.cpp:1294 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MainWindow.cpp:810 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MainWindow.cpp:731 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PathManipulator.cpp:266 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBlack, fSkip. |
General Analysis |
PathManipulator.cpp:814 |
High |
V773 |
The function was exited without releasing the 'menu' pointer. A memory leak is possible. |
General Analysis |
CopyEngine.cpp:398 |
High |
V547 |
Expression 'ret < ((int) 0)' is always false. |
General Analysis |
InstallerApp.cpp:62 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fEULAWindow. |
General Analysis |
InstallerApp.cpp:104 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
InstallerWindow.cpp:681 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
InstallerWindow.cpp:638 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
InstallerWindow.cpp:355 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
InstallerWindow.cpp:712 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
InstallerWindow.cpp:913 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
InstallerWindow.cpp:629 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
InstallerWindow.cpp:619 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
InstallerWindow.cpp:611 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
InstallerWindow.cpp:603 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
WorkerThread.cpp:439 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
WorkerThread.cpp:477 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
WorkerThread.cpp:406 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MainWindow.cpp:107 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MainWindow.cpp:182 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PadView.cpp:456 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Magnify.cpp:1263 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fImageFrozenOnSave. |
General Analysis |
AddressTextControl.cpp:188 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fModificationMessage. |
General Analysis |
Content.cpp:2345 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors and destructors. |
General Analysis |
Content.cpp:2265 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors and destructors. |
General Analysis |
Content.cpp:2235 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors and destructors. |
General Analysis |
Content.cpp:771 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Content.cpp:1826 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Content.cpp:2285 |
High |
V595 |
The 'type.Type()' pointer was utilized before it was verified against nullptr. Check lines: 2285, 2289. |
General Analysis |
Content.cpp:1979 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Content.cpp:3305 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Enclosures.cpp:312 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Enclosures.cpp:258 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Header.cpp:452 |
High |
V773 |
Visibility scope of the 'fromField' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
KUndoBuffer.cpp:17 |
High |
V595 |
The 'RedoText' pointer was utilized before it was verified against nullptr. Check lines: 17, 18. |
General Analysis |
MailWindow.cpp:2579 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MailWindow.cpp:1848 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MailWindow.cpp:1828 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MailWindow.cpp:1436 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MailWindow.cpp:3254 |
High |
V773 |
The function was exited without releasing the 'term' pointer. A memory leak is possible. |
General Analysis |
MailWindow.cpp:2308 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MailWindow.cpp:1751 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MailWindow.cpp:1673 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MailWindow.cpp:2407 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MailWindow.cpp:1268 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Signature.cpp:483 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fParent. |
General Analysis |
Signature.cpp:246 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Signature.cpp:307 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
WIndex.cpp:83 |
High |
V773 |
The function was exited without releasing the 'dataFile' pointer. A memory leak is possible. |
General Analysis |
Mandelbrot.cpp:83 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMouseButtons. |
General Analysis |
MediaConverterApp.cpp:431 |
High |
V547 |
Expression 'rvf->display.format == B_RGBA32' is always false. |
General Analysis |
MediaConverterApp.cpp:146 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MediaConverterApp.cpp:217 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MediaConverterWindow.cpp:1022 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MediaConverterWindow.cpp:490 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MediaFileInfoView.cpp:170 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Controller.cpp:746 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PeakView.cpp:163 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
VolumeSlider.cpp:22 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMinSnap, fMaxSnap. |
General Analysis |
MainApp.cpp:71 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MainWin.cpp:1416 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MainWin.cpp:2124 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MainWin.cpp:1177 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
VideoConsumer.cpp:49 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fPerformanceTimeBase. |
General Analysis |
VideoProducer.cpp:773 |
High |
V593 |
Consider reviewing the expression of the 'A = B != C' kind. The expression is calculated as following: 'A = (B != C)'. |
General Analysis |
VideoProducer.cpp:42 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBufferDuration, fConnectedFormat. |
General Analysis |
NetworkStreamWin.cpp:71 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PlaylistListView.cpp:219 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFontHeight. |
General Analysis |
PlaylistWindow.cpp:89 |
High |
V763 |
Parameter 'frame' is always rewritten in function body before being used. |
General Analysis |
PlaylistWindow.cpp:63 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
RemovePLItemsCommand.cpp:126 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
UrlPlaylistItem.cpp:29 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fDuration. |
General Analysis |
UrlPlaylistItem.cpp:23 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fDuration. |
General Analysis |
SettingsWindow.cpp:210 |
High |
V773 |
Visibility scope of the 'buttonBox' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
SettingsWindow.cpp:210 |
High |
V773 |
Visibility scope of the 'settingsBox' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MidiPlayerWindow.cpp:397 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ScopeView.cpp:40 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fIsFinished. |
General Analysis |
NetworkStatus.cpp:163 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
NetworkStatusView.cpp:569 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
NetworkStatusView.cpp:474 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
OverlayView.cpp:184 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
OverlayView.cpp:61 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fText. |
General Analysis |
PackageInfo.cpp:1089 |
High |
V773 |
The function was exited without releasing the 'warning' pointer. A memory leak is possible. |
General Analysis |
PackageInstall.cpp:39 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fItemExistsPolicy. |
General Analysis |
PackageInstall.cpp:166 |
High |
V773 |
The function was exited without releasing the 'reinstall' pointer. A memory leak is possible. |
General Analysis |
PackageView.cpp:556 |
High |
V773 |
Visibility scope of the 'installType' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PackageView.cpp:386 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PackageView.cpp:139 |
High |
V773 |
Visibility scope of the 'text' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PackageView.cpp:92 |
High |
V773 |
The function was exited without releasing the 'warning' pointer. A memory leak is possible. |
General Analysis |
UninstallView.cpp:374 |
High |
V547 |
Expression is always true. |
General Analysis |
PairsWindow.cpp:335 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PeopleApp.cpp:252 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PersonWindow.cpp:227 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PersonWindow.cpp:318 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PictureView.cpp:389 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PictureView.cpp:569 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
libhttpd.c:2795 |
High |
V773 |
The function was exited without releasing the 'nameptrs' pointer. A memory leak is possible. |
General Analysis |
libhttpd.c:2795 |
High |
V773 |
The function was exited without releasing the 'names' pointer. A memory leak is possible. |
General Analysis |
libhttpd.c:260 |
High |
V773 |
The function was exited without releasing the 'hs' pointer. A memory leak is possible. |
General Analysis |
PoorManAdvancedView.cpp:54 |
High |
V773 |
Visibility scope of the 'connectionOptions' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PoorManLoggingView.cpp:83 |
High |
V773 |
Visibility scope of the 'fileLogging' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PoorManLoggingView.cpp:83 |
High |
V773 |
Visibility scope of the 'consoleLogging' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PoorManServer.cpp:32 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fListenerTid. |
General Analysis |
PoorManSiteView.cpp:79 |
High |
V773 |
Visibility scope of the 'webSiteOptions' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PoorManSiteView.cpp:79 |
High |
V773 |
Visibility scope of the 'webSiteLocation' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PoorManWindow.cpp:585 |
High |
V773 |
Visibility scope of the 'serverAlert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PoorManWindow.cpp:585 |
High |
V773 |
Visibility scope of the 'dirAlert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ExtendedInfoWindow.cpp:288 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSelected. |
General Analysis |
PowerStatus.cpp:105 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PowerStatusView.cpp:736 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MemoryBarMenu.cpp:39 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLastTotalTime. |
General Analysis |
PCWorld.cpp:111 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PCWorld.cpp:102 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
Preferences.cpp:120 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ProcessController.cpp:487 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ThreadBarMenuItem.cpp:29 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fUser. |
General Analysis |
ConfigView.cpp:78 |
High |
V763 |
Parameter 'rect' is always rewritten in function body before being used. |
General Analysis |
CPUButton.cpp:249 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
CPUButton.cpp:211 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DeskbarPulseView.cpp:186 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PulseApp.cpp:199 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PulseApp.cpp:284 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PulseView.cpp:156 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
RemoteView.cpp:1269 |
High |
V774 |
The 'string' pointer was used after the memory was released. |
General Analysis |
ScreenshotWindow.cpp:254 |
High |
V773 |
Visibility scope of the 'divider' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ScreenshotWindow.cpp:681 |
High |
V773 |
The function was exited without releasing the 'overwriteAlert' pointer. A memory leak is possible. |
General Analysis |
ScreenshotWindow.cpp:142 |
High |
V607 |
Ownerless expression 'name << 1'. |
General Analysis |
ScreenshotWindow.cpp:628 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ScreenshotWindow.cpp:254 |
High |
V773 |
Visibility scope of the 'menuLocation' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ScreenshotWindow.cpp:254 |
High |
V773 |
Visibility scope of the 'menuFormat' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ScreenshotWindow.cpp:717 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Utility.cpp:47 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: borderSize. |
General Analysis |
ProgressWindow.cpp:28 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fRetrievedUpdate, fRetrievedShow. |
General Analysis |
ShowImageView.cpp:173 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fImageOrientation. |
General Analysis |
ShowImageView.cpp:963 |
High |
V773 |
Visibility scope of the 'palert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ShowImageWindow.cpp:1110 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ShowImageWindow.cpp:1237 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
SoftwareUpdaterWindow.cpp:339 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
SoftwareUpdaterWindow.cpp:537 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
UpdateManager.cpp:236 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
RecorderWindow.cpp:1320 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
RecorderWindow.cpp:1314 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
RecorderWindow.cpp:1150 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
RecorderWindow.cpp:1075 |
High |
V595 |
The 'track' pointer was utilized before it was verified against nullptr. Check lines: 1075, 1083. |
General Analysis |
RecorderWindow.cpp:1328 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ScopeView.cpp:333 |
High |
V595 |
The 'fBitmap' pointer was utilized before it was verified against nullptr. Check lines: 333, 336. |
General Analysis |
ScopeView.cpp:27 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fRenderSem, fPreview. |
General Analysis |
TrackSlider.cpp:68 |
High |
V595 |
The 'fBitmap' pointer was utilized before it was verified against nullptr. Check lines: 68, 71. |
General Analysis |
TrackSlider.cpp:480 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fRight, fLeftX, fRightX, fPositionX, fLastX. |
General Analysis |
UpDownButton.cpp:11 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTrackingY. |
General Analysis |
VolumeSlider.cpp:17 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fVolume. |
General Analysis |
StatusView.cpp:189 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Sudoku.cpp:26 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fWindow. |
General Analysis |
SudokuWindow.cpp:417 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
TermApp.cpp:136 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
TermView.cpp:2008 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
TermViewStates.cpp:894 |
High |
V530 |
The return value of function 'strtol' is required to be utilized. |
General Analysis |
TermWindow.cpp:1260 |
High |
V595 |
The 'fTabView' pointer was utilized before it was verified against nullptr. Check lines: 1260, 1277. |
General Analysis |
TermWindow.cpp:813 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
GrepWindow.cpp:1233 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
GrepWindow.cpp:1326 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
MainWin.cpp:603 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
BrowserApp.cpp:391 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
BrowserApp.cpp:109 |
High |
V573 |
Uninitialized variable 'cookieArchive' was used. The variable was used to initialize itself. |
General Analysis |
BrowserWindow.cpp:948 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
BrowserWindow.cpp:2678 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
BrowserWindow.cpp:1791 |
High |
V773 |
The function was exited without releasing the 'panel' pointer. A memory leak is possible. |
General Analysis |
BrowserWindow.cpp:1897 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
BrowserWindow.cpp:2023 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
BrowserWindow.cpp:2049 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
BrowserWindow.cpp:1928 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
DownloadProgressView.cpp:590 |
High |
V773 |
Visibility scope of the 'contextMenu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DownloadProgressView.cpp:420 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DownloadWindow.cpp:278 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
TabView.cpp:27 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fIsFirst, fIsLast, fIsFront. |
General Analysis |
URLInputGroup.cpp:265 |
High |
V773 |
The function was exited without releasing the 'menu' pointer. A memory leak is possible. |
General Analysis |
Workspaces.cpp:857 |
High |
V763 |
Parameter 'height' is always rewritten in function body before being used. |
General Analysis |
Workspaces.cpp:698 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Workspaces.cpp:856 |
High |
V763 |
Parameter 'width' is always rewritten in function body before being used. |
General Analysis |
alert.cpp:213 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
BPlusTree.cpp:95 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCurrentKey, fDuplicateNode, fDuplicate, fNumDuplicates, fIsFragment. |
General Analysis |
Hashtable.cpp:35 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCount, fIteratorEntry. |
General Analysis |
Hashtable.cpp:216 |
High |
V772 |
Calling a 'delete' operator for a void pointer will cause undefined behavior. |
General Analysis |
Hashtable.cpp:207 |
High |
V772 |
Calling a 'delete' operator for a void pointer will cause undefined behavior. |
General Analysis |
Inode.cpp:676 |
High |
V629 |
Consider inspecting the 'fRun.length << fDisk->BlockShift()' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Inode.cpp:1312 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTo. |
General Analysis |
Inode.cpp:1318 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTo. |
General Analysis |
Inode.cpp:732 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Inode.cpp:756 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Inode.cpp:909 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
recover.cpp:295 |
High |
V629 |
Consider inspecting the 'disk.Log().length << disk.BlockShift()' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
recover.cpp:308 |
High |
V629 |
Consider inspecting the 'disk.Log().length << disk.BlockShift()' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
recover.cpp:42 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fPercentUsed. |
General Analysis |
recover.cpp:474 |
High |
V757 |
It is possible that an incorrect variable is compared with nullptr after type conversion using 'dynamic_cast'. Check lines: 474, 476. |
General Analysis |
cddb_lookup.cpp:120 |
High |
V641 |
The size of the allocated memory buffer is not a multiple of the element size. |
General Analysis |
cddb_server.h:45 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: year. |
General Analysis |
checkitout.cpp:64 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
BasicProfileResult.cpp:225 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
BasicProfileResult.cpp:201 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
CallgrindProfileResult.cpp:205 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
CallgrindProfileResult.cpp:293 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
CallgrindProfileResult.cpp:293 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
CallgrindProfileResult.cpp:190 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'snprintf' function. The memsize type argument is expected. |
General Analysis |
CallgrindProfileResult.cpp:298 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
CallgrindProfileResult.cpp:305 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
CallgrindProfileResult.cpp:309 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
profile.cpp:861 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
SharedImage.cpp:59 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
SharedImage.cpp:20 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fInfo. |
General Analysis |
SharedImage.cpp:46 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
SummaryProfileResult.cpp:15 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashNext. |
General Analysis |
Team.cpp:74 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
Team.cpp:82 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
Team.cpp:163 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
Team.cpp:121 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
Team.cpp:115 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'snprintf' function. The memsize type argument is expected. |
General Analysis |
DeskButton.cpp:192 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MediaReplicant.cpp:495 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MediaReplicant.cpp:294 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
VolumeControl.cpp:61 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fOriginalValue, fMinSnap, fMaxSnap, fMediaServerRunning, fAddOnServerRunning. |
General Analysis |
diskimage.cpp:248 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
mail2mbox.cpp:58 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'snprintf' function. The memsize type argument is expected. |
General Analysis |
spamdbm.cpp:2545 |
High |
V773 |
Visibility scope of the 'AboutAlertPntr' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
spamdbm.cpp:1845 |
High |
V773 |
The 'AlertPntr' pointer was assigned values twice without releasing the memory. A memory leak is possible. |
General Analysis |
spamdbm.cpp:1513 |
High |
V773 |
Visibility scope of the 'AlertPntr' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
spamdbm.cpp:4929 |
High |
V773 |
Visibility scope of the 'TempWindowPntr' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
spamdbm.cpp:7141 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_CachedTotalGenuineMessages, m_CachedTotalSpamMessages, m_CachedWordCount. |
General Analysis |
spamdbm.cpp:3706 |
High |
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. |
General Analysis |
spamdbm.cpp:3750 |
High |
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. |
General Analysis |
spamdbm.cpp:3679 |
High |
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. |
General Analysis |
spamdbm.cpp:3687 |
High |
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. |
General Analysis |
spamdbm.cpp:3693 |
High |
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. |
General Analysis |
spamdbm.cpp:3700 |
High |
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. |
General Analysis |
spamdbm.cpp:3769 |
High |
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. |
General Analysis |
spamdbm.cpp:3755 |
High |
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. |
General Analysis |
spamdbm.cpp:3762 |
High |
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. |
General Analysis |
MediaPlay.cpp:77 |
High |
V595 |
The 'track' pointer was utilized before it was verified against nullptr. Check lines: 77, 82. |
General Analysis |
mimeset.cpp:241 |
High |
V1010 |
Unchecked tainted data is used in index: 'strlen(name)'. |
General Analysis |
mkdos.cpp:325 |
High |
V646 |
Consider inspecting the application's logic. It's possible that 'else' keyword is missing. |
General Analysis |
mkdos.cpp:575 |
High |
V547 |
Expression 'numFATs > 1' is always true. |
General Analysis |
login.cpp:38 |
High |
V739 |
EOF should not be compared with a value of the 'char' type. The '(c = fgetc(stdin))' should be of the 'int' type. |
General Analysis |
passwd.cpp:175 |
High |
V575 |
The null pointer is passed into 'crypt' function. Inspect the second argument. |
General Analysis |
cmds.c:168 |
High |
V1010 |
Unchecked tainted data is used in index: 'line'. |
General Analysis |
cmds.c:1502 |
High |
V1010 |
Unchecked tainted data is used in index: 'strlen(acct)'. |
General Analysis |
cmds.c:2667 |
High |
V590 |
Consider inspecting the 'argc == 0 || argc != 2' expression. The expression is excessive or contains a misprint. |
General Analysis |
fetch.c:198 |
High |
V1010 |
Unchecked tainted data is used in index: 'strlen(user)'. |
General Analysis |
fetch.c:216 |
High |
V1010 |
Unchecked tainted data is used in the third argument: 'rlen'. Check lines: 216, 214. |
General Analysis |
fetch.c:1061 |
High |
V1010 |
Unchecked tainted data is used in index: 'reply[0]'. |
General Analysis |
fetch.c:961 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'warnx' function. A null pointer is used. |
General Analysis |
fetch.c:1727 |
High |
V614 |
Uninitialized variable 'rval' used. |
General Analysis |
fetch.c:207 |
High |
V1010 |
Unchecked tainted data is used in the third argument: 'clen'. Check lines: 207, 205. |
General Analysis |
ftp.c:1594 |
High |
V547 |
Expression 'data_addr.si_su.su_sin.sin_family == 1' is always true. |
General Analysis |
main.c:1010 |
High |
V591 |
Non-void function should return a value. |
General Analysis |
util.c:418 |
High |
V1010 |
Unchecked tainted data is used in index: 'strlen(tmp)'. |
General Analysis |
util.c:1260 |
High |
V547 |
Expression 'rv == 1' is always false. |
General Analysis |
ifconfig.cpp:610 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
ifconfig.cpp:606 |
High |
V576 |
Potentially incorrect format string is passed to the 'printf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
netstat.cpp:201 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
netstat.cpp:199 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
ping6.c:1295 |
High |
V507 |
Pointer to local array 'iov' is stored outside the scope of this array. Such a pointer will become invalid. |
General Analysis |
ping6.c:998 |
High |
V641 |
The size of the allocated memory buffer is not a multiple of the element size. |
General Analysis |
ping6.c:1604 |
High |
V547 |
Expression 'i > 0' is always false. |
General Analysis |
route.cpp:200 |
High |
V595 |
The 'family' pointer was utilized before it was verified against nullptr. Check lines: 200, 219. |
General Analysis |
commands.c:2873 |
High |
V614 |
Uninitialized pointer 'res' used. |
General Analysis |
state.c:1521 |
High |
V547 |
Expression 'i == 255' is always false. |
General Analysis |
state.c:1527 |
High |
V547 |
Expression 'i == 255' is always false. |
General Analysis |
telnetd.c:413 |
High |
V536 |
Be advised that the utilized constant value is represented by an octal form. Oct: 020, Dec: 16. |
General Analysis |
telnetd.c:412 |
High |
V547 |
Expression 'tos < 0' is always true. |
General Analysis |
utility.c:231 |
High |
V501 |
There are identical sub-expressions '(nfrontp > next)' to the left and to the right of the '&&' operator. |
General Analysis |
command_checksum.cpp:136 |
High |
V773 |
The function was exited without releasing the 'inputFileFile' pointer. A memory leak is possible. |
General Analysis |
command_extract.cpp:164 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashTableNext. |
General Analysis |
command_recompress.cpp:119 |
High |
V773 |
The function was exited without releasing the 'inputFileFile' pointer. A memory leak is possible. |
General Analysis |
pc.c:316 |
High |
V590 |
Consider inspecting the '* ptr == ';' && * ptr != '\0'' expression. The expression is excessive or contains a misprint. |
General Analysis |
pc.c:287 |
High |
V1010 |
Unchecked tainted data is used in index: 'strlen(buff)'. |
General Analysis |
PackageManager.cpp:36 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fShowProgress, fLastBytes, fLastRateCalcTime, fDownloadRate. |
General Analysis |
reindex.cpp:58 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fType. |
General Analysis |
setdecor.cpp:102 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
setdecor.cpp:102 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
setdecor.cpp:138 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
setdecor.cpp:138 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
setmime.cpp:727 |
High |
V575 |
The null pointer is passed into 'free' function. Inspect the first argument. |
General Analysis |
translate.cpp:429 |
High |
V672 |
There is probably no need in creating the new 'path' variable here. One of the function's arguments possesses the same name and this argument is a reference. Check lines: 348, 429. |
General Analysis |
beos.c:1140 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'sprintf' function. The memsize type argument is expected. |
General Analysis |
envargs.c:114 |
High |
V767 |
Suspicious access to element of 'bufptr' array by a constant index inside a loop. |
General Analysis |
envargs.c:192 |
High |
V767 |
Suspicious access to element of 's' array by a constant index inside a loop. |
General Analysis |
extract.c:1259 |
High |
V1010 |
Unchecked tainted data is used in index: 'fnlen'. |
General Analysis |
fileio.c:1716 |
High |
V1028 |
Possible overflow. Consider casting operands of the 'days + dy' operator to the 'unsigned long' type, not the result. |
General Analysis |
unzip.c:1917 |
High |
V547 |
Expression 'numopts == 0' is always false. |
General Analysis |
unzip.h:76 |
High |
V1040 |
Possible typo in the spelling of a pre-defined macro name. The '_unix' macro is similar to '__unix'. |
General Analysis |
unzip.h:91 |
High |
V1040 |
Possible typo in the spelling of a pre-defined macro name. The '_unix' macro is similar to '__unix'. |
General Analysis |
zipinfo.c:745 |
High |
V773 |
The function was exited without releasing the 'fn_matched' pointer. A memory leak is possible. |
General Analysis |
zipinfo.c:745 |
High |
V773 |
The function was exited without releasing the 'xn_matched' pointer. A memory leak is possible. |
General Analysis |
urlwrapper.cpp:66 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
writembr.cpp:99 |
High |
V590 |
Consider inspecting this expression. The expression is excessive or contains a misprint. |
General Analysis |
Message.cpp:307 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer 'fHeader'. |
General Analysis |
Message.cpp:1396 |
High |
V781 |
The value of the 'field->count' variable is checked after it was used. Perhaps there is a mistake in program logic. Check lines: 1396, 1403. |
General Analysis |
Message.cpp:1207 |
High |
V781 |
The value of the 'size' variable is checked after it was used. Perhaps there is a mistake in program logic. Check lines: 1207, 1208. |
General Analysis |
AppFileInfo.cpp:1009 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
AppFileInfo.cpp:1049 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
AppFileInfo.cpp:723 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
AppFileInfo.cpp:599 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Directory.cpp:681 |
High |
V654 |
The condition 'error == ((int) 0)' of loop is always true. |
General Analysis |
Directory.cpp:688 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
NodeInfo.cpp:651 |
High |
V547 |
Expression 'error == ((int) 0)' is always false. |
General Analysis |
NodeInfo.cpp:694 |
High |
V547 |
Expression 'error == ((int) 0)' is always false. |
General Analysis |
NodeInfo.cpp:449 |
High |
V547 |
Expression 'verb == B_OPEN' is always true. |
General Analysis |
Volume.cpp:136 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Volume.cpp:135 |
High |
V547 |
Expression 'device >= 0' is always true. Unsigned type value is always >= 0. |
General Analysis |
Volume.cpp:142 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
misc.cpp:56 |
High |
V547 |
Expression 'sleep((unsigned) secs) < 0' is always false. Unsigned type value is never < 0. |
General Analysis |
Cursor.cpp:81 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: _reservedWasPendingViewCursor, _reserved. |
General Analysis |
Cursor.cpp:29 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: _reservedWasPendingViewCursor, _reserved. |
General Analysis |
Cursor.cpp:64 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: _reservedWasPendingViewCursor, _reserved. |
General Analysis |
Message.cpp:1811 |
High |
V781 |
The value of the 'field->count' variable is checked after it was used. Perhaps there is a mistake in program logic. Check lines: 1811, 1818. |
General Analysis |
Message.cpp:380 |
High |
V512 |
A call of the 'memset' function will lead to underflow of the buffer 'fHeader'. |
General Analysis |
Message.cpp:1606 |
High |
V781 |
The value of the 'size' variable is checked after it was used. Perhaps there is a mistake in program logic. Check lines: 1606, 1607. |
General Analysis |
Roster.cpp:866 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Roster.cpp:1322 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Roster.cpp:1526 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Roster.cpp:1683 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Roster.cpp:2783 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Roster.cpp:2820 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Roster.cpp:841 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Roster.cpp:2713 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
DiscoveryAgent.cpp:136 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLastUsedListener. |
General Analysis |
DiscoveryListener.cpp:149 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLocalDevice. |
General Analysis |
RemoteDevice.cpp:293 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fPageRepetitionMode, fScanPeriodMode, fScanMode, fClockOffset. |
General Analysis |
DebugLooper.cpp:31 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fResult. |
General Analysis |
TeamDebugger.cpp:153 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNext. |
General Analysis |
TeamDebugger.cpp:215 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTeamDebugInfo. |
General Analysis |
ThreadHandler.cpp:953 |
High |
V773 |
The function was exited without releasing the 'listener' pointer. A memory leak is possible. |
General Analysis |
ThreadHandler.cpp:811 |
High |
V595 |
The 'cpuState' pointer was utilized before it was verified against nullptr. Check lines: 811, 818. |
General Analysis |
ThreadHandler.cpp:79 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNext. |
General Analysis |
DwarfImageDebugInfo.cpp:267 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
DwarfStackFrameDebugInfo.cpp:167 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTypeFactory. |
General Analysis |
DwarfTypeFactory.cpp:792 |
High |
V595 |
The 'baseTypeEntry' pointer was utilized before it was verified against nullptr. Check lines: 792, 799. |
General Analysis |
Function.cpp:13 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNext. |
General Analysis |
TeamDebugInfo.cpp:90 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNext. |
General Analysis |
BreakpointManager.cpp:504 |
High |
V547 |
Expression 'error != ((int) 0)' is always false. |
General Analysis |
TeamMemoryBlockManager.cpp:42 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
AbbreviationTable.h:21 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
BaseUnit.cpp:15 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSourceLanguage. |
General Analysis |
DataReader.h:110 |
High |
V598 |
The 'memcpy' function is used to copy the fields of 'Type' class. Virtual table pointer will be damaged by this. |
General Analysis |
DebugInfoEntries.cpp:2252 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fIsExternal. |
General Analysis |
DwarfExpressionEvaluator.cpp:110 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fObjectAddress, fFrameAddress, fObjectAddressValid, fFrameAddressValid. |
General Analysis |
DwarfFile.cpp:1947 |
High |
V547 |
Expression 'remaining < 0' is always false. Unsigned type value is never < 0. |
General Analysis |
TypeUnit.h:56 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
FileManager.cpp:492 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
FileManager.cpp:360 |
High |
V595 |
The 'parentDirectory' pointer was utilized before it was verified against nullptr. Check lines: 360, 369. |
General Analysis |
LocatableEntry.cpp:24 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNext. |
General Analysis |
ExpressionValues.cpp:49 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
ImageInfo.cpp:9 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fType. |
General Analysis |
StackFrameValueInfos.cpp:45 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
StackFrameValues.cpp:42 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
TypeLookupConstraints.cpp:18 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSubtypeKind. |
General Analysis |
TypeLookupConstraints.cpp:10 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTypeKind, fSubtypeKind. |
General Analysis |
LocalTargetHostInterface.cpp:30 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fPortWorker. |
General Analysis |
ValueLocation.cpp:72 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fWritable. |
General Analysis |
UiUtils.cpp:544 |
High |
V609 |
Divide by zero. Denominator range [0..64]. |
General Analysis |
Worker.cpp:106 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNext. |
General Analysis |
Worker.cpp:228 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fWorkToDoSem. |
General Analysis |
DirectWindow.cpp:539 |
High |
V547 |
Expression 'status == ((int) 0)' is always true. |
General Analysis |
GameProducer.cpp:41 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fStartTime, fFramesSent, fBufferSize. |
General Analysis |
GameSound.cpp:26 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFormat, _reserved. |
General Analysis |
PushGameSound.cpp:39 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLock, _reserved. |
General Analysis |
PushGameSound.cpp:19 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLock, _reserved. |
General Analysis |
AbstractSpinner.cpp:266 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: font_info. |
General Analysis |
BMCPrivate.cpp:119 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fPreviousWidth. |
General Analysis |
ColumnListView.cpp:585 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFieldID, fSortAscending, fWantsEvents. |
General Analysis |
Dragger.cpp:332 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Gradient.cpp:87 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fData. |
General Analysis |
HaikuControlLook.cpp:2005 |
High |
V595 |
The 'icon' pointer was utilized before it was verified against nullptr. Check lines: 2005, 2019. |
General Analysis |
ComplexLayouter.cpp:163 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMin, fMax. |
General Analysis |
LayoutOptimizer.cpp:532 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fActiveMatrix, fActiveMatrixTemp. |
General Analysis |
ListItem.cpp:34 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTemporaryList. |
General Analysis |
MenuField.cpp:143 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: font_info, label_width, label_height. |
General Analysis |
MenuWindow.cpp:234 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fValue, fLimit. |
General Analysis |
PictureButton.cpp:17 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: unused, _reserved. |
General Analysis |
PictureButton.cpp:31 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: unused, _reserved. |
General Analysis |
PicturePlayer.cpp:124 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
PicturePlayer.cpp:203 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
Polygon.cpp:167 |
High |
V630 |
The 'realloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
PopUpMenu.cpp:39 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: _fUnusedBool1, _fUnusedBool2, _reserved. |
General Analysis |
PopUpMenu.cpp:55 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: _fUnusedBool1, _fUnusedBool2, _reserved. |
General Analysis |
PrintJob.cpp:109 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ScrollBar.cpp:282 |
High |
V547 |
Expression 'fOrientation == B_VERTICAL' is always true. |
General Analysis |
ScrollView.cpp:53 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBorders, _reserved. |
General Analysis |
Shape.cpp:623 |
High |
V630 |
The 'realloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
TextControl.cpp:129 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: font_info, label_width, label_height. |
General Analysis |
TextInput.cpp:30 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBool. |
General Analysis |
TextInput.cpp:40 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBool. |
General Analysis |
TextView.cpp:5596 |
High |
V506 |
Pointer to local variable 'normalized' is stored outside the scope of this variable. Such a pointer will become invalid. |
General Analysis |
View.cpp:4535 |
High |
V595 |
The 'fOwner' pointer was utilized before it was verified against nullptr. Check lines: 4535, 4539. |
General Analysis |
Window.cpp:226 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: focus. |
General Analysis |
ZombieReplicantView.cpp:32 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fArchive. |
General Analysis |
TimeUnitFormat.cpp:125 |
High |
V773 |
The function was exited without releasing the 'timeUnitAmount' pointer. A memory leak is possible. |
General Analysis |
UnicodeChar.cpp:222 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:27 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:49 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:58 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:67 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:77 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:214 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:230 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:89 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:37 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:115 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:126 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:142 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:152 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:163 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:186 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:196 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:206 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
UnicodeChar.cpp:103 |
High |
V603 |
The object was created but it is not being used. If you wish to call constructor, 'this->BUnicodeChar::BUnicodeChar(....)' should be used. |
General Analysis |
b_mail_message.cpp:29 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMultiPart. |
General Analysis |
FileConfigView.cpp:131 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMeta, _reserved. |
General Analysis |
mail_encoding.cpp:211 |
High |
V547 |
Expression 'n >= 1' is always true. |
General Analysis |
MailMessage.cpp:677 |
High |
V763 |
Parameter 'length' is always rewritten in function body before being used. |
General Analysis |
BufferConsumer.cpp:281 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors and destructors. |
General Analysis |
BufferConsumer.cpp:139 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors and destructors. |
General Analysis |
BufferConsumer.cpp:512 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors and destructors. |
General Analysis |
DormantNodeManager.cpp:220 |
High |
V547 |
Expression 'status < ((int) 0)' is always false. |
General Analysis |
MediaClient.cpp:182 |
High |
V501 |
There are identical sub-expressions to the left and to the right of the '||' operator: input == __null || input == __null |
General Analysis |
MediaClientNode.cpp:684 |
High |
V522 |
Dereferencing of the null pointer 'buffer' might take place. |
General Analysis |
MediaClientNode.cpp:21 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fStartTime. |
General Analysis |
MediaConnection.cpp:15 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fConnected, fPadding. |
General Analysis |
SimpleMediaClient.cpp:116 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBufferSize. |
General Analysis |
FormatManager.cpp:202 |
High |
V547 |
Expression 'format.u.encoded_audio.encoding == 0' is always true. |
General Analysis |
FormatManager.cpp:214 |
High |
V547 |
Expression 'format.u.encoded_video.encoding == 0' is always true. |
General Analysis |
MediaDecoder.cpp:244 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBuffer. |
General Analysis |
MediaDecoder.cpp:251 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBuffer. |
General Analysis |
MediaDecoder.cpp:260 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBuffer. |
General Analysis |
MediaDefs.cpp:684 |
High |
V547 |
Expression 'format->encoding == 0' is always true. |
General Analysis |
MediaDefs.cpp:665 |
High |
V547 |
Expression 'format->encoding == 0' is always true. |
General Analysis |
MediaEncoder.cpp:291 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBufferSize. |
General Analysis |
MediaEncoder.cpp:282 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBufferSize. |
General Analysis |
MediaEncoder.cpp:273 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBufferSize. |
General Analysis |
MediaFormats.cpp:313 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: id. |
General Analysis |
MediaRecorder.cpp:343 |
High |
V522 |
Dereferencing of the null pointer 'input' might take place. |
General Analysis |
MediaRoster.cpp:1550 |
High |
V614 |
Uninitialized variable 'dummy' used. Consider checking the third actual argument of the 'write_port' function. |
General Analysis |
MediaRoster.cpp:2842 |
High |
V641 |
The size of the allocated memory buffer is not a multiple of the element size. |
General Analysis |
ParameterWeb.cpp:2034 |
High |
V595 |
The 'name' pointer was utilized before it was verified against nullptr. Check lines: 2034, 2035. |
General Analysis |
SoundFile.cpp:57 |
High |
V595 |
The 'fMediaFile' pointer was utilized before it was verified against nullptr. Check lines: 57, 59. |
General Analysis |
SoundPlayNode.cpp:32 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLatency, fInternalLatency, fStartTime. |
General Analysis |
TimeSource.cpp:446 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: _reserved_area, _reserved_bool_, _reserved_time_source_. |
General Analysis |
TimeSource.cpp:267 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: _reserved_area, _reserved_bool_, _reserved_time_source_. |
General Analysis |
MidiStore.cpp:26 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: time, ticks, tempo. |
General Analysis |
MidiSynth.cpp:22 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSongVariables, fPerformanceVariables, fMidiQueue. |
General Analysis |
MidiEndpoint.cpp:236 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fIsConsumer, _reserved. |
General Analysis |
AbstractSocket.cpp:37 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fIsBound. |
General Analysis |
NetworkDevice.cpp:784 |
High |
V773 |
The function was exited without releasing the 'listener' pointer. A memory leak is possible. |
General Analysis |
FetchFileJob.cpp:32 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSuccess, fBytes, fTotalBytes. |
General Analysis |
FetchFileJob.cpp:176 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSuccess, fBytes, fTotalBytes. |
General Analysis |
GlobalWritableFileInfo.cpp:15 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fIsDirectory. |
General Analysis |
PackageFileHeapReader.cpp:160 |
High |
V1028 |
Possible overflow. Consider casting operands of the 'chunkIndex + 1' operator to the 'uint64' type, not the result. |
General Analysis |
PackageFileHeapWriter.cpp:166 |
High |
V575 |
The null pointer is passed into 'free' function. Inspect the first argument. |
General Analysis |
PackageReaderImpl.cpp:306 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHeapOffset, fHeapSize. |
General Analysis |
PackageWriterImpl.cpp:441 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHeapOffset, fHeaderSize. |
General Analysis |
ReaderImplBase.cpp:763 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMinorFormatVersion, fCurrentMinorFormatVersion. |
General Analysis |
RepositoryReaderImpl.cpp:284 |
High |
V595 |
The 'contentHandler' pointer was utilized before it was verified against nullptr. Check lines: 284, 288. |
General Analysis |
RepositoryWriterImpl.cpp:96 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fPackageReader. |
General Analysis |
PackageDataReaderV1.cpp:70 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fOffset, fSize. |
General Analysis |
ReaderImplBaseV1.cpp:44 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: heapOffset, heapSize. |
General Analysis |
ReaderImplBaseV1.cpp:56 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: heapOffset, heapSize. |
General Analysis |
PackageInfoSet.cpp:34 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: hashNext. |
General Analysis |
RefreshRepositoryRequest.cpp:33 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fValidateChecksumJob. |
General Analysis |
UserSettingsFileInfo.cpp:15 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fIsDirectory. |
General Analysis |
JsonTextWriter.cpp:689 |
High |
V547 |
Expression 'write_result == ((int) 0)' is always true. |
General Analysis |
Variant.cpp:195 |
High |
V568 |
It's odd that 'sizeof()' operator evaluates the size of a pointer to a class, but not the size of the 'this->fReferenceable' class object. |
General Analysis |
AppFileInfo.cpp:1083 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
AppFileInfo.cpp:1043 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
AppFileInfo.cpp:597 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
AppFileInfo.cpp:721 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
Directory.cpp:399 |
High |
V654 |
The condition 'error == ((int) 0)' of loop is always true. |
General Analysis |
Directory.cpp:406 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
DiskDevice.cpp:352 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
MoveJob.cpp:22 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fOffset. |
General Analysis |
SetStringJob.cpp:16 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fJobType. |
General Analysis |
Database.cpp:646 |
High |
V547 |
Expression 'status == ((int) 0)' is always true. |
General Analysis |
database_support.cpp:223 |
High |
V773 |
The function was exited without releasing the 'icon8' pointer. A memory leak is possible. |
General Analysis |
DatabaseLocation.cpp:631 |
High |
V547 |
Expression 'result == ((int) 0)' is always true. |
General Analysis |
NodeInfo.cpp:347 |
High |
V547 |
Expression 'verb == B_OPEN' is always true. |
General Analysis |
PathMonitor.cpp:98 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashNext. |
General Analysis |
PathMonitor.cpp:690 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashNext. |
General Analysis |
PathMonitor.cpp:268 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashNext. |
General Analysis |
PathMonitor.cpp:1465 |
High |
V522 |
Dereferencing of the null pointer 'directory' might take place. |
General Analysis |
PathMonitor.cpp:350 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashNext. |
General Analysis |
QueryPredicate.cpp:497 |
High |
V595 |
The 'node' pointer was utilized before it was verified against nullptr. Check lines: 497, 504. |
General Analysis |
Resources.cpp:662 |
High |
V595 |
The 'item' pointer was utilized before it was verified against nullptr. Check lines: 662, 664. |
General Analysis |
ResourceStrings.cpp:361 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: _reserved1, _reserved2. |
General Analysis |
Err.cpp:65 |
High |
V611 |
The memory was allocated using 'new T[]' operator but was released using the 'delete' operator. Consider inspecting this code. It's probably better to use 'delete [] fMsg;'. |
General Analysis |
Archivable.cpp:609 |
High |
V773 |
Visibility scope of the 'manager' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Archivable.cpp:301 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: _reserved. |
General Analysis |
CompressionAlgorithm.cpp:186 |
High |
V547 |
Expression 'fBufferSize > 0' is always false. |
General Analysis |
Job.cpp:57 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fResult. |
General Analysis |
ZlibCompressionAlgorithm.cpp:206 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fStream. |
General Analysis |
ZstdCompressionAlgorithm.cpp:199 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: inBuffer, outBuffer. |
General Analysis |
AutoMounterSettings.cpp:157 |
High |
V773 |
Visibility scope of the 'autoMountBox' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
AutoMounterSettings.cpp:157 |
High |
V773 |
Visibility scope of the 'bootMountBox' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
AutoMounterSettings.cpp:290 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ContainerWindow.cpp:4309 |
High |
V654 |
The condition 'err == ((int) 0)' of loop is always true. |
General Analysis |
ContainerWindow.cpp:339 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
ContainerWindow.cpp:3353 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FindPanel.cpp:327 |
High |
V595 |
The 'fFile' pointer was utilized before it was verified against nullptr. Check lines: 327, 333. |
General Analysis |
FindPanel.cpp:2096 |
High |
V773 |
The function was exited without releasing the 'removeButton' pointer. A memory leak is possible. |
General Analysis |
FindPanel.cpp:2096 |
High |
V773 |
The function was exited without releasing the 'addButton' pointer. A memory leak is possible. |
General Analysis |
FindPanel.cpp:1407 |
High |
V517 |
The use of 'if (A) {...} else if (A) {...}' pattern was detected. There is a probability of logical error presence. Check lines: 1407, 1410. |
General Analysis |
FSClipboard.cpp:490 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
FSClipboard.cpp:504 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
FSUndoRedo.h:92 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''U\0\0\0''. |
General Analysis |
FSUndoRedo.h:85 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''U\0\0\0''. |
General Analysis |
FSUndoRedo.h:99 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''T\0\0\0''. |
General Analysis |
FSUtils.cpp:744 |
High |
V547 |
Expression 'action == kMove' is always true. |
General Analysis |
FSUtils.cpp:697 |
High |
V547 |
Expression 'action == kMove' is always true. |
General Analysis |
FSUtils.cpp:656 |
High |
V547 |
Expression 'action == kMove' is always true. |
General Analysis |
FSUtils.cpp:678 |
High |
V547 |
Expression 'action == kMove' is always true. |
General Analysis |
FSUtils.cpp:2175 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:758 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:3409 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
FSUtils.cpp:3634 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:2980 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
FSUtils.cpp:371 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:2946 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:3714 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
FSUtils.cpp:2930 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:2904 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
FSUtils.cpp:2286 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
FSUtils.cpp:3720 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
FSUtils.cpp:3403 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
FSUtils.cpp:2265 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:3168 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:2069 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:2192 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:784 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:810 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:860 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:1798 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:2146 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:2134 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:2247 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:1978 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
FSUtils.cpp:1951 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
FSUtils.cpp:1811 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
IconCache.cpp:773 |
High |
V763 |
Parameter 'entry' is always rewritten in function body before being used. |
General Analysis |
IconCache.cpp:864 |
High |
V763 |
Parameter 'entry' is always rewritten in function body before being used. |
General Analysis |
IconCache.cpp:832 |
High |
V763 |
Parameter 'entry' is always rewritten in function body before being used. |
General Analysis |
InfoWindow.cpp:2018 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
InfoWindow.cpp:1994 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Model.cpp:107 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fStatBuf. |
General Analysis |
NodeWalker.cpp:395 |
High |
V522 |
Dereferencing of the null pointer 'source' might take place. The null pointer is passed into 'build_dirent' function. Inspect the first argument. Check lines: 395, 451. |
General Analysis |
OpenWithWindow.cpp:1050 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHaveCommonPreferredApp. |
General Analysis |
OpenWithWindow.cpp:1031 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHaveCommonPreferredApp. |
General Analysis |
OpenWithWindow.cpp:734 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
OpenWithWindow.cpp:715 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PoseView.cpp:8408 |
High |
V595 |
The 'ContainerWindow()' pointer was utilized before it was verified against nullptr. Check lines: 8408, 8427. |
General Analysis |
PoseView.cpp:5074 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PoseView.cpp:5851 |
High |
V590 |
Consider inspecting this expression. The expression is excessive or contains a misprint. |
General Analysis |
PoseView.cpp:2729 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PoseView.cpp:8594 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PoseView.cpp:9677 |
High |
V595 |
The 'targetPose' pointer was utilized before it was verified against nullptr. Check lines: 9677, 9683. |
General Analysis |
PoseView.cpp:8577 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PoseView.cpp:4842 |
High |
V614 |
Uninitialized variable 'tmp' used. Consider checking the fourth actual argument of the 'WriteAttr' function. |
General Analysis |
PoseView.cpp:4782 |
High |
V614 |
Uninitialized variable 'tmp' used. Consider checking the fourth actual argument of the 'WriteAttr' function. |
General Analysis |
PoseView.cpp:6222 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PoseView.cpp:6171 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PoseView.cpp:5096 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PoseView.cpp:5085 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PoseView.cpp:4861 |
High |
V595 |
The 'poseView' pointer was utilized before it was verified against nullptr. Check lines: 4861, 4884. |
General Analysis |
PoseView.cpp:6528 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PoseView.cpp:5108 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
SettingsHandler.cpp:185 |
High |
V739 |
EOF should not be compared with a value of the 'char' type. The 'ch' should be of the 'int' type. |
General Analysis |
TextWidget.cpp:69 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fParams. |
General Analysis |
Tracker.cpp:1714 |
High |
V590 |
Consider inspecting this expression. The expression is excessive or contains a misprint. |
General Analysis |
Tracker.cpp:828 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
TrackerInitialState.cpp:749 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
TrackerSettings.cpp:154 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fUseCounter. |
General Analysis |
TrackerSettings.cpp:123 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fUseCounter. |
General Analysis |
WidgetAttributeText.cpp:974 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
WidgetAttributeText.cpp:1762 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
WidgetAttributeText.cpp:1871 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
WidgetAttributeText.cpp:837 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
WidgetAttributeText.cpp:1725 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
WidgetAttributeText.cpp:1266 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fValue. |
General Analysis |
WidgetAttributeText.cpp:1734 |
High |
V1028 |
Possible overflow. Consider casting operands of the 'textView->TextLength() + 1' operator to the 'size_t' type, not the result. |
General Analysis |
TranslatorRoster.cpp:884 |
High |
V774 |
The 'self' pointer was used after the memory was released. |
General Analysis |
agg_gsv_text.cpp:484 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_indices, m_glyphs, m_bglyph, m_eglyph, m_w, m_h. |
General Analysis |
agg_rounded_rect.cpp:27 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_status. |
General Analysis |
agg_vcgen_bspline.cpp:22 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_cur_abscissa, m_max_abscissa. |
General Analysis |
agg_vcgen_contour.cpp:27 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_out_vertex. |
General Analysis |
agg_vcgen_dash.cpp:28 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_dashes, m_curr_rest, m_v1, m_v2. |
General Analysis |
agg_vcgen_smooth_poly1.cpp:26 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_ctrl1_x, m_ctrl1_y, m_ctrl2_x, m_ctrl2_y. |
General Analysis |
agg_vcgen_stroke.cpp:27 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_prev_status. |
General Analysis |
ALMLayout.cpp:247 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fRowColumnManager, _reserved. |
General Analysis |
ALMLayout.cpp:1151 |
High |
V614 |
Potentially uninitialized pointer 'bottom' used. Consider checking the fifth actual argument of the '_Init' function. |
General Analysis |
ALMLayout.cpp:1151 |
High |
V614 |
Potentially uninitialized pointer 'top' used. Consider checking the third actual argument of the '_Init' function. |
General Analysis |
ALMLayout.cpp:1151 |
High |
V614 |
Potentially uninitialized pointer 'right' used. Consider checking the fourth actual argument of the '_Init' function. |
General Analysis |
SharedSolver.cpp:84 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMinResult, fMaxResult, fPreferredResult, fLayoutResult. |
General Analysis |
SharedSolver.cpp:96 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMinResult, fMaxResult, fPreferredResult, fLayoutResult. |
General Analysis |
getpass.c:41 |
High |
V1010 |
Unchecked tainted data is used in index: 'length'. |
General Analysis |
iflib.c:6292 |
High |
V614 |
Potentially uninitialized pointer 'ndesc' used. |
General Analysis |
iflib.c:5873 |
High |
V614 |
Potentially uninitialized pointer 'tqg' used. Consider checking the sixth actual argument of the 'iflib_irq_set_affinity' function. |
General Analysis |
iflib.c:5871 |
High |
V614 |
Potentially uninitialized pointer 'q' used. |
General Analysis |
iflib.c:5871 |
High |
V614 |
Potentially uninitialized pointer 'fn' used. |
General Analysis |
iflib.c:5871 |
High |
V614 |
Potentially uninitialized pointer 'gtask' used. |
General Analysis |
iflib.c:5820 |
High |
V614 |
Potentially uninitialized pointer 'intr_fast' used. Consider checking the fourth actual argument of the '_iflib_irq_alloc' function. |
General Analysis |
iflib.c:5817 |
High |
V614 |
Potentially uninitialized pointer 'q' used. |
General Analysis |
iflib.c:5816 |
High |
V614 |
Potentially uninitialized pointer 'gtask' used. |
General Analysis |
iflib.c:3518 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
iflib.c:3518 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'freebsd_printf' function. The intmax_t/uintmax_t type argument is expected. |
General Analysis |
subr_gtaskqueue.c:459 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:470 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:600 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:602 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:607 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:435 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:240 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:395 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:254 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:258 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:263 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:351 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:353 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:360 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:473 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:238 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:252 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:220 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:457 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:364 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:437 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:223 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:589 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:591 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:390 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:575 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
subr_gtaskqueue.c:191 |
High |
V523 |
The 'then' statement is equivalent to the 'else' statement. |
General Analysis |
driver.c:240 |
High |
V729 |
Function body contains the 'err7' label that is not used by any 'goto' statements. |
General Analysis |
fbsd_busdma_x86.c:304 |
High |
V629 |
Consider inspecting the '(bz->total_bpages) << 12' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
if.c:1101 |
High |
V784 |
The size of the bit mask is less than the size of the first operand. This will cause the loss of higher bits. |
General Analysis |
if.c:542 |
High |
V512 |
A call of the 'memcpy' function will lead to the 'address' buffer becoming out of range. |
General Analysis |
taskqueue.c:363 |
High |
V614 |
Uninitialized variable 'status' used. Consider checking the third actual argument of the 'taskqueue_enqueue_locked' function. |
General Analysis |
unit.cpp:108 |
High |
V547 |
Expression 'slotIndex >= 0' is always true. Unsigned type value is always >= 0. |
General Analysis |
ieee80211_adhoc.c:689 |
High |
V634 |
The priority of the '*' operation is higher than that of the '<<' operation. It's possible that parentheses should be used in the expression. |
General Analysis |
ieee80211_crypto_ccmp.c:381 |
High |
V512 |
A call of the 'memcpy' function will lead to the 'wh->i_addr1' buffer becoming out of range. |
General Analysis |
ieee80211_hostap.c:1728 |
High |
V634 |
The priority of the '*' operation is higher than that of the '<<' operation. It's possible that parentheses should be used in the expression. |
General Analysis |
ieee80211_ioctl.c:2574 |
High |
V1008 |
Consider inspecting the 'for' operator. No more than one iteration of the loop will be performed. |
General Analysis |
ieee80211_ioctl.c:2615 |
High |
V1008 |
Consider inspecting the 'for' operator. No more than one iteration of the loop will be performed. |
General Analysis |
ieee80211_ioctl.c:2557 |
High |
V547 |
Expression 'sr->sr_duration < 1' is always false. |
General Analysis |
ieee80211_output.c:842 |
High |
V557 |
Array overrun is possible. The 'ieee80211_send_setup' function processes value '16'. Inspect the fourth argument. Check lines: 842, 3026. |
General Analysis |
ieee80211_output.c:842 |
High |
V557 |
Array overrun is possible. The 'ieee80211_send_setup' function processes value '16'. Inspect the fourth argument. Check lines: 842, 1027. |
General Analysis |
ieee80211_output.c:842 |
High |
V557 |
Array overrun is possible. The 'ieee80211_send_setup' function processes value '16'. Inspect the fourth argument. Check lines: 842, 911. |
General Analysis |
ieee80211_output.c:842 |
High |
V557 |
Array overrun is possible. The 'ieee80211_send_setup' function processes value '16'. Inspect the fourth argument. Check lines: 842, 2368. |
General Analysis |
ieee80211_output.c:1022 |
High |
V616 |
The 'tid' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
ieee80211_output.c:842 |
High |
V781 |
The value of the 'tid' variable is checked after it was used. Perhaps there is a mistake in program logic. Check lines: 842, 843. |
General Analysis |
ieee80211_phy.c:405 |
High |
V614 |
Potentially uninitialized pointer 'rt' used. |
General Analysis |
ieee80211_scan.c:297 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'freebsd_printf' function. The memsize type argument is expected. |
General Analysis |
ieee80211_scan.c:297 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'freebsd_printf' function. The memsize type argument is expected. |
General Analysis |
glutGameMode.cpp:22 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fOriginalMode, fCurrentMode. |
General Analysis |
glutMenu.h:69 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: win. |
General Analysis |
xattr.cpp:57 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'sprintf' function. The memsize type argument is expected. |
General Analysis |
VectorPath.cpp:1073 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
VectorPath.cpp:1071 |
High |
V630 |
The 'realloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
cp932.h:152 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
cp932.h:140 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
euc_jp.h:65 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
euc_jp.h:135 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
hz.h:105 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_cn.h:136 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_cn.h:190 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_cnext.h:252 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_cnext.h:308 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp.h:130 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp.h:85 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp.h:95 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp.h:151 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp1.h:97 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp1.h:154 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp1.h:107 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp1.h:175 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp2.h:619 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp2.h:167 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp2.h:213 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp2.h:186 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp2.h:199 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp2.h:458 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp2.h:434 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp2.h:486 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp2.h:403 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp3.h:471 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp3.h:146 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp3.h:125 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp3.h:135 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp3.h:364 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_jp3.h:342 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_kr.h:145 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
iso2022_kr.h:101 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
isoir165.h:146 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
java.h:128 |
High |
V547 |
Expression 'i < 10' is always false. |
General Analysis |
java.h:122 |
High |
V547 |
Expression 'i < 10' is always false. |
General Analysis |
sjis.h:92 |
High |
V547 |
Expression 'ret != 1' is always false. |
General Analysis |
ActiveSetSolver.cpp:352 |
High |
V654 |
The condition '!done' of loop is always true. |
General Analysis |
m_apm_lc.h:230 |
High |
V1040 |
Possible typo in the spelling of a pre-defined macro name. The '__MINGW_H' macro is similar to '__MINGW__'. |
General Analysis |
AddPrinterDlg.cpp:36 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fProtocolClassList, fDescription. |
General Analysis |
GraphicsDriver.cpp:703 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
JobSetupDlg.cpp:449 |
High |
V773 |
Visibility scope of the 'pagesPerSheet' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
JobSetupDlg.cpp:449 |
High |
V773 |
Visibility scope of the 'paperSourceMenufield' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
JobSetupDlg.cpp:137 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fDitherMenuField, fHalftoneBox, fPreview. |
General Analysis |
JobSetupDlg.cpp:449 |
High |
V773 |
Visibility scope of the 'colorMenuField' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MarginView.cpp:153 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTop, fBottom, fLeft, fRight, fPage, fPageSize. |
General Analysis |
PageSetupDlg.cpp:224 |
High |
V773 |
Visibility scope of the 'resolution' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PageSetupDlg.cpp:224 |
High |
V773 |
Visibility scope of the 'orientation' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PageSetupDlg.cpp:224 |
High |
V773 |
Visibility scope of the 'paperSize' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PageSetupDlg.cpp:349 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFilter. |
General Analysis |
PrinterDriver.cpp:163 |
High |
V773 |
The function was exited without releasing the 'preview' pointer. A memory leak is possible. |
General Analysis |
PrinterDriver.cpp:99 |
High |
V773 |
The function was exited without releasing the 'dialog' pointer. A memory leak is possible. |
General Analysis |
syn-att.c:195 |
High |
V547 |
Expression 'size == 8' is always false. |
General Analysis |
syn-att.c:197 |
High |
V547 |
Expression 'size == 16' is always false. |
General Analysis |
syn-att.c:199 |
High |
V547 |
Expression 'size == 64' is always false. |
General Analysis |
udis86.c:47 |
High |
V1031 |
The 'memset' function is not declared. Passing data to or from this function can be affected. |
General Analysis |
pidfile.c:190 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'snprintf' function. The memsize type argument is expected. |
General Analysis |
prim_ops.c:1623 |
High |
V547 |
Expression 'cnt >= 8' is always false. |
General Analysis |
prim_ops.c:1666 |
High |
V547 |
Expression 'cnt >= 16' is always false. |
General Analysis |
prim_ops.c:983 |
High |
V610 |
Undefined behavior. Check the shift operator '<<'. The right operand ('cnt' = [1..32]) is greater than or equal to the length in bits of the promoted left operand. |
General Analysis |
prim_ops.c:985 |
High |
V610 |
Undefined behavior. Check the shift operator '>>'. The right operand ('(33 - cnt)' = [1..32]) is greater than or equal to the length in bits of the promoted left operand. |
General Analysis |
prim_ops.c:1709 |
High |
V547 |
Expression 'cnt >= 32' is always false. |
General Analysis |
prim_ops.c:1133 |
High |
V610 |
Undefined behavior. Check the shift operator '>>'. The right operand ('cnt' = [1..32]) is greater than or equal to the length in bits of the promoted left operand. |
General Analysis |
AntialiasingSettingsView.cpp:235 |
High |
V773 |
Visibility scope of the 'message' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
AntialiasingSettingsView.cpp:213 |
High |
V773 |
Visibility scope of the 'message' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ColorPreview.cpp:126 |
High |
V579 |
The AddData function receives the pointer and its size as arguments. It is possibly a mistake. Inspect the fourth argument. |
General Analysis |
ColorPreview.cpp:127 |
High |
V568 |
It's odd that 'sizeof()' operator evaluates the size of a pointer to a class, but not the size of the 'color' class object. |
General Analysis |
FakeScrollBar.cpp:31 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fKnobStyle. |
General Analysis |
FontView.cpp:61 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fRunner. |
General Analysis |
BackgroundsView.cpp:245 |
High |
V773 |
Visibility scope of the 'imageMenuField' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
BackgroundsView.cpp:245 |
High |
V773 |
Visibility scope of the 'placementMenuField' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
BackgroundsView.cpp:665 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
BluetoothMain.cpp:21 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fWindow. |
General Analysis |
BluetoothMain.cpp:61 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
BluetoothSettingsView.cpp:233 |
High |
V773 |
Visibility scope of the 'message' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
BluetoothSettingsView.cpp:287 |
High |
V773 |
Visibility scope of the 'message' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DeviceListItem.cpp:20 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fRSSI. |
General Analysis |
DataTranslations.cpp:149 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DataTranslations.cpp:160 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DataTranslations.cpp:90 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DataTranslations.cpp:58 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DataTranslationsWindow.cpp:349 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ApplicationTypeWindow.cpp:1079 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
AttributeListView.cpp:107 |
High |
V512 |
A call of the 'snprintf' function will lead to overflow of the buffer 'buffer + 6'. |
General Analysis |
AttributeWindow.cpp:269 |
High |
V773 |
Visibility scope of the 'typeMenuField' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
FileTypes.cpp:492 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
IconView.cpp:520 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSource. |
General Analysis |
IconView.cpp:1226 |
High |
V773 |
Visibility scope of the 'icon' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
IconView.cpp:909 |
High |
V773 |
Visibility scope of the 'icon' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
IconView.cpp:850 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PreferredAppMenu.cpp:298 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PreferredAppMenu.cpp:204 |
High |
V678 |
An object is used as an argument to its own method. Consider checking the first actual argument of the 'SetMarked' function. |
General Analysis |
Keyboard.cpp:57 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
KeyboardLayout.cpp:360 |
High |
V630 |
The 'realloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
KeyboardLayoutView.cpp:83 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fOffscreenView, fDragModifiers, fBaseFontHeight, fBaseFontSize, fFactor, fGap. |
General Analysis |
KeyboardLayoutView.cpp:231 |
High |
V773 |
Visibility scope of the 'alternativesPopUp' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
KeyboardLayoutView.cpp:333 |
High |
V773 |
Visibility scope of the 'modifiersPopUp' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
KeymapWindow.cpp:679 |
High |
V773 |
Visibility scope of the 'message' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
LocaleWindow.cpp:161 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
AutoConfigView.cpp:474 |
High |
V792 |
The '_HasMarkedChanged' 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 '||'. |
General Analysis |
AutoConfigView.cpp:472 |
High |
V792 |
The '_HasMarkedChanged' 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 '||'. |
General Analysis |
AutoConfigView.cpp:473 |
High |
V792 |
The '_HasMarkedChanged' 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 '||'. |
General Analysis |
AutoConfigWindow.cpp:94 |
High |
V773 |
The function was exited without releasing the 'invalidMailAlert' pointer. A memory leak is possible. |
General Analysis |
ConfigWindow.cpp:755 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
FilterConfigView.cpp:40 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLastDragTarget, fDragIndex. |
General Analysis |
Media.cpp:45 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the signed long type is expected. |
General Analysis |
Media.cpp:45 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'sscanf' function. A pointer to the signed long type is expected. |
General Analysis |
Media.cpp:45 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'sscanf' function. A pointer to the signed long type is expected. |
General Analysis |
Media.cpp:45 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'sscanf' function. A pointer to the signed long type is expected. |
General Analysis |
MediaWindow.cpp:445 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
Mouse.cpp:41 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MouseView.cpp:91 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fDigitBaseline, fDigitHeight. |
General Analysis |
SettingsView.cpp:157 |
High |
V773 |
Visibility scope of the 'message' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
SettingsView.cpp:135 |
High |
V773 |
Visibility scope of the 'message' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
SettingsView.cpp:221 |
High |
V773 |
Visibility scope of the 'focusFollowsMouseField' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
NetworkWindow.cpp:617 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
GeneralView.cpp:129 |
High |
V773 |
Visibility scope of the 'message' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Notifications.cpp:26 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fWindow. |
General Analysis |
NotificationsView.cpp:226 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
NotificationsView.cpp:203 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PrefletWin.cpp:124 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
AddPrinterDialog.cpp:285 |
High |
V773 |
Visibility scope of the 'transportMenuField' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
AddPrinterDialog.cpp:285 |
High |
V773 |
Visibility scope of the 'printerMenuField' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
AddRepoWindow.cpp:96 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
RepositoriesWindow.cpp:117 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
TaskTimer.cpp:168 |
High |
V773 |
Visibility scope of the 'newAlert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MonitorView.cpp:28 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBackgroundColor. |
General Analysis |
ScreenApplication.cpp:45 |
High |
V773 |
Visibility scope of the 'aboutAlert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ScreenMode.cpp:505 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''QDS\0''. |
General Analysis |
ScreenMode.cpp:548 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''VSC\0''. |
General Analysis |
ScreenMode.cpp:551 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''ZCM\0''. |
General Analysis |
ScreenMode.cpp:545 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''VIZ\0''. |
General Analysis |
ScreenMode.cpp:542 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''UNM\0''. |
General Analysis |
ScreenMode.cpp:539 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''TSB\0''. |
General Analysis |
ScreenMode.cpp:538 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''TOS\0''. |
General Analysis |
ScreenMode.cpp:508 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''REL\0''. |
General Analysis |
ScreenMode.cpp:444 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''HEI\0''. |
General Analysis |
ScreenMode.cpp:447 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''HIT\0''. |
General Analysis |
ScreenMode.cpp:448 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''HTC\0''. |
General Analysis |
ScreenMode.cpp:451 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''HSL\0''. |
General Analysis |
ScreenMode.cpp:454 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''HWP\0''. |
General Analysis |
ScreenMode.cpp:457 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''ICL\0''. |
General Analysis |
ScreenMode.cpp:520 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''SNI\0''. |
General Analysis |
ScreenMode.cpp:517 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''SHP\0''. |
General Analysis |
ScreenMode.cpp:514 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''SDI\0''. |
General Analysis |
ScreenMode.cpp:511 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''SAM\0''. |
General Analysis |
ScreenMode.cpp:460 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''IVM\0''. |
General Analysis |
ScreenMode.cpp:443 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''HIQ\0''. |
General Analysis |
ScreenMode.cpp:463 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''LEN\0''. |
General Analysis |
ScreenMode.cpp:469 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''LTN\0''. |
General Analysis |
ScreenMode.cpp:472 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''MAX\0''. |
General Analysis |
ScreenMode.cpp:475 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''MED\0''. |
General Analysis |
ScreenMode.cpp:478 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''MEI\0''. |
General Analysis |
ScreenMode.cpp:481 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''MEL\0''. |
General Analysis |
ScreenMode.cpp:484 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''MIR\0''. |
General Analysis |
ScreenMode.cpp:487 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''MTC\0''. |
General Analysis |
ScreenMode.cpp:490 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''NAN\0''. |
General Analysis |
ScreenMode.cpp:493 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''NOK\0''. |
General Analysis |
ScreenMode.cpp:496 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''OQI\0''. |
General Analysis |
ScreenMode.cpp:499 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''PHL\0''. |
General Analysis |
ScreenMode.cpp:502 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''PTS\0''. |
General Analysis |
ScreenMode.cpp:466 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''LPL\0''. |
General Analysis |
ScreenMode.cpp:440 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''GWY\0''. |
General Analysis |
ScreenMode.cpp:384 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''ACR\0''. |
General Analysis |
ScreenMode.cpp:434 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''FUS\0''. |
General Analysis |
ScreenMode.cpp:535 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''TAT\0''. |
General Analysis |
ScreenMode.cpp:532 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''SUN\0''. |
General Analysis |
ScreenMode.cpp:529 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''SRC\0''. |
General Analysis |
ScreenMode.cpp:526 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''SPT\0''. |
General Analysis |
ScreenMode.cpp:380 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''ADI\0''. |
General Analysis |
ScreenMode.cpp:383 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''AAC\0''. |
General Analysis |
ScreenMode.cpp:523 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''SNY\0''. |
General Analysis |
ScreenMode.cpp:385 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''API\0''. |
General Analysis |
ScreenMode.cpp:388 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''ACT\0''. |
General Analysis |
ScreenMode.cpp:391 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''APP\0''. |
General Analysis |
ScreenMode.cpp:394 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''AUO\0''. |
General Analysis |
ScreenMode.cpp:397 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''BNQ\0''. |
General Analysis |
ScreenMode.cpp:437 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''GSM\0''. |
General Analysis |
ScreenMode.cpp:403 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''CPQ\0''. |
General Analysis |
ScreenMode.cpp:406 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''DEL\0''. |
General Analysis |
ScreenMode.cpp:400 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''CPL\0''. |
General Analysis |
ScreenMode.cpp:412 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''DWE\0''. |
General Analysis |
ScreenMode.cpp:415 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''ECS\0''. |
General Analysis |
ScreenMode.cpp:418 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''ELS\0''. |
General Analysis |
ScreenMode.cpp:421 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''EMA\0''. |
General Analysis |
ScreenMode.cpp:424 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''EIZ\0''. |
General Analysis |
ScreenMode.cpp:409 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''DPC\0''. |
General Analysis |
ScreenMode.cpp:425 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''ENC\0''. |
General Analysis |
ScreenMode.cpp:428 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''EPI\0''. |
General Analysis |
ScreenMode.cpp:431 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''FCM\0''. |
General Analysis |
ScreenWindow.cpp:590 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ScreenWindow.cpp:1384 |
High |
V773 |
Visibility scope of the 'window' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ScreenWindow.cpp:1394 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ScreenWindow.cpp:741 |
High |
V595 |
The 'fOtherRefresh' pointer was utilized before it was verified against nullptr. Check lines: 741, 747. |
General Analysis |
PasswordWindow.cpp:164 |
High |
V575 |
The null pointer is passed into 'crypt' function. Inspect the second argument. |
General Analysis |
ScreenSaverWindow.cpp:1007 |
High |
V595 |
The 'modulesTab' pointer was utilized before it was verified against nullptr. Check lines: 1007, 1014. |
General Analysis |
ShortcutsWindow.cpp:286 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ShortcutsWindow.cpp:293 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ShortcutsWindow.cpp:621 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
HApp.cpp:52 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
HEventList.cpp:134 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
NetworkTimeView.cpp:425 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
Time.cpp:66 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
TouchpadPrefView.cpp:43 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fOldXScrollRange, fOldYScrollRange. |
General Analysis |
TouchpadPrefView.cpp:112 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
SettingsWindow.cpp:331 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
VirtualMemory.cpp:56 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
BitmapManager.cpp:51 |
High |
V501 |
There are identical sub-expressions to the left and to the right of the '-' operator: (addr_t) b - (addr_t) b |
General Analysis |
ClientMemoryAllocator.cpp:328 |
High |
V595 |
The 'fAllocator' pointer was utilized before it was verified against nullptr. Check lines: 328, 329. |
General Analysis |
Desktop.cpp:214 |
High |
V646 |
Consider inspecting the application's logic. It's possible that 'else' keyword is missing. |
General Analysis |
DesktopListener.cpp:324 |
High |
V792 |
The 'SetDecoratorSettings' 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 '||'. |
General Analysis |
AccelerantBuffer.cpp:12 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fDisplayMode, fFrameBufferConfig. |
General Analysis |
AccelerantHWInterface.cpp:100 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fAccGetPreferredDisplayMode, fAccGetMonitorInfo, fAccGetEDIDInfo, fFrameBufferConfig. |
General Analysis |
AccelerantHWInterface.cpp:263 |
High |
V773 |
The 'device' pointer was assigned values twice without releasing the memory. A memory leak is possible. |
General Analysis |
RemoteMessage.h:205 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCode. |
General Analysis |
agg_rasterizer_scanline_aa_subpix.h:45 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_scan_y. |
General Analysis |
agg_scanline_p_subpix.h:46 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_y. |
General Analysis |
agg_scanline_p_subpix_avrg_filtering.h:47 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_y. |
General Analysis |
agg_scanline_storage_subpix.h:472 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_dx. |
General Analysis |
agg_scanline_u_subpix.h:41 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_y. |
General Analysis |
agg_scanline_u_subpix_avrg_filtering.h:43 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: m_y. |
General Analysis |
BitmapPainter.cpp:33 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fScaleX, fScaleY. |
General Analysis |
Painter.cpp:184 |
High |
V670 |
The uninitialized class member 'fPatternHandler' is used to initialize the 'fInternal' member. Remember that members are initialized in the order of their declarations inside a class. |
General Analysis |
Painter.cpp:182 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fIdentityTransform. |
General Analysis |
FontEngine.cpp:416 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fPreciseAdvanceX, fPreciseAdvanceY. |
General Analysis |
FontEngine.cpp:482 |
High |
V616 |
The '(FT_RENDER_MODE_NORMAL)' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
FontStyle.cpp:60 |
High |
V616 |
The '(FT_RENDER_MODE_NORMAL)' named constant with the value of 0 is used in the bitwise operation. |
General Analysis |
PictureBoundingBoxPlayer.cpp:351 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
ServerBitmap.cpp:84 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fToken. |
General Analysis |
ServerBitmap.cpp:59 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fToken. |
General Analysis |
ServerPicture.cpp:362 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
ServerPicture.cpp:838 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
ServerWindow.cpp:3657 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
ServerWindow.cpp:3135 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
DeskbarReplicant.cpp:187 |
High |
V773 |
Visibility scope of the 'menu' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DeskbarReplicant.cpp:219 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
HCIControllerAccessor.cpp:8 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSocket. |
General Analysis |
DebugServer.cpp:389 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fTeamInfo. |
General Analysis |
DebugServer.cpp:888 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DebugServer.cpp:1307 |
High |
V614 |
Uninitialized variable 'error' used. |
General Analysis |
AddOnManager.cpp:124 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSafeMode. |
General Analysis |
KeyRequestWindow.cpp:67 |
High |
V773 |
The function was exited without releasing the 'controls' pointer. A memory leak is possible. |
General Analysis |
Job.cpp:24 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCondition. |
General Analysis |
Worker.cpp:139 |
High |
V773 |
Visibility scope of the 'worker' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
ErrorLogWindow.cpp:56 |
High |
V763 |
Parameter 'rect' is always rewritten in function body before being used. |
General Analysis |
ErrorLogWindow.cpp:24 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: scroll. |
General Analysis |
MailDaemonApplication.cpp:314 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
media_server.cpp:978 |
High |
V614 |
Uninitialized variable 'status' used. |
General Analysis |
MidiServerApp.cpp:87 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MidiServerApp.cpp:828 |
High |
V614 |
Uninitialized variable 'status' used. |
General Analysis |
AutoMounter.cpp:644 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
AutoMounter.cpp:1010 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
AutoMounter.cpp:629 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
AutoMounter.cpp:608 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DHCPClient.cpp:830 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'syslog' function. The memsize type argument is expected. |
General Analysis |
DHCPClient.cpp:835 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'syslog' function. The memsize type argument is expected. |
General Analysis |
DHCPClient.cpp:463 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'syslog' function. The memsize type argument is expected. |
General Analysis |
DHCPClient.cpp:840 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'syslog' function. The memsize type argument is expected. |
General Analysis |
DHCPClient.cpp:871 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'syslog' function. The memsize type argument is expected. |
General Analysis |
DHCPClient.cpp:474 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fStartTime, fRequestTime, fRenewalTime, fRebindingTime. |
General Analysis |
DHCPClient.cpp:101 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
NetServer.cpp:174 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
NetServer.cpp:1198 |
High |
V614 |
Uninitialized variable 'status' used. |
General Analysis |
NotificationServer.cpp:120 |
High |
V614 |
Uninitialized variable 'error' used. |
General Analysis |
NotificationServer.cpp:32 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fWindow. |
General Analysis |
NotificationView.cpp:62 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHeight. |
General Analysis |
NotificationWindow.cpp:406 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
DebugSupport.cpp:54 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
JobQueue.cpp:18 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMutex, fNewJobCondition. |
General Analysis |
Root.cpp:533 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
ConfigWindow.cpp:317 |
High |
V773 |
Visibility scope of the 'about' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PrintServerApp.cpp:406 |
High |
V773 |
The function was exited without releasing the 'alert' pointer. A memory leak is possible. |
General Analysis |
PrintServerApp.R5.cpp:107 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
PrintServerApp.R5.cpp:150 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
MessageRunnerManager.cpp:302 |
High |
V595 |
The 'info' pointer was utilized before it was verified against nullptr. Check lines: 302, 311. |
General Analysis |
TRoster.cpp:495 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
TRoster.cpp:686 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
TRoster.cpp:739 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
TRoster.cpp:1660 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
SyslogDaemon.cpp:89 |
High |
V773 |
Visibility scope of the 'alert' pointer was exited without releasing the memory. A memory leak is possible. |
General Analysis |
SyslogDaemon.cpp:34 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fDaemon, fPort. |
General Analysis |
amiga_ffs.h:180 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''DOS\3''. |
General Analysis |
amiga_ffs.h:178 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''DOS\1''. |
General Analysis |
amiga_ffs.h:179 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''DOS\2''. |
General Analysis |
amiga_ffs.h:19 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fSize. |
General Analysis |
amiga_ffs.h:177 |
High |
V1039 |
Character escape is used in multicharacter literal. This causes implementation-defined behavior. Inspect expression: ''DOS\0''. |
General Analysis |
amiga_ffs.h:21 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fData. |
General Analysis |
Stream.cpp:280 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Stream.cpp:283 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Stream.cpp:257 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Stream.cpp:261 |
High |
V629 |
Consider inspecting the expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Directory.cpp:464 |
High |
V629 |
Consider inspecting the 'fStream.FirstCluster() << 16' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
File.cpp:136 |
High |
V629 |
Consider inspecting the 'fStream.FirstCluster() << 16' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Volume.cpp:197 |
High |
V629 |
Consider inspecting the 'fDataStart << SectorShift()' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
Volume.cpp:30 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fMaxRootEntries. |
General Analysis |
TCP.cpp:189 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fRemoteAddress, fRemotePort, fAcknowledgeNumber, fNextSequence. |
General Analysis |
pager.cpp:153 |
High |
V576 |
Incorrect format. Consider checking the fourth actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
pager.cpp:153 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
pager.cpp:153 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
cpu.cpp:310 |
High |
V547 |
Expression 'channel == 2' is always false. |
General Analysis |
cpu.cpp:239 |
High |
V547 |
Expression 'channel == 2' is always false. |
General Analysis |
devices.cpp:571 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fIdentifier. |
General Analysis |
devices.cpp:886 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
devices.cpp:716 |
High |
V576 |
Potentially incorrect format string is passed to the 'dprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
smp.cpp:458 |
High |
V512 |
A call of the 'memset' function will lead to overflow of the buffer '(uint8 *) finalStack + 1 * 4096'. |
General Analysis |
video.cpp:648 |
High |
V763 |
Parameter 'menu' is always rewritten in function body before being used. |
General Analysis |
cpu.cpp:241 |
High |
V547 |
Expression 'channel == 2' is always true. |
General Analysis |
devices.cpp:297 |
High |
V773 |
The function was exited without releasing the 'savedDevicePath' pointer. A memory leak is possible. |
General Analysis |
devices.cpp:416 |
High |
V512 |
A call of the 'memcmp' function will lead to underflow of the buffer 'deviceHeader'. |
General Analysis |
video.cpp:264 |
High |
V763 |
Parameter 'menu' is always rewritten in function body before being used. |
General Analysis |
arch_cpu.cpp:818 |
High |
V547 |
Expression 'result == ((int) 0)' is always true. |
General Analysis |
arch_user_debugger.cpp:336 |
High |
V784 |
The size of the bit mask is less than the size of the first operand. This will cause the loss of higher bits. |
General Analysis |
irq_routing_table.cpp:239 |
High |
V773 |
The function was exited without releasing the 'link' pointer. A memory leak is possible. |
General Analysis |
msi.cpp:102 |
High |
V629 |
Consider inspecting the 'apic_id << 12' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
msi.cpp:70 |
High |
V629 |
Consider inspecting the 'sBootCPUAPICId << 12' expression. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. |
General Analysis |
X86PagingStructures.cpp:10 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: pgdir_phys. |
General Analysis |
X86VMTranslationMap.cpp:27 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fInvalidPages, fIsKernelMap. |
General Analysis |
block_cache.cpp:979 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next, id. |
General Analysis |
block_cache.cpp:1356 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: lock, busy_reading_condition, busy_writing_condition, condition_variable. |
General Analysis |
file_cache.cpp:119 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fBusyConditions, fAllocatingThread. |
General Analysis |
BreakpointManager.cpp:519 |
High |
V547 |
Expression 'bytesTransferred > 0' is always false. |
General Analysis |
BreakpointManager.cpp:29 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: splayNext. |
General Analysis |
debug.cpp:1341 |
High |
V641 |
The size of the allocated memory buffer is not a multiple of the element size. |
General Analysis |
debug_heap.cpp:99 |
High |
V717 |
It is suspicious to cast object of base class 'allocation_header' to derived class 'free_entry'. |
General Analysis |
debug_heap.cpp:208 |
High |
V717 |
It is suspicious to cast object of base class 'allocation_header' to derived class 'free_entry'. |
General Analysis |
debug_heap.cpp:203 |
High |
V717 |
It is suspicious to cast object of base class 'allocation_header' to derived class 'free_entry'. |
General Analysis |
debug_heap.cpp:200 |
High |
V717 |
It is suspicious to cast object of base class 'allocation_header' to derived class 'free_entry'. |
General Analysis |
debug_heap.cpp:199 |
High |
V717 |
It is suspicious to cast object of base class 'allocation_header' to derived class 'free_entry'. |
General Analysis |
debug_heap.cpp:179 |
High |
V717 |
It is suspicious to cast object of base class 'allocation_header' to derived class 'free_entry'. |
General Analysis |
debug_heap.cpp:174 |
High |
V717 |
It is suspicious to cast object of base class 'allocation_header' to derived class 'free_entry'. |
General Analysis |
debug_heap.cpp:192 |
High |
V717 |
It is suspicious to cast object of base class 'allocation_header' to derived class 'free_entry'. |
General Analysis |
debug_heap.cpp:191 |
High |
V717 |
It is suspicious to cast object of base class 'allocation_header' to derived class 'free_entry'. |
General Analysis |
debug_heap.cpp:187 |
High |
V717 |
It is suspicious to cast object of base class 'allocation_header' to derived class 'free_entry'. |
General Analysis |
debug_heap.cpp:180 |
High |
V717 |
It is suspicious to cast object of base class 'allocation_header' to derived class 'free_entry'. |
General Analysis |
system_profiler.cpp:249 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLock, fProfilingActive, fCPUData. |
General Analysis |
user_debugger.cpp:2269 |
High |
V547 |
Expression 'result == ((int) 0)' is always true. |
General Analysis |
IOCache.cpp:41 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fAreaBase, fMappingReservation. |
General Analysis |
IORequest.cpp:474 |
High |
V595 |
The 'fParent' pointer was utilized before it was verified against nullptr. Check lines: 474, 494. |
General Analysis |
IOSchedulerSimple.cpp:87 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFinisherLock, fAllocatedRequestOwnerCount, fIterationBandwidth, fMinOwnerBandwidth, fMaxOwnerBandwidth. |
General Analysis |
KDiskDeviceManager.cpp:708 |
High |
V547 |
Expression 'error == ((int) 0)' is always true. |
General Analysis |
KDiskSystem.cpp:29 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFlags. |
General Analysis |
DPC.cpp:70 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLock. |
General Analysis |
EntryCache.cpp:200 |
High |
V547 |
Expression 'entry->index == kEntryRemoved' is always false. |
General Analysis |
fifo.cpp:77 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLock. |
General Analysis |
rootfs.cpp:800 |
High |
V547 |
Expression 'nameLength < ((int) 0)' is always false. |
General Analysis |
socket.cpp:983 |
High |
V547 |
Expression 'message.msg_controllen < 0' is always false. Unsigned type value is never < 0. |
General Analysis |
vfs.cpp:2662 |
High |
V575 |
The 'memcpy' function processes '0' elements. Inspect the third argument. |
General Analysis |
vfs.cpp:5533 |
High |
V614 |
Potentially uninitialized pointer 'cookie' used. Consider checking the fourth actual argument of the 'get_new_fd' function. |
General Analysis |
vfs.cpp:5403 |
High |
V614 |
Potentially uninitialized pointer 'cookie' used. Consider checking the fourth actual argument of the 'get_new_fd' function. |
General Analysis |
heap.cpp:2485 |
High |
V575 |
The 'memalign' function processes '0' elements. Inspect the first argument. |
General Analysis |
lock.cpp:395 |
High |
V595 |
The 'waiter.thread' pointer was utilized before it was verified against nullptr. Check lines: 395, 399. |
General Analysis |
MessagingService.cpp:256 |
High |
V558 |
Function returns the pointer to temporary local object: & command. |
General Analysis |
MessagingService.cpp:263 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fServerTeam, fLockSem, fCounterSem. |
General Analysis |
port.cpp:925 |
High |
V522 |
Dereferencing of the null pointer 'port' might take place. |
General Analysis |
port.cpp:135 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: team_link, hash_link, id, name_hash_link. |
General Analysis |
realtime_sem.cpp:285 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashLink. |
General Analysis |
realtime_sem.cpp:373 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fNextPrivateSemID. |
General Analysis |
xsi_message_queue.cpp:322 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLink. |
General Analysis |
xsi_semaphore.cpp:576 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLink. |
General Analysis |
RunQueue.h:120 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fPriority. |
General Analysis |
scheduler_cpu.cpp:80 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCPUNumber, fCore, fSchedulerModeLock, fQueueLock. |
General Analysis |
scheduler_cpu.cpp:643 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fPackageID, fCoreLock. |
General Analysis |
scheduler_cpu.cpp:400 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fCoreID, fPackage, fCPULock, fQueueLock, fActiveTimeLock, fLoadLock. |
General Analysis |
sem.cpp:255 |
High |
V779 |
Unreachable code detected. It is possible that an error is present. |
General Analysis |
HashedObjectCache.cpp:48 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: lower_boundary. |
General Analysis |
MemoryManager.cpp:1122 |
High |
V595 |
The 'metaChunkList' pointer was utilized before it was verified against nullptr. Check lines: 1122, 1137. |
General Analysis |
MemoryManager.cpp:1059 |
High |
V595 |
The 'metaChunkList' pointer was utilized before it was verified against nullptr. Check lines: 1059, 1089. |
General Analysis |
ObjectCache.h:146 |
High |
V558 |
Function returns the pointer to temporary local object: & pointer. |
General Analysis |
SmallObjectCache.cpp:108 |
High |
V558 |
Function returns the pointer to temporary local object. |
General Analysis |
SmallObjectCache.cpp:24 |
High |
V558 |
Function returns the pointer to temporary local object: & pointer. |
General Analysis |
smp.cpp:1434 |
High |
V630 |
The 'malloc' function is used to allocate memory for an array of objects which are classes containing constructors. |
General Analysis |
team.cpp:988 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
UserTimer.cpp:493 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fRunningThreads, fAbsolute. |
General Analysis |
UserTimer.cpp:887 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fAbsolute. |
General Analysis |
kernel_cpp.cpp:215 |
High |
V575 |
The null pointer is passed into 'fputs' function. Inspect the second argument. |
General Analysis |
list.cpp:225 |
High |
V558 |
Function returns the pointer to temporary local object. |
General Analysis |
list.cpp:208 |
High |
V558 |
Function returns the pointer to temporary local object. |
General Analysis |
list.cpp:142 |
High |
V558 |
Function returns the pointer to temporary local object. |
General Analysis |
list.cpp:135 |
High |
V558 |
Function returns the pointer to temporary local object. |
General Analysis |
list.cpp:132 |
High |
V558 |
Function returns the pointer to temporary local object. |
General Analysis |
list.cpp:116 |
High |
V558 |
Function returns the pointer to temporary local object. |
General Analysis |
list.cpp:113 |
High |
V558 |
Function returns the pointer to temporary local object. |
General Analysis |
vm.cpp:2449 |
High |
V614 |
Potentially uninitialized pointer 'cache' used. Consider checking the first actual argument of the 'SetTo' function. |
General Analysis |
vm.cpp:2451 |
High |
V614 |
Potentially uninitialized pointer 'source' used. |
General Analysis |
vm_page.cpp:3080 |
High |
V611 |
The memory was allocated using 'new' operator but was released using the 'free' function. Consider inspecting operation logics behind the 'wrapperPool' variable. |
General Analysis |
vm_page.cpp:3081 |
High |
V611 |
The memory was allocated using 'new' operator but was released using the 'free' function. Consider inspecting operation logics behind the 'wrappers' variable. |
General Analysis |
VMAddressSpace.cpp:86 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fHashTableLink. |
General Analysis |
VMAddressSpaceLocking.cpp:560 |
High |
V595 |
The 'originalItems' pointer was utilized before it was verified against nullptr. Check lines: 560, 568. |
General Analysis |
VMAnonymousCache.cpp:385 |
High |
V773 |
The 'allocation' pointer was assigned values twice without releasing the memory. A memory leak is possible. |
General Analysis |
VMArea.cpp:29 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: id, fBase, fSize. |
General Analysis |
VMKernelAddressSpace.cpp:71 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFreeLists, fFreeListCount. |
General Analysis |
VMKernelArea.cpp:14 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fRange. |
General Analysis |
dst_api.c:916 |
High |
V597 |
The compiler could delete the 'memset' function call, which is used to flush 'in_buff' buffer. The memset_s() function should be used to erase the private data. |
General Analysis |
dst_api.c:685 |
High |
V597 |
The compiler could delete the 'memset' function call, which is used to flush 'key_st' object. The memset_s() function should be used to erase the private data. |
General Analysis |
dst_api.c:446 |
High |
V597 |
The compiler could delete the 'memset' function call, which is used to flush 'encoded_block' buffer. The memset_s() function should be used to erase the private data. |
General Analysis |
dst_api.c:1018 |
High |
V597 |
The compiler could delete the 'memset' function call, which is used to flush 'f_key' object. The memset_s() function should be used to erase the private data. |
General Analysis |
getnetnamadr.c:236 |
High |
V547 |
Expression 'class == ns_c_in' is always true. |
General Analysis |
ctl_srvr.c:280 |
High |
V510 |
The '(* ctx->logger)' function is not expected to receive class-type variable as seventh actual argument. |
General Analysis |
ev_connects.c:356 |
High |
V575 |
The 'read' function processes '0' elements. Inspect the third argument. |
General Analysis |
ev_connects.c:72 |
High |
V570 |
The '* (_errnop())' variable is assigned to itself. |
General Analysis |
ev_files.c:65 |
High |
V570 |
The '* (_errnop())' variable is assigned to itself. |
General Analysis |
logging.c:361 |
High |
V547 |
Expression 'strlen(lc->buffer) > (size_t) 20480' is always false. |
General Analysis |
ns_name.c:600 |
High |
V1028 |
Possible overflow. Consider casting operands of the 'n + 1' operator to the 'size_t' type, not the result. |
General Analysis |
ns_print.c:157 |
High |
V1028 |
Possible overflow. Consider casting operands of the 'x + len' operator to the 'size_t' type, not the result. |
General Analysis |
mtctxres.c:85 |
High |
V773 |
The function was exited without releasing the 'mt' pointer. A memory leak is possible. |
General Analysis |
res_debug.c:723 |
High |
V579 |
The __ns_format_ttl function receives the pointer and its size as arguments. It is possibly a mistake. Inspect the third argument. |
General Analysis |
res_init.c:801 |
High |
V547 |
Expression is always true. |
General Analysis |
res_init.c:678 |
High |
V512 |
A call of the 'memcpy' function will lead to underflow of the buffer 'rnd'. |
General Analysis |
res_init.c:787 |
High |
V547 |
Expression is always true. |
General Analysis |
ICUCollateData.cpp:119 |
High |
V595 |
The 'in' pointer was utilized before it was verified against nullptr. Check lines: 119, 127. |
General Analysis |
ICULocaleBackend.cpp:30 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fLocaleDescription, fLocaleConv, fLCTimeInfo, fPosixLanginfo. |
General Analysis |
driver_settings.cpp:461 |
High |
V575 |
The null pointer is passed into 'free' function. Inspect the first argument. |
General Analysis |
dirent.c:107 |
High |
V641 |
The size of the allocated memory buffer is not a multiple of the element size. |
General Analysis |
dlfcn.c:110 |
High |
V575 |
The null pointer is passed into 'dlopen' function. Inspect the second argument. |
General Analysis |
LocaleBackend.cpp:28 |
High |
V575 |
The null pointer is passed into 'dlopen' function. Inspect the second argument. |
General Analysis |
malloc_debug_api.cpp:181 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the unsigned long type is expected. |
General Analysis |
malloc_debug_api.cpp:174 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'sscanf' function. A pointer to the unsigned long type is expected. |
General Analysis |
pthread_cancel.cpp:82 |
High |
V547 |
Expression '(oldFlags & 0) != 0' is always false. |
General Analysis |
pthread_key.cpp:55 |
High |
V654 |
The condition 'specificSequence != sequence' of loop is always false. |
General Analysis |
pthread_rwlock.cpp:27 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: status. |
General Analysis |
sigwaitinfo.cpp:13 |
High |
V575 |
The null pointer is passed into 'sigtimedwait' function. Inspect the third argument. |
General Analysis |
merge.c:120 |
High |
V514 |
Dividing sizeof a pointer 'sizeof (u_char *)' by another value. There is a probability of logical error presence. |
General Analysis |
strtod.c:545 |
High |
V564 |
The '&' operator is applied to bool type value. You've probably forgotten to include parentheses or intended to use the '&&' operator. |
General Analysis |
utimes.c:111 |
High |
V575 |
The null pointer is passed into 'utimensat' function. Inspect the second argument. |
General Analysis |
syslog.cpp:164 |
High |
V512 |
A call of the 'vsnprintf' function will lead to overflow of the buffer 'message.message'. |
General Analysis |
add_ons.h:44 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next. |
General Analysis |
elf_symbol_lookup.h:72 |
High |
V595 |
The 'fValuesResolved' pointer was utilized before it was verified against nullptr. Check lines: 72, 74. |
General Analysis |
elf_tls.h:62 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fGeneration. |
General Analysis |
OpenGLApp.cpp:17 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fWindow. |
General Analysis |
tcptester.cpp:241 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
command_checkfs.cpp:64 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
block_cache.cpp:471 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: lock. |
General Analysis |
block_cache.cpp:383 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: next, id. |
General Analysis |
block_cache.cpp:540 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
block_cache.cpp:700 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
block_cache.cpp:1568 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
block_cache.cpp:700 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
block_cache.cpp:724 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
block_cache.cpp:724 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
block_cache.cpp:782 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
block_cache.cpp:782 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
block_cache.cpp:900 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
block_cache.cpp:1568 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
block_cache.cpp:1615 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
block_cache.cpp:749 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
driver_settings.cpp:788 |
High |
V547 |
Expression 'bufferSize >= 0' is always true. Unsigned type value is always >= 0. |
General Analysis |
driver_settings.cpp:575 |
High |
V547 |
Expression '* _bufferSize >= 0' is always true. Unsigned type value is always >= 0. |
General Analysis |
driver_settings.cpp:427 |
High |
V575 |
The null pointer is passed into 'free' function. Inspect the first argument. |
General Analysis |
file_cache.cpp:260 |
High |
V576 |
Incorrect format. Consider checking the fifth actual argument of the 'fssh_snprintf' function. The memsize type argument is expected. |
General Analysis |
file_cache.cpp:252 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
fssh.cpp:770 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
fssh.cpp:774 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
fssh.cpp:760 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
fssh.cpp:411 |
High |
V576 |
Incorrect format. Consider checking the sixth actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
fssh.cpp:776 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
fssh.cpp:772 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
fssh.cpp:124 |
High |
V730 |
Not all members of a class are initialized inside the constructor. Consider inspecting: fFunction. |
General Analysis |
fssh.cpp:771 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
fssh.cpp:1143 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fprintf' function. The memsize type argument is expected. |
General Analysis |
fssh.cpp:777 |
High |
V576 |
Incorrect format. Consider checking the second actual argument of the 'printf' function. The memsize type argument is expected. |
General Analysis |
kernel_export.cpp:74 |
High |
V522 |
Dereferencing of the null pointer 'badAddress' might take place. |
General Analysis |
vfs.cpp:4955 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_dprintf' function. The memsize type argument is expected. |
General Analysis |
vfs.cpp:1900 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
vfs.cpp:1074 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
vfs.cpp:786 |
High |
V576 |
Incorrect format. Consider checking the third actual argument of the 'fssh_panic' function. The memsize type argument is expected. |
General Analysis |
gensyscallinfos.cpp:413 |
High |
V1022 |
An exception was thrown by pointer. Consider throwing it by value instead. |
General Analysis |
gensyscallinfos.cpp:347 |
High |
V1022 |
An exception was thrown by pointer. Consider throwing it by value instead. |
General Analysis |
gensyscallinfos.cpp:316 |
High |
V1022 |
An exception was thrown by pointer. Consider throwing it by value instead. |
General Analysis |
collectcatkeys.cpp:290 |
High |
V576 |
Potentially incorrect format string is passed to the 'fprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |
General Analysis |
DefaultCatalog.cpp:163 |
High |
V576 |
Potentially incorrect format string is passed to the 'fprintf' function. Prefix 'L' is not applicable to conversion specifier 'u'. |
General Analysis |
DefaultCatalog.cpp:154 |
High |
V576 |
Potentially incorrect format string is passed to the 'fprintf' function. Prefix 'L' is not applicable to conversion specifier 'd'. |