Method for positioning specific memory illegally rewritten by function

Abstract

The invention provides a method that a positioned specific memory is illegally rewritten by a function, wherein, during the running of an embedded real-time operating system, exception processing of the function when the specific memory is rewritten is set in the specific memory function body which is not allowed to be visited, and corresponding processing and positioning are carried out when thespecific memory is rewritten in the function. The method that the positioned specific memory is illegally rewritten by the function can better avoid the condition that the positioned specific memory is illegally rewritten but unknown to people, so as to improve the stability of the system.

Description

technical field [0001] The invention relates to the communication field, in particular to a method for locating specific memory illegally rewritten by a function. Background technique [0002] In the field of communication technology, most products use embedded real-time operating systems, such as Linux, VxWorks and other operating systems. In the current data communication products, such as routers, switches, and broadband access servers, VxWorks is used as the cornerstone of technical development. The memory management adopts the flat (FLAT) memory mode based on VxWorks. All global variables, queues, Linked lists and pointers can be directly accessed by all tasks. Although this can improve the efficiency of communication between processes or tasks, it is also likely to cause abnormal system operation. [0003] In order to avoid the system instability caused by the above-mentioned shared memory, it is usually considered to protect the shared memory by prohibiting preempti...

AI Technical Summary

Problems solved by technology

[0004] In the above three methods, the prohibition of preemption will temporarily invalidate the kernel task scheduling, but other tasks cannot run except for the interrupt program; when using semaphores to protect shared memory, other tasks are not prohibited from running, only access The suspension of tasks to shared memory resources, although it has little impact on the real-time performance of the system, cannot prevent the interrupt service program from accessing critical resources; while turning off interrupts is more effective than the above two methods, it can completely prevent other The conflicting access of tasks or interrupt service programs has the highest execution efficiency, but the interrupt can only be turned off for a short time, otherwise the system clock and other external events will not be processed correctly, thus greatly reducing the real-time level of the system

[0005] In short, the protection of specific shared memory through the above three methods has its own shortcomings. Therefore, it is necessary to find a more effective method to prevent specific memory from being illegally rewritten

Images