V6031. V5603. V2571.

V3145. The 'while' operator has empty body. Be advised that the size of the type 'long' varies between LLP64/LP64 data models. Function result is saved inside the 'byte' type variable. A bool type variable is incremented. InvalidClassException may occur during deserialization. What happens when we try to compile the class definition in following code snippet? V558. V1026. Moving an object in a return statement prevents copy elision. It is possible that a typo is present inside the expression. V659. V1059. Buffer size is not a multiple of element size. V2598. V5607. Temporary anonymous object is used. V778. A compatible declaration should be visible when an object or function with external linkage is defined. MISRA. The 'i' variable should probably be incremented instead of the 'n' variable. V595. V708. The expression is always false. A method can return default null value. Possible dereference of invalid iterator 'X'.

Consider checking the first actual argument of the 'Foo' method. AUTOSAR. Check lines: N1, N2. V1017. V2561. Don't use terminating functions in library code. V1016. Possible incorrect initialization of variable. The passed line may contain format specification. Identifiers that start with '__' or '_[A-Z]' are reserved. V802. Class destructor should not exit with an exception. Consider inspecting this expression.

V622. Possible exception when deserializing type.

V2573. Ignored InterruptedException could lead to delayed thread shutdown. V3023. Every 'switch' statement should contain non-empty switch-clauses. The 'continue' operator will terminate 'do { } while (FALSE)' loop because the condition is always false. AUTOSAR. V706. V1027. V537. AUTOSAR. Passing objects of incompatible types to the method of collection. V681. MISRA. V717. The expression is incorrect or it can be simplified. Incorrect comparison of BOOL type variable with TRUE. V3118. V3528. Destructor of base class should always be private. V729. V591. Consider inspecting 'X'. WPF: A class containing registered property does not correspond with a type that is passed as the ownerType.type. Probably the '+=' should be used here. By declaring it abstract using the virtual keyword. AUTOSAR. V3066. Suspicious operation of 'sizeof(X)/sizeof(T)' kind, where 'X' is of the 'class' type. V1043. Consider inspecting the loop expression. Constant expression evaluation should not result in an unsigned integer wrap-around. PVS-Studio . The standard signal handling functions should not be used. V828. Check for missing 'throw' keyword. > ? Possible exception when serializing type. Consider inspecting the expression. Line whose first token is '#' should be a valid preprocessing directive. Suspicious type conversion: HRESULT -> BOOL (BOOL -> HRESULT). V3018. V2521. > .. V3553. Subtraction, >, >=, <, <= should be applied only to pointers that address elements of the same array. V785. V762. Analysis of 'Makefile/Utility' type projects is not supported in this tool. V5301. It is suspicious that a char or string literal is added to a pointer.

V3140. V3541.

V2002. No more than one iteration of the loop will be performed. ( ), * , , PVS-Studio Microsoft MVP, , 2008 - 2022, Profesoras, profesores, estudiantes: The global namespace should only contain 'main', namespace declarations and 'extern "C"' declarations. The '+' operation is executed. Suspicious division. V2597. V3103. V2517. Expressions with pointer type should not be used in the '+', '-', '+=' and '-=' operations. V3094. Typedef names should be unique across all name spaces. Suspicious subexpression in a sequence of similar comparisons. AUTOSAR. V6026. Size of every element in X array is not equal to divisor. MISRA.

An object is used as an argument to its own method. Probably meant: *ptr = zero. MISRA. Consider creating a 'T' type object. The loop counter should not have floating-point type. Pointer to array is out of array bounds. MISRA. Unsafe synchronization on an object. A terminal null is present inside a string. > ? > ? AUTOSAR. The expression was implicitly cast from integer type to real type. > ? V3054. Operation is executed 3 or more times in a row. There is a probability of logical error presence. operators are used for accessing members of the same object. V3136. V816. Possible typo inside the string literal. The object was used after it was verified against null. Operands of the logical '&&' or the '||' operators, the '!' > - ? V776. V3164. V2588. Suspicious division. Consider inspecting the statement of '*pointer++' pattern. The method does not override another method from the base class. There should be no attempt to write to a stream that has been opened for reading. It is suspicious that variable is initialized through itself. V2544. There are two 'if' statements with identical conditional expressions. V3525. Defining an absolute path to the file or directory is considered a poor style. if want to delete the constructor of both the classes but the can't happen it should be delete only derived class object. Pointer was used before its check for nullptr. V745. Non-void function must return value. V3051. Pointer to an object of the class is cast to unrelated class. V5612. An excessive check can be simplified. V698. V2505. Verifying that a pointer value is not NULL is not required. V3549. V666. > ? WPF: writing and reading are performed on a different Dependency Properties. V521. The switch statement does not cover all values of the enum. Potentially tainted data is written into logs. Variables are initialized through the call to the same function. It's possible that the loop will be executed incorrectly or won't be executed at all. It will not compile because class body of Birds is not defined. AUTOSAR. V686. Consider inspecting conditional expression of the loop. A smart pointer may not destroy an object correctly. Function execution could be deferred. V637. V2557. Potentially unsafe double-checked locking. Consider utilizing 64-bit compiler if possible. The initial value of the index in the nested loop equals 'i'. It's probably an error or un-optimized code. It is possible that there is an error. OWASP. The 'continue' operator will terminate 'do { } while (false)' loop because the condition is always false. The left operand of integer division is less than the right one. V523. > ?

Consider replacing standard container with a different one. EOF should not be compared with a value of the 'char' type. An identifier with array type passed as a function argument should not decay to a pointer. Function 'Foo' writes/reads 'N' bytes. V578. It's better to use '= default;' syntax instead of empty body. There are identical sub-expressions to the left and to the right of the 'foo' operator. The 'switch' statement should have 'default' as the last label. V3544. V796. Consider inspecting the expression. Character escape is used in multicharacter literal. > ?

Consider pre-allocating it by calling reserve(N). This condition was already verified in previous line. > ? Operands of the logical '&&' or the '||' operators, the '!' MISRA. The condition (ptr - const_value) is only false if the value of a pointer equals a magic constant. Implicit conversion of the type of 'new' operator's argument to size_t type.

V3160. Using 'std::move' function's with const object disables move semantics. V2577. This expression can be simplified. It will be closed before the method exits. MISRA. V749. Possible null dereference. It is possible that an error is present. V621. V738. Initializer of a field marked by [ThreadStatic] attribute will be called once on the first accessing thread. Make sure the expression is correct. V3032. An exception handling block does not contain any code. V2587. The variable in the loop exit condition does not change its value between iterations. MISRA. Not all IDisposable members are properly disposed. V6073. Function exited without performing epilogue actions. V6045. This will cause the loss of the higher bits. More than N bits are required to store the value, but the expression evaluates to the T type which can only hold K bits. . Function call may lead to buffer overflow. AUTOSAR. Function receives suspicious argument. Consider inspecting the NN argument of the 'Foo' function. V583. V3096. A 32-bit variable is utilized as a reference to a pointer. V3530. Suspicious literal: '/r'. AUTOSAR. Inspect the Nth argument. OWASP. Initial and final values of the iterator are the same. > ? V6054. V598. V592. V1031. The expression contains a comma. Decreased performance.

V2595. V577. Anonymous function is used to unsubscribe from event. Consider synchronizing the field on all usages. Friend keyword can be used for a function in the public section of a class. > ? > ? AUTOSAR. It is more efficient to catch exception by reference rather than by value. Explicit conversion from memsize type to 32-bit integer type. Exception classes should be publicly accessible. Implicit type conversion N argument of function 'foo' to 32-bit type. Suspicious invocation of Thread.run(). OWASP. V525. AUTOSAR. V6050. V660. Unreachable code under a 'case' label. Size of a pointer is divided by another value. Two opposite conditions were encountered. It is possible that 'foo = bar == baz ? V3123. Two similar code fragments.

Probably meant: (T1)((T2)a + b). V2591. Parameter 'A' is always rewritten in method body before being used. Suspicious return of an always empty collection. There should be no implicit integral-floating conversion.

OWASP. Nonsensical comparison of two different functions' addresses. V728. It is odd that the body of 'Foo_1' function is fully equivalent to the body of 'Foo_2' function. Parameter of 'CancellationToken' type is not used inside function's body. The 'swap' function may interchange a variable with itself. Use volatile variable(s) or synchronization primitives to avoid this. Expression of sizeof(T)*N kind is summed up with pointer to T type. V3108. V586. OWASP. Consider inspecting the function call. V3040. Inspect the program's logic. Undefined behavior. V3015. This is unexpected behavior. V572. MISRA. V3002. This leads to undefined behavior. The standard input/output functions should not be used. V723. Consider inspecting the 'for' operator. Insecure XML parser is used to process potentially tainted data. Memory is allocated and released multiple times inside the loop body. V5011. MISRA. The macro with the 'setjmp' name and the function with the 'longjmp' name should not be used. V3166. V3542. Property accessors use different backing fields. > ? Decreased performance. Value of a composite expression should not be cast to a different essential type category or a wider essential type. MISRA. V615. NULL, Electronics Bazaar is one of best Online Shopping Store in India. V594. V3111. Custom declaration of standard type. Variable is assigned but not used by the end of the function. Constructor contains potentially uninitialized members. AUTOSAR. If the programmer does not explicitly provide a destructor, then which of the following creates an empty destructor?


V3144. V6085. The 'throw' keyword could be missing. Suspicious semicolon ';' after 'if/for/while' operator. V2533. Dangerous construction is used: 'm[x] = m.size()', where 'm' is of 'T' class. > ? OWASP. The original exception object was swallowed. Parameter is not utilized inside method's body. Bounds should not contain size of a buffer, but a number of characters it can hold. MISRA. How many default constructors per class are possible? String is printed into itself. Consider inspecting the application's logic. V641. V668. Bit shifting of the 32-bit value with a subsequent expansion to the 64-bit type. Pointer was used in the logical expression before its check for nullptr in the same logical expression. A component of TimeSpan is used, which does not represent full time interval. V548. Excessive type casting: string -> char * -> string. V1057. The 'default' label should be either the first or the last label of a 'switch' statement. Single-bit bit fields should not be declared as signed type. The '?.' Consider inspecting the expression. Memsize type is used in the struct/class. Compiler may optimize out this loop or make it infinite. , : , , , . V3115. V3035. Consider inspecting the expression for function call. A value is being subtracted from the unsigned variable. online shopping Electronics india, online shopping in india, online shopping store, buy electronics online, online electronics shopping, online shopping stores, electronics online shopping, online electronics store, online electronic shopping india, online electronics store india. V3059. Use 'double.IsNaN()' method instead. V787. V5005. V568. A class object and a member of that class. V1077. A function should not call itself either directly or indirectly. Expression resulting from the macro expansion should be surrounded by parentheses. V2527. AUTOSAR. V3085. Potential insecure deserialization vulnerability. It will not compile because a class cannot be protectedly inherited from other class. V1060. V580. Parameter 'A' is always rewritten in method body before being used. Consider inspecting the expression. V587. V803. V5304.

Object created using 'new' operator is immediately cast to another type. OWASP. V015. V3127. V3067. Comparing objects of incompatible types. Integer constant is converted to pointer. Array size should be specified explicitly when array declaration uses designated initialization. Possibly 'Total*' value was intended instead. Floating-point values should not be tested for equality or inequality. Function returns a pointer to the internal string buffer of a local object, which will be destroyed. Function receives an odd argument. V2017.

A double memory deallocation will occur. > ? The variable is not used after copying. Octal and hexadecimal escape sequences should be terminated. V5003. Unions should not be used. V3058. V673. V3131. V532. Bool type value is compared with value of N. Consider inspecting the expression. V221. Function always returns the same value of NN. The value of uninitialized variable should not be used. V644. V636. Consider inspecting the expression. Storing credentials inside source code can lead to security issues. It may be an error. Calling the 'foo' virtual function in the constructor/destructor may lead to unexpected result at runtime. A pointer/reference parameter in a function should be declared as pointer/reference to const if the corresponding object was not modified. Consider utilizing an explicit type cast to avoid the loss of a fractional part. Identical expression to the left and to the right of compound assignment. Member operator[] of object 'foo' is declared with 32-bit type argument, but is called with memsize type argument. V6101. V2615. WPF: the type registered for DependencyProperty does not correspond with the type of the property used to access it. The expression is checked for compatibility with the type 'A', but is casted to the 'B' type. MISRA. V6059. The Ctor(SerializationInfo, StreamingContext) constructor is missing. It is pointless to compute the distance between the elements of different arrays. V6037. The '? The 'static' storage class specifier should be used in all declarations of object and functions that have internal linkage. It is not recommended to return null or throw exceptions from 'ToString()' method. > ?

>. - ? Potential XEE vulnerability. Check for an error or bad coding style. V1083. Consider using the 'size()' function. V6096. It's probably an error or un-optimized code.

WPF: the names of the property registered for DependencyProperty, and of the property used to access it, do not correspond with each other. V5004. It's possible that the line was commented out improperly, thus altering the program's operation logics. V730. The argument of the method is not expected to be null.

The closing tag was encountered, while the tag was expected. V647.

V604. Dereferencing the result of 'as' operator can lead to NullReferenceException. In such a case, the comparison operation may behave unexpectedly.

MISRA. OWASP. There should be no occurrence of undefined or critical unspecified behaviour. MISRA. Use of constant NN. > - ? V121. V808. malloc() function accepts a dangerous expression in the capacity of an argument. > ?

The 'throw' operator does not have any arguments and is not located within the 'catch' block. V2618. Potentially tainted data might be used to execute a malicious script. The 'throw' keyword could be missing. Some warnings could have been disabled. An exception handling block does not contain any code. Consider specifying execution policy explicitly. No handlers will be unsubscribed, as a separate delegate instance is created for each anonymous function declaration. But how destructor uses virtual? V2578. V206. V3105. 16, Col. Ladrn de Guevara, C.P. Empirical analysis. , V1002. Consider implementing event accessors explicitly or use 'sealed' keyword. V1054. Features from should not be used. MISRA. The 'throw' keyword could be missing. MISRA. Probably it is a mistake. Possible XSS vulnerability. One of the operands in the operation equals NN. V704. Possibly an equality comparison was intended. > ? Function returns pointer/reference to temporary local object. By making at least one member function as pure virtual function. Consider verifying the initializer.

V516. Consider inspecting the 'for' operator. , , V1002. Possible excessive expression or typo. Operand of sizeof() operator should not have other side effects. Decreased performance. The functions from time.h/ctime should not be used. Declaring virtual methods in a class marked as 'final' is pointless. Use _beginthreadex/_endthreadex functions instead of CreateThread/ExitThread functions. OWASP. V514. V3091. Odd semicolon ';' after 'if/for/while' operator. V6011. Consider inspecting the expression. A variable of the memsize type is read from a stream. Two or more case-branches perform the same actions. Controlling expressions should not be invariant.

The 'A' function was called several times with identical arguments. V2530. Decreased performance. Casts between a void pointer and an arithmetic type should not be performed. Annotation that does not have 'RUNTIME' retention policy will not be accessible through Reflection API. MISRA. Waiting on this expression is unreliable, as compiler may optimize some of the variables. That is base class destructor must not be called upon calling derived class destructor. V818. V3503. Suspicious return of a local reference variable which always equals null. MISRA. The 'X' counter is not used inside a nested loop.

Potential logical error. V6039.

Expression of essential type 'foo' should not be explicitly cast to essential type 'bar'. MISRA. > ? V3156. V1012. AUTOSAR. MISRA. The function with the 'atof/atoi/atol/atoll' name should not be used. V3147. V002. V823. > ? Passing 'BSTR ' to the 'SysAllocString' function may lead to incorrect object creation. V805. An exception handling block does not contain any code. V6071. An item with the same key has already been added. The 'alloca' function is used inside the loop. Recurring check. It is suspicious and can possibly be an error. V004. > , 1935 ? :' operator, regardless of its conditional expression, always returns one and the same value. MISRA. Condition of a loop is always true/false. V566. V2006. > ? Consider inspecting the expression. V2516. V3521. Comparison with 'double.NaN' is meaningless. MISRA. The 'goto' statement should not be used. The original exception object was swallowed. Consider inspecting usage of 'Y' counter. AUTOSAR. V6036. V6013. V6086. The value of the captured variable will be overwritten on the next iteration of the loop in each instance of anonymous function that captures it. V3095. V593. V714. A pattern was detected: A || (A && ). It is possible that a line was commented out improperly, thus altering the program's operation logic. OWASP. Functions should not have unused parameters. The 'Thread' object is created but is not started. V773. V765. Function body contains the 'X' label that is not used by any 'goto' statements. V3141. Decreased performance. Suspicious division: sizeof(X) / Value. Declaration should contain no more than two levels of pointer nesting. The 'Foo' function receives class-type variable as 'N'th actual argument. It is inefficient to identify an empty string by using 'strlen(str) > 0' construct. V689. Every 'switch' statement should have a 'default' label, which, in addition to the terminating 'break' statement, should contain either a statement or a comment. V549. WPF: readonly field of 'DependencyProperty' type is not initialized. V575. Such a pointer will become invalid. Consider assigning value to 'foo' variable instead of declaring it anew. Function with a non-void return type should return a value from all exit paths. MISRA. Exception classes should be publicly accessible.

V630. The behavior is undefined for arithmetic or comparisons with pointers that do not point to members of the same array. Pointer is used both as an array and as a pointer to single object. The 'x' variable is assigned to itself. Undefined behavior will occur in case of signed integer overflow. MISRA. The 'if' 'else if' construct should be terminated with an 'else' statement. :' operator. V3068. Consider inspecting the 'for' operator. > () ? It is possible that macro expansion resulted in incorrect evaluation order. The 'delete A, B' expression only destroys the 'A' object. Consider inspecting the 'switch' statement. > ? Block of memory should only be freed if it was allocated by a Standard Library function. V3070. V770. V5013. Keyword 'nullptr' can be used for 'pointer' type exception. The function is deprecated in the Win64 system. V2506. Probably meant 'A[B] < C'. V2594. Casting potential 'null' value to a value type can lead to NullReferenceException. In such a case, the comparison operation can potentially behave unexpectedly. V3533. The 'throw' keyword could be missing. MISRA. A non-serializable class should not be serialized. Probably the '!=' should be used here. V3011. V732. V3154. Expression is equivalent to moving one unique pointer to another. Consider reviewing the correctness of 'X' item's usage.

Expressions with enum underlying type should have values corresponding to the enumerators of the enumeration. V2563.

V3149. V515. This can result in an overflow. V3536. V3519. Cast should not convert pointer to function to any other pointer type. A function name may be missing. Consider using '||' and '&&' instead. Significance of virtual function is to provide late binding by restricting the early binding. V6077. No answer description available for this question. It is possible that creating a new variable is unnecessary. Class member is initialized with dangling reference. V2525. Potential Java SE API compatibility issue. V5012. The variable is incremented in the loop. Memory allocation will lead to an exception. The 'if (ptr != NULL)' check can be removed. V694. V6068. Two similar code fragments were found. This means that the second 'if' statement is senseless. V724. OWASP. V6056. V1051. V6105. Potential division by zero. Cyclomatic complexity: NN.

Intermodular analysis may be incomplete, as it is not run on all source files. V543. Exception is of the 'int' type because NULL is defined as 0.

It's odd that this method always returns one and the same value of NN.

V530. V3506.

Possible incorrect order of arguments passed to function. Consider using an explicit type cast to avoid overflow or loss of a fractional part. V3053. Consider assigning realloc() to a temporary pointer. So destructor should be always virtual so respective descended class's destruction execute instead of parent class destructior, when accesed through pointer as a refrence of the oblect.

The value is out of range of enum values. One pair of parentheses is unnecessary or misprint is present. V3082. V124. V529. Priority of the '&&' operator is higher than that of the '||' operator. Pointer was used after the memory was released. Implicit type conversion from memsize type to 32-bit type. V2503. AUTOSAR. Suspicious function declaration. Perhaps, this is a typo and 'X' variable should be used instead of 'Y'. V3004. > ? MISRA. Consider inspecting the first parameter of 'getline' function. V596. V741. V3084. The argument should probably be rendered as a constant pointer/reference. Octal constants should not be used. The object could have been garbage collected before the 'Target' property was accessed. Consider replacing 'const T' with 'const .. &T' / 'const .. *T'. Value may not correspond with the length of a string passed with YY argument. > ? An unconditional 'break/continue/return/goto' within a loop. MISRA. It is possible that different variables are used inside initializer and iterator. MISRA. V799. This may be a potential error. Destructor of the object will be invoked a second time after leaving the object's scope.

V544. The expression is excessive or contains a logical error. V3017. It is suspicious that the result of the statement is a part of the condition. Question is : Which of the following statement is correct? V2504. The return value of non-void function should be used. V3173. Any loop should be terminated with no more than one 'break' or 'goto' statement. The function with the 'abort/exit/getenv/system' name should not be used. V555. An item with the same key has already been added. A private Ctor(SerializationInfo, StreamingContext) constructor in unsealed type will not be accessible when deserializing derived types. It is possible that the 'i' variable should be incremented instead of the 'n' variable. Remember that 'a == b == c' is not equal to 'a == b && b == c'. V744. MISRA. V3006. Value of 'A' type is assigned to a pointer of 'B' type. V1038. Potential XXE vulnerability. Odd semicolon ';' after 'if/for/while' operator. The 'malloc' function is used to allocate memory for an array of objects that are classes containing constructors/destructors.

V539. V769. V6094. Any label should be declared in the same block as 'goto' statement or in any block enclosing it. V798. It is suspicious that the BSTR data type is compared using a relational operator. Incorrect format. V772. Member 'x' should point to string terminated by two 0 characters. Potentially tainted data is used to create an object using deserialization. Two identical text blocks were detected. Consider using parentheses in the expression. V3117. > ? > ? V638. Check lines: N1, N2. V2508. V303. V3547. V672. V2589. V1014. This file is marked with copyleft license, which requires you to open the derived source code. V820. Use of jump statements in 'finally' block can lead to the loss of unhandled exceptions.

The 'if/if-else/for/while/foreach' statement and code block after it are not related. V684. V3021. The 'A' field should probably be returned/assigned instead. V551. V3037. V3545. V5618. V3555. Use volatile variable(s) or synchronization primitives to avoid this. Check lines: N1, N2. The first 'if' statement contains function return. MISRA. The 'bar2.h' header will be excluded from compilation. V6022. Suspicious pointer arithmetic. V3161. OWASP. Consider inspecting the return statement. V2593. Casting expression to 'X' type before implicitly casting it to other type may be excessive or incorrect. Do not define an unnamed namespace in a header file. Bit fields should only be declared with explicitly signed or unsigned integer type.

Calling the 'SingleOrDefault' method may lead to 'InvalidOperationException'. MISRA. Use 'memmove' function. V202. V2602. C-style and functional notation casts should not be performed. Consider using 'std::move' instead. Stack of original exception could be lost. V6027. V2600. V3501. V3076. > ? Incorrect type of a loop variable. It's possible that the line was commented out improperly, thus altering the program's operation logics.