Leetcode error reporting and its solution

LeetCode Report errors

AddressSanitizer: xxx-buffer-overflow

Usually C/C++ compiler No boundary check is added to memory access . Sometimes better than code errors , There is reading or writing Operated on the memory address outside the buffer . Such mistakes are generally difficult to detect . So once compilation occurs AddressSanitizer: stack-buffer-overflow error , First, check whether the boundary conditions of your code are not controlled .

stack-buffer-overflow

give an example ：

int a[10];
a[11] = 10; // stack-buffer-overflow
a[-1] = 10; //stack-buffer-underflow

resolvent ： Check every cycle in the program （for or while loop ） Whether the conditions are correct .

head-buffer-overflow

give an example ：

int* x = malloc(10);
int n=x[11]; //heap-buffer-overflow
int n=x[-1]; //heap-buffer-underflow

heap-buffer-overflow

The cause of this error is generally that the array is out of bounds , Maybe the initialized array is not long enough or the subscript is out of bounds in the program .

resolvent ： Check whether the array subscript in the code is used correctly , Exclude the possibility of crossing the boundary .

runtime error: member access within null pointer

The reason for the error ： Trying to use a null pointer , Most of the time, it is because of the special data of the topic , For example, an empty array
resolvent ： Add judgment conditions , And the order of judgment cannot be changed . Exclude references to null pointers .

runtime error: reference binding to null pointer of type ‘xxx’

translate ： Runtime error ： The reference is bound to the type “xxx” The null pointer of

The reason for the error ：

• Yes for Loop or while when , The case that the array is empty is not considered
• Value and type do not correspond , such as int flag=true;