Program -class operating system debug method based on serial mode excavation

Abstract

The invention discloses a program-level operating system debugging method based on sequential pattern mining, comprising the following steps: to find all the frequent system calling sequential patterns through sequential pattern mining; to compute all the parameters in a hidden Markov model to identify abnormal system calling sequences. The method makes use of the sequential pattern mining method to carry through pattern mining to the system calling sequence set in the desktop operating system to find all the frequent sequence set, and also makes use of the frequent sequence set to train the hidden Markov model so as to eventually identify the abnormal system calling sequences through the Markov model to accurately and quickly target the bug location of the entire desktop operating system to help the user to improve the operating system.

Description

A Program-Level Operating System Debugging Method Based on Sequential Pattern Mining technical field The invention relates to a program-level operating system debugging method based on sequence pattern mining, and belongs to the field of desktop operating system debugging. Background technique At present, due to insufficient funds and manpower, many desktop operating systems encounter various bugs (system defects) in the later stage of perfection. Sometimes the number of bugs is too large, and developers can't grasp the key points, often can't find the real bugs, and the system has not been really improved. At this time, general developers will use traditional debugging tools to find bugs, such as GDB (General Public License Debugger) and other tools. GDB is a program debugging tool under UNIX released by the GNU (General Public License) open source organization. It mainly has the following functions in debugging: ① start the program, and run the program as you like acco...

AI Technical Summary

Problems solved by technology

However, desktop operating systems are generally relatively large, and it is unrealistic for GDB to debug the entire system. It only has a very obvious effect on local debugging, and cannot quickly locate the bug location of the entire desktop operating system.

Images