WO2020215567A1

WO2020215567A1 - Global hook automatic repair method, apparatus, device, and storage medium

Info

Publication number: WO2020215567A1
Application number: PCT/CN2019/103162
Authority: WO
Inventors: 何兵
Original assignee: 平安科技（深圳）有限公司
Priority date: 2019-04-26
Filing date: 2019-08-29
Publication date: 2020-10-29
Also published as: CN110221961A

Abstract

Disclosed by the present application are a global hook automatic repair method, apparatus, device, and storage medium based on the field of security monitoring, used for automatically blocking classes which cause global crashes, avoiding modification of the code and improving repair efficiency. The method of the present application comprises: defining a loop, said loop being used for hooking all classes; defining a variable function, said variable function being used for recording the name of a class to be hooked; according to the loop and the variable function, determining whether the name of the class to be hooked is in a filter list; if the name of the class to be hooked is in said filter list, then blocking the crash class corresponding to the name of the class to be hooked, said crash class being a category which causes a crash or an exception.

Description

Global hook automatic repair method, device, equipment and storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on April 26, 2019, the application number is 201910341769.2, and the invention title is "Global hook automatic repair method, device, equipment and storage medium", the entire content of which is incorporated by reference Incorporate in the application.

Technical field

The present invention relates to the field of operating system security monitoring, in particular to a method, device, equipment and storage medium for automatically repairing a global hook.

Background technique

With the rapid development of the mobile phone industry, mobile phone systems have also developed accordingly. At present, the mainstream systems include Android and IOS systems. For the IOS system, if the IOS project needs to test the code coverage, a better way is to hook all the classes, and then add the statistical code in all the methods of all the classes, but because the types of classes in each project are complex and the number is huge , The writing of some classes will cause a crash on a hook.

At present, the more conventional method is to manually eliminate the problem manually. The inventor realizes that the code needs to be manually modified to shield the related classes that cause the crash, and the repair efficiency is low.

Summary of the invention

The embodiments of the present application provide a global hook automatic repair method, device, device, and storage medium, which are used to automatically shield classes that cause global crashes, avoid code modification, and improve repair efficiency.

The first aspect of the embodiments of the present application provides a global hook automatic repair method based on data analysis, including: defining a loop for hooking all classes; defining a variable function for Record the name of the class to be hooked; determine whether the name of the class to be hooked is in the filter list according to the loop and the variable function; if the name of the class to be hooked is in the filter list, block A crash class corresponding to the name of the class to be hooked, and the crash class is the class that caused the crash or exception.

Optionally, in the first implementation manner of the first aspect of the embodiments of the present application, after the method determines whether the name of the class to be hooked is in the filter list according to the loop and the variable function, It also includes: if the name of the class to be hooked is not in the filter list, calling the loop to hook the class to be hooked.

Optionally, in the second implementation manner of the first aspect of the embodiments of the present application, after the shielding the crash class corresponding to the name of the class to be hooked, the crash class is the class that caused the crash or exception, The method further includes: monitoring an abnormal function, the abnormal function is used to monitor and record the array corresponding to the crash class; determining the name of the crash class in the abnormal function according to the array corresponding to the crash class; The name of the crash category is imported into the filtering list.

Optionally, in the third implementation manner of the first aspect of the embodiments of the present application, the defining a loop, the loop being used to hook all classes includes: obtaining the path of the currently running target application; obtaining The name and quantity of each class of the target application; a for loop is defined according to the name and quantity of each class, and the for loop is used to globally hook each class according to the path of the target application.

Optionally, in the fourth implementation manner of the first aspect of the embodiments of the present application, the defining a variable function, where the variable function is used to record the name of the class to be hooked includes: obtaining a preset key value; The preset key value calls an array of crash classes stored in the system memory or a preset database; a variable function is defined according to the array of crash classes, and the variable function is used to record the name of the class to be hooked.

Optionally, in the fifth implementation manner of the first aspect of the embodiments of the present application, the determining whether the name of the class to be hooked is included in the filter list according to the loop and the variable function: determining that the The array called in the loop; determine the variable function in the called array; determine the name of the class to be hooked in the variable function, and determine whether the name of the class to be hooked is in the filter list.

Optionally, in the sixth implementation manner of the first aspect of the embodiments of the present application, the method further includes: if the number of crash categories in the filter list is greater than a threshold, integrating the categories that caused the crash; The prefixes of the crash classes of the same type in the crash classes; the crash classes with the prefixes are blocked in batches.

The second aspect of the embodiments of the present application provides a global hook automatic repair device, including: a first definition unit for defining a loop, the loop is used for hooking all classes; a second definition unit for Define a variable function, the variable function is used to record the name of the class to be hooked; the judging unit is used to judge whether the name of the class to be hooked is in the filter list according to the loop and the variable function; first The shielding unit, if the name of the class to be hooked is in the filter list, is used to shield the crash class corresponding to the name of the class to be hooked, and the crash class is a class that causes a crash or an exception.

Optionally, in the first implementation manner of the second aspect of the embodiments of the present application, the global hook automatic repair device further includes: a calling unit, if the name of the class to be hooked is not in the filter list, it is used Call the loop to hook the class to be hooked.

Optionally, in the second implementation manner of the second aspect of the embodiments of the present application, the global hook automatic repair device further includes: a monitoring unit for monitoring abnormal functions, and the abnormal functions are used for monitoring and recording the crash category Corresponding array; a first determining unit for determining the name of the crash class in the abnormal function according to the array corresponding to the crash class; an importing unit for importing the name of the crash class into the filter list.

Optionally, in the third implementation manner of the second aspect of the embodiments of the present application, the first definition unit is specifically configured to: obtain the path of the currently running target application; obtain the names and names of various classes of the target application; Quantity: A for loop is defined according to the name and quantity of each class, and the for loop is used to globally hook each class according to the path of the target application.

Optionally, in the fourth implementation manner of the second aspect of the embodiments of the present application, the second definition unit is specifically configured to: obtain a preset key value; call the storage in the system memory or the preset according to the preset key value. An array of crash classes in the database is set; a variable function is defined according to the array of crash classes, and the variable function is used to record the name of the class to be hooked.

Optionally, in the fifth implementation manner of the second aspect of the embodiments of the present application, the judging unit is specifically configured to: determine the array called in the loop; determine the variable function in the called array; State the name of the class to be hooked in the variable function, and determine whether the name of the class to be hooked is in the filter list.

Optionally, in the sixth implementation manner of the second aspect of the embodiments of the present application, the global hook automatic repair device further includes: an integration unit, if the number of crash categories in the filter list is greater than a threshold, it is used to The second determining unit is used to determine the prefix of the crash category of the same type in the crash category; the second shielding unit is used to block the crash categories with the prefix in batches.

The third aspect of the embodiments of the present application provides a global hook automatic repair device, which includes a memory, a processor, and a computer program stored on the memory and running on the processor, and the processor executes the The computer program implements the global hook automatic repair method described in any of the above embodiments.

The fourth aspect of the embodiments of the present application provides a computer-readable storage medium that stores instructions in the computer-readable storage medium, and when the instructions run on a computer, the computer executes any of the foregoing The steps of the global hook automatic repair method.

In the technical solution provided by the embodiment of this application, a loop is defined, which is used to hook all classes; a variable function is defined, which is used to record the name of the class to be hooked; and the loop and variable function are used to determine the Whether the name of the hook class is in the filter list; if the name of the class to be hooked is in the filter list, the crash class corresponding to the name of the class to be hooked is blocked, and the crash class is the class that caused the crash or exception. The embodiment of the application automatically shields classes that cause global crashes, avoids code modification, and improves repair efficiency.

Description of the drawings

FIG. 1 is a schematic diagram of an embodiment of a global hook automatic repair method in an embodiment of the application;

2 is a schematic diagram of another embodiment of the global hook automatic repair method in the embodiment of the application;

Fig. 3 is a schematic diagram of an embodiment of a global hook automatic repair device in an embodiment of the application;

4 is a schematic diagram of another embodiment of the global hook automatic repair device in the embodiment of the application;

Figure 5 is a schematic diagram of an embodiment of a global hook automatic repair device in an embodiment of the application.

Detailed ways

In order to enable those skilled in the art to better understand the solutions of the present application, the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, without having to use To describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances so that the embodiments described herein can be implemented in an order other than the content illustrated or described herein. In addition, the terms "including" or "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device including a series of steps or units is not necessarily limited to those clearly listed Steps or units, but may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or equipment.

Please refer to Fig. 1, a flowchart of a global hook automatic repair method provided by an embodiment of the present application, which specifically includes:

101. Define a loop that is used to hook all classes.

The server defines a loop that is used to hook all classes. Specifically, the server defines a for loop through which all classes of the system or application are hooked. For example, the server obtains the path of the currently running target application; the server obtains the name and quantity of each class of the target application; the server defines a for loop according to the name and quantity of each class, and the for loop is used to match the path of the target application All classes are hooked globally.

For example, when you need to hook an application (application, APP), first obtain the path of the currently running APP, such as dladdr(&_mh_execute_header,&info); secondly, obtain the name of each class of the currently running APP, and each class quantity. For example, classes=objc_copyClassNamesForImage(info.dli_fname,&count); among them, the two-dimensional array classes stores the names of all classes, and count stores the number of all classes; finally, a for loop is defined according to the names and numbers of each class. For example, take the array out of the classes in the classes array one by one, and the for loop starts.

102. Define a variable function, which is used to record the name of the class to be hooked.

The server defines a variable function, which is used to record the name of the class to be hooked.

Specifically, the server first obtains the preset key value; then calls the crash class array according to the preset key value, and the crash class array is stored in the system memory or the preset database; and then defines a variable function according to the crash class array, Among them, the variable function is used to record the name of the class to be hooked.

For example, a string defined by the server, such as PA_HookCrashListKey, is stored and recalled using the system's own storage (or pre-written database code). The crashed class array is the object obtained from the database by key.

103. Determine whether the name of the class to be hooked is in the filter list according to the loop and variable function.

The server judges whether the name of the class to be hooked is in the filter list according to the loop and variable function. Specifically, the server determines the array to be called in the loop; the server determines the variable function in the called array; the server determines the name of the class to be hooked in the variable function, and determines whether the name of the class to be hooked is in the filter list. If the name of the class to be hooked is in the filtering list, the server blocks the crash class corresponding to the name of the class to be hooked. If the name of the class to be hooked is not in the filter list, the server will call the hooked class in a loop.

Specifically, the server hooks the hooked class through a for loop. The hook is a platform of the Windows message processing mechanism, and the application (APP) can set up a subroutine on it to monitor a certain message in the specified window, and The monitored window can be created by other processes. When the message arrives, it is processed before the target window processing function. The hook mechanism allows applications to intercept and process window messages or specific events. A hook is actually a program segment that processes messages, which is hooked into the system through system calls. Whenever a specific message is sent out and before it reaches the destination window, the hook program captures the message first, that is, the hook function first gets the control right. At this time, the hook function can process (change) the message, or continue to deliver the message without processing, or force the end of the message delivery.

It should be noted that the order of hooks is random and depends on the array order of all the classes returned to me by the system method. I then take out one by one from the array to hook. The hook standard is: get all the methods of the class, filter some of the methods that come with the system and the methods that need to be filtered. The method that needs to be filtered depends on the project and business and is pre-configured by the staff. For the remaining methods, the method Address change, forcibly trigger the object-oriented C (objective-C, OC) language message forwarding mechanism, and then rewrite the forwardInvocation method called during message forwarding, change the address in this method, but before changing it back, You can write some hook code to achieve the purpose of hook.

104. If the name of the class to be hooked is in the filtering list, the crash class corresponding to the name of the class to be hooked is shielded, and the crash class is the class that caused the crash or exception.

If the name of the class to be hooked is in the filter list, the server blocks the crash class corresponding to the name of the class to be hooked, and the crash class is the class that caused the crash or exception.

It is understandable that the system monitors through its own abnormal function, and saves the array to the filter list before each crash. At the next startup, the name of a crash category will be added to the filter list and used as a criterion.

In the embodiment of this application, a loop is defined to hook all classes; a variable function is defined to record the name of the class to be hooked; the name of the class to be hooked is determined according to the loop and variable function Whether it is in the filter list; if the name of the class to be hooked is in the filter list, the crash class corresponding to the name of the class to be hooked is blocked, and the crash class is the class that caused the crash or exception. The classes that cause global crashes can be automatically shielded, avoiding the modification of the system code, and improving the repair efficiency.

Referring to FIG. 2, another embodiment of the global hook automatic repair method in the embodiment of the present application includes:

201. Define a loop for hooking all classes.

202. Define a variable function, which is used to record the name of the class to be hooked.

203. Determine whether the name of the class to be hooked is in the filter list according to the loop and variable function.

Specifically, the server hooks the hooked class through a for loop. The hook is a platform of the Windows message processing mechanism, and the application (APP) can set up a subroutine on it to monitor a certain message in the specified window, and The monitored window can be created by other processes. When the message arrives, it is processed before the target window processing function. The hook mechanism allows applications to intercept and process window messages or specific events. A hook is actually a program segment that processes messages, which is hooked into the system through system calls. Whenever a specific message is sent out, and before reaching the destination window, the hook program captures the message first, that is, the hook function first gets the control right. At this time, the hook function can process (change) the message, or continue to deliver the message without processing, or force the end of the message delivery.

It should be noted that the order of hooks is random and depends on the array order of all the classes returned to me by the system method. I then take out one by one from the array to hook. The hook standard is: get all the methods of the class, filter some of the methods that come with the system and the methods that need to be filtered. The method that needs to be filtered depends on the project and business and is pre-configured by the staff. For the remaining methods, the method Address changes, forcibly triggering the message forwarding mechanism for OC language, and then rewrite the forwardInvocation method called during message forwarding. In this method, the address is changed back, but before changing back, you can also write some hook code to achieve hook the goal of.

204. If the name of the class to be hooked is in the filtering list, shield the crash class corresponding to the name of the class to be hooked, and the crash class is the class that caused the crash or exception.

It is understandable that the system monitors through its own abnormal function, and saves the array to the filter list before each crash. At the next startup, the name of a crash class will be added to the filter list, and the name of the added crash class will be used as the criterion.

205. Monitor an exception function, which is used to monitor and record the array corresponding to the crash class.

The server monitors the abnormal function in the system, where the abnormal function is used to monitor and record the array corresponding to the crash class. The array stores specific data corresponding to each class. For example, if the variable function is a, because the a in the array is stored before the hook is started, that is, a mark is made in the data, and then a is deleted after the method call of the hook code. Conversely, if the hook code crashes and the following code has no chance to run, the a in this array will not be deleted. The next time we hook, we find that a is in the crash array, so we won’t hook it anymore. Fall into a loop.

206. Determine the name of the crash class in the abnormal function according to the array corresponding to the crash class.

The server determines the name of the crash class in the abnormal function according to the array corresponding to the crash class. For example, the server determines the name of the crashed crash class in the exception function NSSetUncaughtExceptionHandler according to the array corresponding to the crashed class.

207. Import the name of the crash class into the filtering list.

The server imports the names of crash classes into the filter list, which includes the names of classes that can cause system crashes or exceptions.

Optionally, if the number of crash classes in the filter list is greater than the threshold, the server integrates the classes that caused the crash; the server determines the prefixes of the crash classes of the same type in the crash classes; the server blocks the crash classes with prefixes in batches.

In the embodiment of this application, a loop is defined to hook all classes; a variable function is defined to record the name of the class to be hooked; the name of the class to be hooked is determined according to the loop and variable function Whether it is in the filter list; if the name of the class to be hooked is in the filter list, the crash class corresponding to the name of the class to be hooked will be shielded, the crash class is the class that caused the crash or exception; the exception function is monitored Used to monitor and record the array corresponding to the crash class. In the embodiment of this application, each time the system crashes, there will be one more class that needs to be blocked in the crash array. When the hook code is started next time, according to the previous strategy, hooks are not executed for this class, so that the crashed classes will not be executed. Once hooked, it will not cause the system to crash. The classes that cause the global crash can be automatically blocked, avoiding the modification of the system code, and improving the repair efficiency.

Optionally, on the basis of the above-mentioned embodiment corresponding to FIG. 2, in an optional embodiment of the global hook automatic repair method provided in the embodiment of the present application, it may further include:

Determine whether the variable function in the loop is empty; if the variable function is not empty, delete the class corresponding to the variable function in the array of crash classes.

Specifically, the server determines whether the variable function in the loop is empty. If the variable function is not empty, the server deletes the class corresponding to the variable function in the array of crash classes. If the variable function is empty, the server ignores the variable function.

Optionally, on the basis of the embodiment corresponding to FIG. 2 above, in an optional embodiment of the global hook automatic repair method provided in the embodiment of the present application, the method further includes:

If the name of the class to be hooked is not in the filter list, hook the class to be hooked in a loop.

In the embodiment of this application, a loop is defined to hook all classes; a variable function is defined to record the name of the class to be hooked; the name of the class to be hooked is determined according to the loop and variable function Whether it is in the filter list; if the name of the class to be hooked is in the filter list, the crash class corresponding to the name of the class to be hooked will be shielded, the crash class is the class that caused the crash or exception; the exception function is monitored Used to monitor and record the array corresponding to the crash class. The classes that cause global crashes can be automatically shielded, avoiding the modification of the system code, and improving the repair efficiency.

The global hook automatic repair method in the embodiment of this application is described above, and the global hook automatic repair device in the embodiment of this application is described below. Please refer to FIG. 3. An embodiment of the global hook automatic repair device in the embodiment of this application includes:

The first definition unit 301 is used to define a loop, and the loop is used to hook all classes;

The second definition unit 302 is used to define a variable function, and the variable function is used to record the name of the class to be hooked;

The judging unit 303 is configured to judge whether the name of the class to be hooked is in the filter list according to the loop and the variable function;

The first shielding unit 304, if the name of the class to be hooked is in the filter list, it is used to shield the crash class corresponding to the name of the class to be hooked, and the crash class is the one that caused the crash or exception class.

Referring to FIG. 4, an embodiment of the global hook automatic repair device in the embodiment of the present application includes:

Optionally, the global hook automatic repair device also includes:

The calling unit 305, if the name of the class to be hooked is not in the filter list, is used to hook the class to be hooked through the loop.

Optionally, the global hook automatic repair device also includes:

The monitoring unit 306 is configured to monitor abnormal functions, and the abnormal functions are used to monitor and record the array corresponding to the crash class;

The first determining unit 307 is configured to determine the name of the crash class in the abnormal function according to the array corresponding to the crash class;

The importing unit 308 is configured to import the name of the crash category into the filtering list.

Optionally, the first definition unit 301 is specifically used for:

Obtain the path of the currently running target application; obtain the name and quantity of each class of the target application; define a for loop according to the name and quantity of each class, and the for loop is used to follow the target application The path of the global hook for each class.

Optionally, the second definition unit 302 is specifically configured to:

Obtain a preset key value; call an array of crash classes stored in the system memory or a preset database according to the preset key value; define a variable function according to the array of crash classes, and the variable function is used for recording The name of the class to be hooked.

Optionally, the judging unit 303 is specifically configured to:

Determine the array called in the loop; determine the variable function in the called array; determine the name of the class to be hooked in the variable function, and determine whether the name of the class to be hooked is in the filter list .

Optionally, the global hook automatic repair device also includes:

The integration unit 309, if the number of crash categories in the filter list is greater than the threshold, is used to integrate the categories that caused the crash;

The second determining unit 310 is configured to determine the prefix of the crash category of the same type in the crash category;

The second shielding unit 311 is used to shield the crash classes with the prefix in batches.

In the embodiment of this application, a loop is defined, which is used to hook all classes; a variable function is defined, which is used to record the name of the class to be hooked; the name of the class to be hooked is judged according to the loop and variable function Whether it is in the filter list; if the name of the class to be hooked is in the filter list, the crash class corresponding to the name of the class to be hooked will be shielded, the crash class is the class that caused the crash or exception; the exception function is monitored Used to monitor and record the array corresponding to the crash class. The classes that cause global crashes can be automatically shielded, avoiding the modification of the system code, and improving the repair efficiency.

The above Figures 3 to 4 describe the global hook automatic repair device in the embodiment of the present application in detail from the perspective of modular functional entities, and the following describes the global hook automatic repair device in the embodiment of the present application in detail from the perspective of hardware processing.

Figure 5 is a schematic structural diagram of a global hook automatic repair device provided by an embodiment of the present application. The global hook automatic repair device 500 may have relatively large differences due to different configurations or performance, and may include one or more processors (central Processing units, CPU) 501 (for example, one or more processors) and memory 509, and one or more storage media 508 for storing application programs 507 or data 506 (for example, one or one storage device with a large amount of storage). Among them, the memory 509 and the storage medium 508 may be short-term storage or persistent storage. The program stored in the storage medium 508 may include one or more modules (not shown in the figure), and each module may include a series of command operations in the global hook automatic repair device. Further, the processor 501 may be configured to communicate with the storage medium 508, and execute a series of instruction operations in the storage medium 508 on the global hook automatic repair device 500.

The global hook automatic repair device 500 may also include one or more power supplies 502, one or more wired or wireless network interfaces 503, one or more input and output interfaces 504, and/or one or more operating systems 505, such as Windows Serve, Mac OS X, Unix, Linux, FreeBSD, etc. Those skilled in the art can understand that the structure of the global hook automatic repair device shown in FIG. 5 does not constitute a limitation on the global hook automatic repair device, and may include more or less components than shown in the figure, or combine certain components, Or different component arrangements. The processor 501 can execute any of the first definition unit 301, the second definition unit 302, the judgment unit 303, the first shielding unit 304, the calling unit 305, the listening unit 306, the first determining unit 307, and the importing unit 308 in the foregoing embodiment. The function of a unit. The processor 501 may also perform the function of any one of the integration unit 309, the second determination unit 310, and the second shielding unit 311 in the foregoing embodiment.

The following is a detailed introduction to each component of the global hook automatic repair device in conjunction with Figure 5:

The processor 501 is the control center of the global hook automatic repair device, and can perform processing according to the set global hook automatic repair method. The processor 501 uses various interfaces and lines to connect the entire global hook to automatically repair various parts of the device, and executes the global hook by running or executing the software program and/or module stored in the memory 509 and calling the data stored in the memory 509 Automatically repair various functions of the device and process data, so as to realize the shielding of crashes. The storage medium 508 and the memory 509 are both carriers for storing data. In the embodiment of the present application, the storage medium 508 may refer to an internal memory with a small storage capacity but high speed, and the storage 509 may have a large storage capacity but a slow storage speed. External memory.

The memory 509 can be used to store software programs and modules. The processor 501 executes various functional applications and data processing of the global hook automatic repair device 500 by running the software programs and modules stored in the memory 509. The memory 509 may mainly include a storage program area and a storage data area, where the storage program area can store the operating system, at least one application program required by the function (such as monitoring abnormal functions, etc.), etc.; the storage data area can store automatic repair according to global hooks Data created by the use of the device (such as defining a variable function, etc.), etc. In addition, the memory 509 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other non-volatile solid-state storage devices. The global hook automatic repair method program and the received data stream provided in the embodiment of the present application are stored in the memory, and when needed, the processor 501 calls from the memory 509.

This application also provides a computer-readable storage medium. The computer-readable storage medium may be a non-volatile computer-readable storage medium. The computer-readable storage medium stores instructions. When the instructions run on a computer When, make the computer execute the following steps of the global hook automatic repair method:

Define a loop, which is used to hook all classes;

Define a variable function, which is used to record the name of the class to be hooked;

Determine whether the name of the class to be hooked is in the filter list according to the loop and the variable function;

If the name of the class to be hooked is in the filtering list, the crash class corresponding to the name of the class to be hooked is blocked, and the crash class is the class that caused the crash or exception.

When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website site, computer, server or data center via wired (such as coaxial cable, optical fiber, twisted pair) or wireless (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server or data center integrated with one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, an optical disc), or a semiconductor medium (for example, a solid state disk (SSD)).

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the above-described system, device, and unit can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or It can be integrated into another system, or some features can be ignored or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other media that can store program code .

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present application, not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, a person of ordinary skill in the art should understand that: The technical solutions recorded in the embodiments are modified, or some of the technical features are equivalently replaced; these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A global hook automatic repair method, including:

Define a loop, which is used to hook all classes;

Define a variable function, which is used to record the name of the class to be hooked;

Determine whether the name of the class to be hooked is in the filter list according to the loop and the variable function;

If the name of the class to be hooked is in the filtering list, the crash class corresponding to the name of the class to be hooked is blocked, and the crash class is the class that caused the crash or exception.
The global hook automatic repair method according to claim 1, after judging whether the name of the class to be hooked is in the filter list according to the loop and the variable function, the method further comprises:

If the name of the class to be hooked is not in the filter list, call the loop to hook the class to be hooked.
The method for automatically repairing a global hook according to claim 2, after the shielding the crash class corresponding to the name of the class to be hooked, after the crash class is the class that caused the crash or exception, the method further comprises:

Monitor abnormal function, the abnormal function is used to monitor and record the array corresponding to the crash class;

Determine the name of the crash class in the abnormal function according to the array corresponding to the crash class;

Import the name of the crash category into the filter list.
According to the global hook automatic repair method according to claim 1, said defining a loop, the loop being used to hook all classes includes:

Get the path of the currently running target application;

Acquiring the name and quantity of each class of the target application;

A for loop is defined according to the name and quantity of each class, and the for loop is used to globally hook each class according to the path of the target application.
The method for automatically repairing a global hook according to claim 1, wherein the defining a variable function, the variable function being used to record the name of the class to be hooked includes:

Get the preset key value;

According to the preset key value, call the crash type array stored in the system memory or the preset database;

A variable function is defined according to the array of the crash class, and the variable function is used to record the name of the class to be hooked.
The method for automatically repairing a global hook according to claim 1, wherein the determining whether the name of the class to be hooked is included in the filter list according to the loop and the variable function:

Determine the array called in the loop;

Determine the variable function in the called array;

Determine the name of the class to be hooked in the variable function, and determine whether the name of the class to be hooked is in the filter list.
The method for automatically repairing a global hook according to any one of claims 1-6, the method further comprising:

If the number of crash categories in the filter list is greater than the threshold, the categories that caused the crash are integrated;

Determine the prefix of the crash category of the same type in the crash category;

Block the crash classes with the prefix in batches.
A global hook automatic repair device, including:

The first definition unit is used to define a loop, and the loop is used to hook all classes;

The second definition unit is used to define a variable function, and the variable function is used to record the name of the class to be hooked;

A judging unit, configured to judge whether the name of the class to be hooked is in the filter list according to the loop and the variable function;

The first shielding unit, if the name of the class to be hooked is in the filter list, it is used to shield the crash class corresponding to the name of the class to be hooked, and the crash class is the class that caused the crash or exception .
According to the global hook automatic repair device according to claim 8, the global hook automatic repair device further comprises:

The calling unit is used to call the loop to hook the class to be hooked if the name of the class to be hooked is not in the filter list.
According to the global hook automatic repair device according to claim 9, the global hook automatic repair device further comprises:

The monitoring unit is used for monitoring abnormal functions, and the abnormal functions are used for monitoring and recording the array corresponding to the crash class;

The first determining unit is configured to determine the name of the crash class in the abnormal function according to the array corresponding to the crash class;

The import unit is used to import the name of the crash category into the filter list.
According to the global hook automatic repair device according to claim 8, the first definition unit is specifically used for:

Get the path of the currently running target application;

Acquiring the name and quantity of each class of the target application;

A for loop is defined according to the name and quantity of each class, and the for loop is used to globally hook each class according to the path of the target application.
According to the global hook automatic repair device according to claim 1, the second definition unit is specifically used for:

Get the preset key value;

According to the preset key value, call the crash type array stored in the system memory or the preset database;

A variable function is defined according to the array of the crash class, and the variable function is used to record the name of the class to be hooked.
According to the global hook automatic repair device according to claim 8, the determining unit is specifically configured to:

Determine the array called in the loop;

Determine the variable function in the called array;

Determine the name of the class to be hooked in the variable function, and determine whether the name of the class to be hooked is in the filter list.
According to the global hook automatic repair device according to any one of claims 8-13, the global hook automatic repair device further comprises:

The integration unit, if the number of crash categories in the filter list is greater than the threshold, it is used to integrate the categories that caused the crash;

The second determining unit is used to determine the prefix of the crash category of the same type in the crash category;

The second shielding unit is used to shield the crash classes with the prefix in batches.
A global hook automatic repair device includes a memory, a processor, and a computer program stored on the memory and running on the processor, and the processor implements the following steps when the processor executes the computer program:

Define a loop, which is used to hook all classes;

Define a variable function, which is used to record the name of the class to be hooked;

Determine whether the name of the class to be hooked is in the filter list according to the loop and the variable function;

If the name of the class to be hooked is in the filtering list, the crash class corresponding to the name of the class to be hooked is blocked, and the crash class is the class that caused the crash or exception.
According to the global hook automatic repair device according to claim 15, after the processor executes the computer program to realize the judgment according to the loop and the variable function whether the name of the class to be hooked is in the filter list, It also includes the following steps:

If the name of the class to be hooked is not in the filter list, call the loop to hook the class to be hooked.
According to the global hook automatic repair device according to claim 16, the processor executes the computer program to realize the shielding of the crash class corresponding to the name of the class to be hooked, and the crash class is the one that caused the crash or exception After the class, it also includes the following steps:

Monitor abnormal function, the abnormal function is used to monitor and record the array corresponding to the crash class;

Determine the name of the crash class in the abnormal function according to the array corresponding to the crash class;

Import the name of the crash category into the filter list.
According to the global hook automatic repair device according to claim 17, the processor executes the computer program to realize the definition of a loop, and when the loop is used for hooking all classes, it includes the following steps:

Get the path of the currently running target application;

Acquiring the name and quantity of each class of the target application;

A for loop is defined according to the name and quantity of each class, and the for loop is used to globally hook each class according to the path of the target application.
According to the global hook automatic repair device according to claim 15, the processor executes the computer program to realize the definition of a variable function, and when the variable function is used to record the name of the class to be hooked, it comprises the following steps:

Get the preset key value;

According to the preset key value, call the crash type array stored in the system memory or the preset database;

A variable function is defined according to the array of the crash class, and the variable function is used to record the name of the class to be hooked.
A computer-readable storage medium in which instructions are stored, and when the instructions are run on a computer, the computer executes the following steps:

Define a loop, which is used to hook all classes;

Define a variable function, which is used to record the name of the class to be hooked;

Determine whether the name of the class to be hooked is in the filter list according to the loop and the variable function;

If the name of the class to be hooked is in the filtering list, the crash class corresponding to the name of the class to be hooked is blocked, and the crash class is the class that caused the crash or exception.