Task stack overflow monitoring method and system

Abstract

The invention provides a task stack overflow monitoring method, which comprises the following steps that: detecting the operation state of a function stack in a task; if the operation state of the function stack is a preset function stack operation, reading the stack bottom address of the task stack; comparing a difference value obtained in a way that the total length of the task stack is subtracted from a current stack top address and the stack bottom address of the task stack; and according to a comparison result, monitoring task stack overflow. Compared with the prior art, the scheme disclosed by the invention does not occupy additional memory space used for setting a read-only memory area, and a task stack overflow phenomenon is monitored in real time and does not fail to be reported.

Description

technical field [0001] The present application relates to the field of computers, in particular to a method and system for monitoring task stack overflow. Background technique [0002] In the operating system, such as the Linux operating system, in order to improve the operating efficiency of the operating system, all tasks will share the same physical address space, only the memory space occupied by the task stack is independent, and there is no memory address protection mechanism between any tasks. The total length of a task stack is limited. If it is too long, memory space will be wasted. If it is too short, it may cause task stack overflow (task stack overflow is also called stack top crossing). Task stack overflow means that memory contents used for other functions will be read and written during task execution. The memory content of other functions may be the memory content used by this task, or the memory content used by other tasks, resulting in various abnormal phe...

AI Technical Summary

Problems solved by technology

[0004] The disadvantage of the existing technical solution is: in the memory space occupied by each function, not every byte can be read and written, and a considerable part of the memory content is reserved, and no read and write operations will occur; even if it is used for The space for storing local variables may not necessarily be written due to different function parameters or external conditions

When other tasks access the memory that has been written into wrong data again, the function will be abnormal, and the phenomenon of task stack overflow cannot be monitored in real time, and the phenomenon of task stack overflow will be missed.

Images