CN111552586B - Application crash processing method and device - Google Patents
Application crash processing method and device Download PDFInfo
- Publication number
- CN111552586B CN111552586B CN202010322048.XA CN202010322048A CN111552586B CN 111552586 B CN111552586 B CN 111552586B CN 202010322048 A CN202010322048 A CN 202010322048A CN 111552586 B CN111552586 B CN 111552586B
- Authority
- CN
- China
- Prior art keywords
- crash
- application program
- source code
- reason
- application
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0787—Storage of error reports, e.g. persistent data storage, storage using memory protection
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3628—Software debugging of optimised code
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Stored Programmes (AREA)
Abstract
One embodiment of the present specification provides an application crash processing method and apparatus, where the method includes: acquiring a crash log of an application program reported by a mobile terminal, and determining a crash reason of the application program according to the crash log of the application program; judging whether the crash reason of the application program is the first type crash reason or the second type crash reason; if the source code is the first type of crash reason, determining a modification strategy of the source code of the application program according to the crash reason of the application program and the crash log of the application program; and if the source code is the second type crash reason, determining historical crash processing information corresponding to the crash reason of the application program according to the corresponding relation between each second type crash reason and the historical crash processing information and the crash reason of the application program so as to prompt a developer of the application program to determine a modification strategy of the source code of the application program. By the aid of the method and the device, efficiency of processing application program crash can be improved, and efficient processing of application program crash can be achieved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for processing application crash.
Background
At present, if the application program crashes in the running process, the application program collects crash information and reports the crash information to a server, and the server displays the crash information to developers so that the developers can determine corresponding crash processing schemes. However, this method only waits for the developer to actively check the crash information and manually provide the processing scheme, and thus the processing efficiency of the application crash is low.
Disclosure of Invention
An embodiment of the present disclosure provides a method and an apparatus for processing an application crash, so as to improve efficiency of processing the application crash and achieve efficient processing of the application crash.
To solve the above technical problem, one embodiment of the present specification is implemented as follows:
in a first aspect, an embodiment of the present specification provides an application crash processing method, including:
acquiring a crash log of an application program reported by a mobile terminal, and determining a crash reason of the application program according to the crash log of the application program;
judging whether the crash reason of the application program is a predetermined first type crash reason or a predetermined second type crash reason; wherein the first type of crash cause is a crash cause that can automatically determine a modification policy of source code of the application; the second type of crash reason is a crash reason which needs to manually determine a modification strategy of the source code of the application program;
if the source code is the first type of crash reason, determining a modification strategy of the source code of the application program according to the crash reason of the application program and the crash log of the application program;
and if the source code is the second-class crash reason, determining historical crash processing information corresponding to the crash reason of the application program according to the preset corresponding relationship between each second-class crash reason and the historical crash processing information and the crash reason of the application program so as to prompt a developer of the application program to determine a modification strategy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
In a second aspect, another embodiment of the present specification provides an apparatus for application crash processing, including:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a crash log of an application program reported by a mobile terminal and determining the crash reason of the application program according to the crash log of the application program;
the judging module is used for judging whether the crash reason of the application program is a predetermined first type crash reason or a predetermined second type crash reason; wherein the first type of crash cause is a crash cause that enables automatic determination of a modification policy of source code of the application; the second type of crash reason is a crash reason which needs to manually determine a modification strategy of the source code of the application program;
the first determining module is used for determining a modification strategy of the source code of the application program according to the crash reason of the application program and the crash log of the application program if the first type of crash reason is the first type of crash reason;
and if the second type of crash reason is the second type of crash reason, determining historical crash processing information corresponding to the crash reason of the application program according to the predetermined corresponding relationship between each second type of crash reason and the historical crash processing information and the crash reason of the application program, so as to prompt a developer of the application program to determine a modification strategy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
In a third aspect, a further embodiment of the present specification provides an application crash processing apparatus, including: a memory, a processor and computer executable instructions stored on the memory and executable on the processor, the computer executable instructions when executed by the processor implementing the steps of the application crash handling method as described in the first aspect above.
In a fourth aspect, a further embodiment of the present specification provides a computer-readable storage medium for storing computer-executable instructions which, when executed by a processor, implement the steps of the application crash handling method according to the first aspect.
In an embodiment of the present specification, a crash cause of an application program can be determined according to a crash log of the application program, if the crash cause of the application program is a predetermined first type crash cause, a modification policy of a source code of the application program is determined according to the crash cause of the application program and the crash log of the application program, and if the crash cause of the application program is a predetermined second type crash cause, historical crash processing information corresponding to the crash cause of the application program is determined according to a predetermined correspondence relationship between each second type crash cause and the historical crash processing information and the crash cause of the application program, so as to prompt a developer to determine the modification policy of the source code of the application program. Therefore, according to the embodiment, the crash processing can be automatically performed based on the crash reason of the application program without manual intervention, so that the efficiency of processing the crash of the application program is improved, and the efficient processing of the crash of the application program is realized.
Drawings
In order to more clearly illustrate the technical solutions in one or more embodiments of the present specification, the drawings used in the embodiments or the description of the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings may be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic view of an application scenario of an application crash handling method according to an embodiment of the present disclosure;
FIG. 2 is a flowchart illustrating a method for processing application crash according to an embodiment of the present disclosure;
FIG. 3 is a flowchart illustrating a method for processing application crash according to an embodiment of the present disclosure;
FIG. 4 is a schematic diagram illustrating module components of an application crash processing apparatus according to an embodiment of the present disclosure;
FIG. 5 is a block diagram illustrating an exemplary implementation of an application crash processing apparatus according to another embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an application crash processing device according to an embodiment of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.
Fig. 1 is a schematic view of an application scenario of an application crash processing method provided in an embodiment of the present specification, as shown in fig. 1, the scenario includes a mobile terminal and a server, where the mobile terminal includes, but is not limited to, a tablet computer 101, a mobile phone 102, and a notebook computer 103 shown in fig. 1, and the server includes, but is not limited to, a server 200 shown in fig. 1. The application program is installed and run in the mobile terminal, and the server can execute the application program crash processing method according to an embodiment of the present specification to solve the problem of application program crash.
Fig. 2 is a schematic flowchart of an application crash processing method according to an embodiment of the present disclosure, and as shown in fig. 2, the flowchart includes the following steps:
step S202, obtaining a crash log of the application program reported by the mobile terminal, and determining the crash reason of the application program according to the crash log of the application program;
step S204, judging whether the crash reason of the application program is a predetermined first type crash reason or a predetermined second type crash reason; the first type of crash reason is a crash reason which can automatically determine a modification strategy of source code of an application program; the second type of crash reason is a crash reason which needs to manually determine the modification strategy of the source code of the application program;
step S206, if the first type of crash reason is the first type of crash reason, determining a modification strategy of the source code of the application program according to the crash reason of the application program and the crash log of the application program;
step S208, if the second type of crash cause is the second type of crash cause, determining historical crash processing information corresponding to the crash cause of the application program according to the predetermined corresponding relationship between each second type of crash cause and the historical crash processing information and the crash cause of the application program, so as to prompt a developer of the application program to determine a modification policy of the source code of the application program according to the historical crash processing information corresponding to the crash cause of the application program.
In an embodiment of the present specification, a crash cause of an application program can be determined according to a crash log of the application program, if the crash cause of the application program is a predetermined first type of crash cause, a modification policy of a source code of the application program is determined according to the crash cause of the application program and the crash log of the application program, and if the crash cause of the application program is a predetermined second type of crash cause, historical crash processing information corresponding to the crash cause of the application program is determined according to a predetermined correspondence between each second type of crash cause and the historical crash processing information and the crash cause of the application program, so as to prompt a developer to determine the modification policy of the source code of the application program. Therefore, according to the embodiment, the crash processing can be automatically performed based on the crash reason of the application program without manual intervention, so that the efficiency of processing the crash of the application program is improved, and the efficient processing of the crash of the application program is realized.
In step S202, the server obtains the crash log of the application program reported by the mobile terminal, and determines the crash reason of the application program according to the crash log of the application program.
Specifically, the mobile terminal runs an application program, which may be an application program of a game type, a news type, a shopping type, and the like, but is not limited herein. If the application program is crashed in the running process, the application program can report a crash log to the server. The crash log records details of the crash, including but not limited to the cause of the crash of the application, the method or class performed at the time of the crash, and the method or class performed prior to the crash. For example, taking an example that an application program fails to call method a and causes a crash, the crash log of the application program records that the cause of the crash is a method call failure, records that the crash is caused by a method a call failure when method a is called, and records that method B is called before method a is called.
After receiving the crash log reported by the mobile terminal, the server reads the crash reason of the application program from the crash log, where the crash reason may be recorded at a specific position in the crash log in a character string manner, for example, at a first row of the crash log.
In step S204, the server determines whether the crash cause of the application is a predetermined first crash cause or a predetermined second crash cause.
Specifically, in this embodiment, a first kind of crash cause and a second kind of crash cause are predetermined, the number of the first kind of crash cause may be multiple, and the number of the second kind of crash cause may also be multiple. The first type of crash reason is a crash reason capable of automatically determining a modification policy of the source code of the application program, and the second type of crash reason is a crash reason requiring manual determination of the modification policy of the source code of the application program, that is, when the first type of crash reason is processed, the modification policy of the source code of the application program can be automatically determined, and when the second type of crash reason is processed, the modification policy of the source code of the application program needs to be manually determined.
In a specific example, according to the processing difficulty of the crash reasons, the first type of crash reasons are set to include crash reasons that are relatively easy to process, for example, the method includes: lang. Setting a second type of crash cause includes crash causes that are more difficult to handle, including for example: lan, outofmemoryrer (memory overflow), android, os, deadobjectexception (object does not exist).
In step S204, the crash reason of the application program is compared with each first type crash reason and each second crash reason, if the crash reason of the application program is consistent with a certain first type crash reason, it is determined that the crash reason of the application program is the first type crash reason, and if the crash reason of the application program is consistent with a certain second type crash reason, it is determined that the crash reason of the application program is the second type crash reason. For example, in the above example, if the crash cause of the application is java.
If the cause of the crash of the application is determined to be the first type of crash cause, the step S206 is executed, and if the cause of the crash is determined to be the second type of crash cause, the step S208 is executed.
In step S206, if the crash reason of the application program is the first type of crash reason, the server determines the modification policy of the source code of the application program according to the crash reason of the application program and the crash log of the application program.
Specifically, taking the crash reason of the application program as an example that an unassigned element (i.e., java. lang. nullpointerexception null pointer) exists in the source code of the application program, determining a modification policy of the source code of the application program according to the crash reason of the application program and the crash log of the application program, specifically including:
(a1) reading the name of an unassigned element in a crash log of the application program and reading the position of the unassigned element in a source code of the application program according to the crash reason of the application program;
(a2) determining a modification policy of source code of the application as follows: and prompting a developer of the application program to assign the unassigned elements in the source code of the application program according to the names of the unassigned elements and the positions of the unassigned elements in the source code of the application program.
Specifically, in act (a1), the application's crash log records details of the crash, including but not limited to the cause of the crash, the method or class executed at the time of the crash, and the method or class executed before the crash. For example, in this embodiment, the name of the unassigned element that caused the crash and the location of the unassigned element in the source code of the application are also recorded in the crash log. Based on this, in the above action (a1), according to the crash reason of the application program, the name of the unassigned element and the position of the unassigned element in the source code of the application program are read in the crash log of the application program, and in the specific reading, the character string corresponding to the crash reason is read in the first row of the crash log, according to the read character string corresponding to the crash reason, the content including the character string is searched in the crash log, and the name of the unassigned element and the position of the unassigned element in the source code of the application program are read from the content including the character string.
In one example, through the above action (a1), the name of the unassigned element can be read in the crash log of the application as "A0001" and the position of the unassigned element in the source code of the application as line 501.
Since the null pointer is caused by the element not being assigned, and people other than the developer cannot determine how the element should be assigned, the modification policy for determining the source code of the application in the above action (a2) is: and prompting a developer of the application program to assign the unassigned elements in the source code of the application program according to the names of the unassigned elements and the positions of the unassigned elements in the source code of the application program.
In one example, the specific content of the modification policy of the source code may be as follows: "prompt you to assign value to method A0001 at line 501 of the source code of the application to handle the null pointer crash issue". The modification strategy of the source code can also be notified to developers of the application program through various communication modes such as mails, short messages and the like.
As can be seen, through the above actions (a1) and (a2), for the problem of application null pointer crash, the server can automatically determine the name of the unassigned element and the location of the element in the source code of the application, so as to automatically perform crash processing, improve the efficiency of processing application crash, and implement efficient processing of application crash.
In another embodiment, taking the crash reason of the application as an example of a failure in invoking an object call in an operating system of the mobile terminal (i.e., a failure in invoking the java.lang.classsnotfoundation exception class mentioned above or a failure in invoking the java.lang.nosuch method exception method mentioned above), determining a modification policy of the source code of the application specifically includes:
(b1) reading the name of a first object which fails to be called in a crash log of the application program according to the crash reason of the application program;
(b2) obtaining an operating system source code of a mobile terminal where an application program is located, and searching a name of a second object, of which the similarity with the name of the first object meets a preset similarity requirement, in the operating system source code;
(b3) determining a modification policy of the source code as: the name of the first object is automatically replaced with the name of the second object in the source code of the application.
The mobile terminal is a mobile terminal running the application program. The object that failed the call includes a method or class.
Specifically, in act (b1), the application's crash log records details of the crash, including but not limited to the cause of the crash, the method or class executed during the crash, and the method or class executed before the crash. For example, in this embodiment, the name of the first object that failed to be called is also recorded in the crash log. Based on this, in the above operation (b1), the name of the first object that failed in call is read from the crash log of the application program according to the crash cause of the application program, and specifically, in reading, the character string corresponding to the crash cause is read from the first line in the crash log, the content including the character string is searched for in the crash log according to the read character string corresponding to the crash cause, and the name of the first object that failed in call is read from the content including the character string. Or, the name of the first object with failed call is directly read from the character string corresponding to the crash reason.
In one example, through the above action (B1), the name of the first object with the call failure can be read in the crash log of the application as "B0002".
Then, in the above action (b2), an operating system source code of the mobile terminal where the application program is located is obtained, and a name of a second object whose similarity with the name of the first object meets a preset similarity requirement is searched in the operating system source code. The similarity between the names of two objects can be calculated by adopting a method for calculating text similarity, a similarity threshold value is preset, if the text similarity between the name of a certain object and the name of a first object is found to be higher than the similarity threshold value, the object is determined to be a second object, and the name of the object is determined to be the name of the second object.
The reason why the first object call fails may be that the developer wrote the object name in the source code of the application program, for example, the name of a certain object is "B0003" in the source code of the operating system, and the developer writes "B0002" in the source code of the application program, so that the call of the object in the operating system of the calling mobile terminal fails.
Based on this, in the above action (b3), the modification policy of the source code is determined as follows: the name of the first object is automatically replaced with the name of the second object in the source code of the application. Specifically, if the object call fails due to the fact that the developer wrongly writes the object name in the source code of the application program, the name of the first object may be automatically replaced with the name of the second object in the source code of the application program, so that the name is corrected to make the object call successful. After determining the modification strategy of the source code, the server can also automatically replace the name of the first object with the name of the second object in the source code of the application program according to the scheme, so that the effects of automatic repair without manual intervention and crash are achieved.
In a specific example, the name of the first object is determined to be "callDrawGLFunction" through the above process, and the name of the second object is found to be "callDrawGLFunction 2" in the source code of the operating system, so that the modification policy of the source code is determined as follows: the "callDrawGLFunction" in the source code of the application is replaced with "callDrawGLFunction 2".
In the action (b2), the obtaining of the operating system source code of the mobile terminal where the application program is located specifically includes:
(b21) reading at least one of operating system version information of the mobile terminal, central processing unit architecture information of the mobile terminal and model information of the mobile terminal from a crash log of the application program;
(b22) and searching the operating system source code of the mobile terminal in the database according to the read information.
Specifically, in addition to the above-described content, the crash log of the application program further records operating system version information of the mobile terminal, central processor architecture information of the mobile terminal, and model information of the mobile terminal, where the operating system version information of the mobile terminal may only include official android version information, may only include ROM version information, and may include both official android version information and ROM version information.
In the action (b21), at least one of the operating system version information of the mobile terminal, the Central Processing Unit (CPU) architecture information of the mobile terminal, and the model information of the mobile terminal is read from the crash log of the application program, for example, only the ROM version information is read, or the official android version information and the model information of the mobile terminal are read, or the official android version information, the CPU architecture information of the mobile terminal and the model information of the mobile terminal are read.
After reading the information, in the above-described action (b22), the operating system source code of the mobile terminal is searched for in the database based on the read information. Specifically, the operating system source code of the mobile terminal is stored in the database in advance, and the operating system source code of the mobile terminal may be searched in the database by using the read information, for example, by using the read ROM version information.
As can be seen, through the above actions (b1) to (b3), in order to solve the problem that the application program crashes due to the failed object call in the operating system that calls the mobile terminal, the server can automatically determine the name of the first object that failed call and the name of the second object that may be correct, so as to perform crash processing automatically, improve the efficiency of processing the application program crash, and implement efficient processing of the application program crash.
In step S208, if the second type of crash cause is the second type of crash cause, a predetermined correspondence between each second type of crash cause and the historical crash processing information is obtained, and the historical crash processing information corresponding to the crash cause of the application program is determined according to the correspondence and the crash cause of the application program. The second type of crash cause may be the so-called memory overflow or the absence of objects.
In step S208, determining historical crash processing information corresponding to the crash reason of the application program according to the correspondence and the crash reason of the application program, specifically: and searching historical crash processing information corresponding to the crash reason of the application program in the corresponding relation.
Specifically, the number of the second type crash reasons is multiple, each second type crash reason has corresponding historical crash processing information, for example, the historical crash processing information corresponding to the memory overflow notifies the crash event to the developer of the application program through all preset notification methods (such as mail, short message, and various communication tools), and notifies the developer of the historical processing experience of the crash. The object does not have corresponding historical crash processing information, namely, a notification mode is randomly selected from all preset notification modes to notify a developer of the application program of the crash event, and the developer is notified of historical processing experience of the crash. The historical processing experience for each second type of crash cause may be manually entered into the server and stored.
Therefore, according to the embodiment, the crash processing can be automatically performed for various crash reasons, so that the efficiency of processing the crash of the application program is improved, and the efficient processing of the crash of the application program is realized.
Fig. 3 is a schematic flowchart of an application crash processing method according to an embodiment of the present disclosure, and as shown in fig. 3, the flowchart further includes the following steps based on fig. 2:
step S302, after determining the modification strategy of the source code, if the modification strategy of the source code is used for prompting a developer of the application program to modify the source code of the application program, providing the crash log of the application program and the modification strategy of the source code to the developer of the application program for the developer to refer to;
step S304, after the modification strategy of the source code is determined, if the modification strategy of the source code indicates that the source code of the application program is automatically modified, the source code of the application program is automatically modified according to the modification strategy of the source code, and the crash log of the application program, the modification strategy of the source code and the modified source code of the application program are provided for developers of the application program to confirm.
Specifically, after determining the modification policy of the source code, if the modification policy of the source code is used to prompt a developer of the application program to modify the source code of the application program, for example, the modification policy of the source code is as follows: and prompting a developer of the application program to assign the unassigned elements in the source code of the application program according to the names of the unassigned elements and the positions of the unassigned elements in the source code of the application program. In step S302, the crash log of the application and the modification policy of the source code are provided to the developer of the application for the developer to refer to. The developer can choose whether to modify the source code of the application program or not by referring to the processing scheme.
In addition, after determining the modification policy of the source code, if the modification policy of the source code indicates that the source code of the application program is automatically modified, for example, the modification policy of the source code is as follows: the name of the first object is automatically replaced with the name of the second object in the source code of the application. Automatically modifying the source code of the application program according to the modification strategy of the source code, and providing the crash log of the application program, the modification strategy of the source code and the modified source code of the application program to a developer of the application program for the developer to confirm. The developer can confirm whether the source code of the modified application program is correct.
In step S302, the cause of the crash of the application may also be provided to the developer. Similarly, in step S304, the crash cause of the application program may also be provided to the developer.
As shown in fig. 3, the process in this embodiment further includes:
step S306, after determining the historical crash processing information corresponding to the crash reason of the application program, providing the crash log of the application program and the historical crash processing information corresponding to the crash reason of the application program to a developer of the application program so as to prompt the developer of the application program to determine a modification strategy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
Specifically, as described above, the second type of crash cause is mainly a crash which is difficult to process, and therefore after determining the historical crash processing information corresponding to the crash cause of the application program, the crash log of the application program and the historical crash processing information corresponding to the crash cause of the application program are provided to the developer of the application program for the developer to refer to, so that the developer finally determines how to process the crash of the application program. In step S306, the crash reason of the application program may also be provided to the developer.
Therefore, by the method shown in fig. 3, the crash of the application program can be automatically handled, and a developer can further confirm how to handle the crash of the application program, so as to ensure that the crash of the application program is handled in time.
In summary, with the application crash processing methods shown in fig. 1 to fig. 3, the crash log of the application can be automatically identified and automatically analyzed, the cause of the crash of the application is determined, and the crash of the application is automatically processed based on the cause of the crash of the application, so that an effect of automatically processing the crash of the application without data operation is achieved, and the development efficiency of the application and the stability of the application are improved.
Fig. 4 is a schematic diagram illustrating a module composition of an apparatus for processing application crash according to an embodiment of the present disclosure, as shown in fig. 4, the apparatus includes:
the obtaining module 41 is configured to obtain a crash log of an application program reported by a mobile terminal, and determine a crash reason of the application program according to the crash log of the application program;
a judging module 42, configured to judge whether a crash cause of the application program is a predetermined first crash cause or a predetermined second crash cause; wherein the first type of crash cause is a crash cause that enables automatic determination of a modification policy of source code of the application; the second type of crash reason is a crash reason which needs to manually determine a modification policy of the source code of the application program;
a first determining module 43, configured to determine, if the source code is the first type of crash cause, a modification policy of the source code of the application program according to the crash cause of the application program and the crash log of the application program;
a second determining module 44, configured to determine, if the source code is the second-class crash reason, historical crash processing information corresponding to the crash reason of the application program according to a predetermined correspondence relationship between each second-class crash reason and the historical crash processing information and the crash reason of the application program, so as to prompt a developer of the application program to determine a modification policy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
Optionally, the crash reason of the application is that there are unassigned elements in the source code of the application; the first determining module is specifically configured to: reading the name of the unassigned element and the position of the unassigned element in the source code of the application program in a crash log of the application program according to the crash reason of the application program; determining a modification policy of source code of the application as follows: and prompting a developer of the application program to assign the unassigned elements in the source code of the application program according to the names of the unassigned elements and the positions of the unassigned elements in the source code of the application program.
Optionally, the crash reason of the application program is that the object call in the operating system of the mobile terminal is failed to be called; the object comprises a method or a class; the first determining module is specifically configured to: reading the name of a first object which fails to be called in a crash log of the application program according to the crash reason of the application program; obtaining an operating system source code of a mobile terminal where the application program is located, and searching a name of a second object, of which the similarity with the name of the first object meets a preset similarity requirement, in the operating system source code; determining a modification policy of the source code as: automatically replacing the name of the first object with the name of the second object in source code of the application.
Optionally, the first determining module is further specifically configured to: reading at least one of operating system version information of the mobile terminal, central processing unit architecture information of the mobile terminal and model information of the mobile terminal from a crash log of the application program; and searching the operating system source code of the mobile terminal in a database according to the read information.
Fig. 5 is a schematic diagram illustrating module components of an application crash processing apparatus according to another embodiment of the present disclosure, as shown in fig. 5, the apparatus further includes:
a first providing module 51, configured to, after determining the modification policy of the source code, provide a crash log of the application program and the modification policy of the source code to a developer of the application program if the modification policy of the source code is used to prompt the developer of the application program to modify the source code of the application program; a second providing module 52, configured to, after determining the modification policy of the source code, if the modification policy of the source code indicates that the source code of the application program is automatically modified, automatically modify the source code of the application program according to the modification policy of the source code, and provide the crash log of the application program, the modification policy of the source code, and the modified source code of the application program to a developer of the application program.
Optionally, as shown in fig. 5, the apparatus further includes: a third providing module 53, configured to, after determining historical crash processing information corresponding to a crash reason of the application program, provide the crash log of the application program and the historical crash processing information corresponding to the crash reason of the application program to a developer of the application program, so as to prompt the developer of the application program to determine a modification policy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
In an embodiment of the present specification, a crash cause of an application program can be determined according to a crash log of the application program, if the crash cause of the application program is a predetermined first type of crash cause, a modification policy of a source code of the application program is determined according to the crash cause of the application program and the crash log of the application program, and if the crash cause of the application program is a predetermined second type of crash cause, historical crash processing information corresponding to the crash cause of the application program is determined according to a predetermined correspondence between each second type of crash cause and the historical crash processing information and the crash cause of the application program, so as to prompt a developer to determine the modification policy of the source code of the application program. Therefore, according to the embodiment, the crash processing can be automatically performed based on the crash reason of the application program without manual intervention, so that the efficiency of processing the crash of the application program is improved, and the efficient processing of the crash of the application program is realized.
When it needs to be described, the application crash processing apparatus provided in an embodiment of the present specification can implement each process in the foregoing application crash processing method embodiment, and achieve the same function and effect, which is not repeated here.
Further, an embodiment of the present specification further provides an application crash processing device, and fig. 6 is a schematic structural diagram of the application crash processing device provided in an embodiment of the present specification, as shown in fig. 6, where the device includes: memory 601, processor 602, bus 603, and communication interface 604. The memory 601, processor 602, and communication interface 604 communicate via the bus 603. the communication interface 604 may include input and output interfaces including, but not limited to, a keyboard, mouse, display, microphone, and the like.
In fig. 6, the memory 601 stores thereon computer-executable instructions executable on the processor 602, and when executed by the processor 602, the computer-executable instructions implement the following processes:
acquiring a crash log of an application program reported by a mobile terminal, and determining a crash reason of the application program according to the crash log of the application program;
judging whether the crash reason of the application program is a predetermined first type crash reason or a predetermined second type crash reason; wherein the first type of crash cause is a crash cause that enables automatic determination of a modification policy of source code of the application; the second type of crash reason is a crash reason which needs to manually determine a modification policy of the source code of the application program;
if the source code is the first type of crash reason, determining a modification strategy of the source code of the application program according to the crash reason of the application program and the crash log of the application program;
if the source code is the second type crash reason, determining historical crash processing information corresponding to the crash reason of the application program according to a predetermined corresponding relationship between each second type crash reason and the historical crash processing information and the crash reason of the application program, so as to prompt a developer of the application program to determine a modification strategy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
Optionally, when the computer-executable instructions are executed by the processor, the crash of the application is due to the presence of an unassigned element in the source code of the application; determining a modification strategy of the source code of the application program according to the crash reason of the application program and the crash log of the application program, wherein the modification strategy comprises the following steps: reading the name of the unassigned element in a crash log of the application program and reading the position of the unassigned element in the source code of the application program according to the crash reason of the application program; determining a modification policy of source code of the application as follows: and prompting a developer of the application program to assign the unassigned elements in the source code of the application program according to the names of the unassigned elements and the positions of the unassigned elements in the source code of the application program.
Optionally, when the computer executable instructions are executed by the processor, the crash reason of the application program is that the object call in the operating system of the mobile terminal fails to be called; the object comprises a method or a class; determining a modification policy for source code of the application, comprising: reading the name of a first object which fails to be called in a crash log of the application program according to the crash reason of the application program; obtaining an operating system source code of a mobile terminal where the application program is located, and searching a name of a second object of which the similarity with the name of the first object meets a preset similarity requirement in the operating system source code; determining a modification policy of the source code as: automatically replacing the name of the first object with the name of the second object in source code of the application.
Optionally, when executed by the processor, the computer-executable instructions obtain an operating system source code of the mobile terminal where the application program is located, where the method includes: reading at least one of operating system version information of the mobile terminal, central processing unit architecture information of the mobile terminal and model information of the mobile terminal from a crash log of the application program; and searching the operating system source code of the mobile terminal in a database according to the read information.
Optionally, the computer executable instructions, when executed by the processor, further comprise: after the modification strategy of the source code is determined, if the modification strategy of the source code is used for prompting a developer of the application program to modify the source code of the application program, providing a crash log of the application program and the modification strategy of the source code to the developer of the application program; after the modification strategy of the source code is determined, if the modification strategy of the source code indicates that the source code of the application program is automatically modified, the source code of the application program is automatically modified according to the modification strategy of the source code, and the crash log of the application program, the modification strategy of the source code and the modified source code of the application program are provided for developers of the application program.
Optionally, the computer executable instructions, when executed by the processor, further comprise: after determining the historical crash processing information corresponding to the crash reason of the application program, providing the crash log of the application program and the historical crash processing information corresponding to the crash reason of the application program to a developer of the application program so as to prompt the developer of the application program to determine a modification strategy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
In an embodiment of the present specification, a crash cause of an application program can be determined according to a crash log of the application program, if the crash cause of the application program is a predetermined first type crash cause, a modification policy of a source code of the application program is determined according to the crash cause of the application program and the crash log of the application program, and if the crash cause of the application program is a predetermined second type crash cause, historical crash processing information corresponding to the crash cause of the application program is determined according to a predetermined correspondence relationship between each second type crash cause and the historical crash processing information and the crash cause of the application program, so as to prompt a developer to determine the modification policy of the source code of the application program. Therefore, according to the embodiment, the crash processing can be automatically performed based on the crash reason of the application program without manual intervention, so that the efficiency of processing the crash of the application program is improved, and the efficient processing of the crash of the application program is realized.
When it needs to be described, the application crash processing device provided in an embodiment of the present specification can implement each process in the foregoing application crash processing method embodiment, and achieve the same function and effect, which is not repeated here.
Further, another embodiment of the present specification also provides a computer-readable storage medium for storing computer-executable instructions, which when executed by a processor implement the following process:
acquiring a crash log of an application program reported by a mobile terminal, and determining a crash reason of the application program according to the crash log of the application program;
judging whether the crash reason of the application program is a predetermined first type crash reason or a predetermined second type crash reason; wherein the first type of crash cause is a crash cause that enables automatic determination of a modification policy of source code of the application; the second type of crash reason is a crash reason which needs to manually determine a modification policy of the source code of the application program;
if the source code is the first type of crash reason, determining a modification strategy of the source code of the application program according to the crash reason of the application program and the crash log of the application program;
and if the source code is the second-class crash reason, determining historical crash processing information corresponding to the crash reason of the application program according to the preset corresponding relationship between each second-class crash reason and the historical crash processing information and the crash reason of the application program so as to prompt a developer of the application program to determine a modification strategy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
Optionally, when the computer-executable instructions are executed by a processor, a crash of the application is due to an unassigned element being present in source code of the application; determining a modification strategy of the source code of the application program according to the crash reason of the application program and the crash log of the application program, wherein the modification strategy comprises the following steps: reading the name of the unassigned element in a crash log of the application program and reading the position of the unassigned element in the source code of the application program according to the crash reason of the application program; determining a modification policy of source code of the application as follows: and prompting a developer of the application program to assign the unassigned elements in the source code of the application program according to the names of the unassigned elements and the positions of the unassigned elements in the source code of the application program.
Optionally, when the computer executable instructions are executed by the processor, the crash reason of the application program is that the object call in the operating system of the mobile terminal is failed to be called; the object comprises a method or a class; determining a modification policy for source code of the application, comprising: reading the name of a first object which fails to be called in a crash log of the application program according to the crash reason of the application program; obtaining an operating system source code of a mobile terminal where the application program is located, and searching a name of a second object, of which the similarity with the name of the first object meets a preset similarity requirement, in the operating system source code; determining a modification policy of the source code as: automatically replacing the name of the first object with the name of the second object in source code of the application.
Optionally, when executed by the processor, the computer executable instructions obtain an operating system source code of the mobile terminal where the application program is located, including: reading at least one of operating system version information of the mobile terminal, central processing unit architecture information of the mobile terminal and model information of the mobile terminal from a crash log of the application program; and searching the operating system source code of the mobile terminal in a database according to the read information.
Optionally, the computer executable instructions, when executed by the processor, further comprise: after the modification strategy of the source code is determined, if the modification strategy of the source code is used for prompting a developer of the application program to modify the source code of the application program, providing a crash log of the application program and the modification strategy of the source code to the developer of the application program; after the modification strategy of the source code is determined, if the modification strategy of the source code indicates that the source code of the application program is automatically modified, the source code of the application program is automatically modified according to the modification strategy of the source code, and the crash log of the application program, the modification strategy of the source code and the modified source code of the application program are provided for developers of the application program.
Optionally, the computer executable instructions, when executed by the processor, further comprise: after determining the historical crash processing information corresponding to the crash reason of the application program, providing the crash log of the application program and the historical crash processing information corresponding to the crash reason of the application program to a developer of the application program so as to prompt the developer of the application program to determine a modification strategy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
In an embodiment of the present specification, a crash cause of an application program can be determined according to a crash log of the application program, if the crash cause of the application program is a predetermined first type crash cause, a modification policy of a source code of the application program is determined according to the crash cause of the application program and the crash log of the application program, and if the crash cause of the application program is a predetermined second type crash cause, historical crash processing information corresponding to the crash cause of the application program is determined according to a predetermined correspondence relationship between each second type crash cause and the historical crash processing information and the crash cause of the application program, so as to prompt a developer to determine the modification policy of the source code of the application program. Therefore, according to the embodiment, the crash processing can be automatically performed based on the crash reason of the application program without manual intervention, so that the efficiency of processing the crash of the application program is improved, and the efficient processing of the crash of the application program is realized.
It should be noted that, the storage medium provided in an embodiment of the present specification can implement each process in the foregoing application crash processing method embodiment, and achieve the same function and effect, which is not repeated here.
The computer-readable storage medium includes a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present specification and is not intended to limit the present document. Various modifications and alterations to the embodiments described herein will be apparent to those skilled in the art. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.
Claims (12)
1. An application crash processing method, comprising:
acquiring a crash log of an application program reported by a mobile terminal, and determining a crash reason of the application program according to the crash log of the application program;
judging whether the crash reason of the application program is a predetermined first type crash reason or a predetermined second type crash reason; wherein the first type of crash cause is a crash cause that can automatically determine a modification policy of source code of the application; the second type of crash reason is a crash reason which needs to manually determine a modification policy of the source code of the application program;
if the source code is the first type of crash reason, determining a modification strategy of the source code of the application program according to the crash reason of the application program and the crash log of the application program;
and if the source code is the second-class crash reason, determining historical crash processing information corresponding to the crash reason of the application program according to the preset corresponding relationship between each second-class crash reason and the historical crash processing information and the crash reason of the application program so as to prompt a developer of the application program to determine a modification strategy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
2. The method of claim 1, wherein the crash reason for the application is that there are unassigned elements in the source code of the application; determining a modification strategy of the source code of the application program according to the crash reason of the application program and the crash log of the application program, wherein the modification strategy comprises the following steps:
reading the name of the unassigned element in a crash log of the application program and reading the position of the unassigned element in the source code of the application program according to the crash reason of the application program;
determining a modification policy of source code of the application as follows: and prompting a developer of the application program to assign the unassigned elements in the source code of the application program according to the names of the unassigned elements and the positions of the unassigned elements in the source code of the application program.
3. The method of claim 1, wherein the crash reason for the application is a failure to invoke an object call in an operating system of the mobile terminal; the object comprises a method or a class; determining a modification policy for source code of the application, comprising:
reading the name of a first object which fails to be called in a crash log of the application program according to the crash reason of the application program;
obtaining an operating system source code of a mobile terminal where the application program is located, and searching a name of a second object of which the similarity with the name of the first object meets a preset similarity requirement in the operating system source code;
determining a modification policy of the source code as: automatically replacing the name of the first object with the name of the second object in source code of the application.
4. The method of claim 3, wherein obtaining the operating system source code of the mobile terminal where the application is located comprises:
reading at least one of operating system version information of the mobile terminal, central processing unit architecture information of the mobile terminal and model information of the mobile terminal from a crash log of the application program;
and searching the operating system source code of the mobile terminal in a database according to the read information.
5. The method according to any one of claims 1-4, further comprising:
after the modification strategy of the source code is determined, if the modification strategy of the source code is used for prompting a developer of the application program to modify the source code of the application program, providing a crash log of the application program and the modification strategy of the source code to the developer of the application program;
after the modification strategy of the source code is determined, if the modification strategy of the source code indicates that the source code of the application program is automatically modified, the source code of the application program is automatically modified according to the modification strategy of the source code, and a crash log of the application program, the modification strategy of the source code and the modified source code of the application program are provided for a developer of the application program.
6. The method according to any one of claims 1-4, further comprising:
after determining the historical crash processing information corresponding to the crash reason of the application program, providing the crash log of the application program and the historical crash processing information corresponding to the crash reason of the application program to a developer of the application program so as to prompt the developer of the application program to determine a modification strategy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
7. An application crash processing apparatus, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a crash log of an application program reported by a mobile terminal and determining the crash reason of the application program according to the crash log of the application program;
the judging module is used for judging whether the crash reason of the application program is a predetermined first type crash reason or a predetermined second type crash reason; wherein the first type of crash cause is a crash cause that enables automatic determination of a modification policy of source code of the application; the second type of crash reason is a crash reason which needs to manually determine a modification strategy of the source code of the application program;
the first determining module is used for determining a modification strategy of the source code of the application program according to the crash reason of the application program and the crash log of the application program if the first type of crash reason is the first type of crash reason;
and if the second type of crash reason is the second type of crash reason, determining historical crash processing information corresponding to the crash reason of the application program according to the predetermined corresponding relationship between each second type of crash reason and the historical crash processing information and the crash reason of the application program, so as to prompt a developer of the application program to determine a modification strategy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
8. The apparatus of claim 7, wherein the crash reason for the application is that there are unassigned elements in the source code of the application; the first determining module is specifically configured to:
reading the name of the unassigned element in a crash log of the application program and reading the position of the unassigned element in the source code of the application program according to the crash reason of the application program;
determining a modification policy of source code of the application as follows: and prompting a developer of the application program to assign the unassigned elements in the source code of the application program according to the names of the unassigned elements and the positions of the unassigned elements in the source code of the application program.
9. The apparatus of claim 7, wherein the crash reason for the application is a failure to invoke an object call in an operating system of the mobile terminal; the object comprises a method or a class; the first determining module is specifically configured to:
reading the name of a first object which fails to be called in a crash log of the application program according to the crash reason of the application program;
obtaining an operating system source code of a mobile terminal where the application program is located, and searching a name of a second object, of which the similarity with the name of the first object meets a preset similarity requirement, in the operating system source code;
determining a modification policy of the source code as: automatically replacing the name of the first object with the name of the second object in source code of the application.
10. The apparatus of claim 9, wherein the first determining module is further specifically configured to:
reading at least one of operating system version information of the mobile terminal, central processing unit architecture information of the mobile terminal and model information of the mobile terminal in a crash log of the application program;
and searching the operating system source code of the mobile terminal in a database according to the read information.
11. The apparatus according to any one of claims 7-10, further comprising:
the first providing module is used for providing a crash log of the application program and a modification strategy of the source code to a developer of the application program after the modification strategy of the source code is determined and if the modification strategy of the source code is used for prompting the developer of the application program to modify the source code of the application program;
and the second providing module is used for automatically modifying the source code of the application program according to the modification policy of the source code and providing the crash log of the application program, the modification policy of the source code and the modified source code of the application program to developers of the application program after the modification policy of the source code is determined and if the modification policy of the source code indicates that the source code of the application program is automatically modified.
12. The apparatus of any one of claims 7-10, further comprising:
and a third providing module, configured to provide the crash log of the application program and the historical crash processing information corresponding to the crash reason of the application program to a developer of the application program after determining the historical crash processing information corresponding to the crash reason of the application program, so as to prompt the developer of the application program to determine a modification policy of the source code of the application program according to the historical crash processing information corresponding to the crash reason of the application program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010322048.XA CN111552586B (en) | 2020-04-22 | 2020-04-22 | Application crash processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010322048.XA CN111552586B (en) | 2020-04-22 | 2020-04-22 | Application crash processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111552586A CN111552586A (en) | 2020-08-18 |
| CN111552586B true CN111552586B (en) | 2022-09-30 |
Family
ID=72001349
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010322048.XA Active CN111552586B (en) | 2020-04-22 | 2020-04-22 | Application crash processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111552586B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017219589A1 (en) * | 2016-06-19 | 2017-12-28 | 乐视控股（北京）有限公司 | Method and system for processing program crash message |
| CN108073495A (en) * | 2016-11-18 | 2018-05-25 | 腾讯科技（深圳）有限公司 | The localization method and device of application crash reason |
| CN109298960A (en) * | 2018-08-15 | 2019-02-01 | 中国平安人寿保险股份有限公司 | Application crashes processing method, device, computer installation and storage medium |
| CN109901941A (en) * | 2018-12-15 | 2019-06-18 | 中国平安人寿保险股份有限公司 | Application crash processing method and processing device, computer installation and storage medium |
| CN109918219A (en) * | 2019-01-28 | 2019-06-21 | 努比亚技术有限公司 | Application crashes repair based reminding method, terminal and computer readable storage medium |
| CN110795259A (en) * | 2018-08-01 | 2020-02-14 | 北京京东尚科信息技术有限公司 | Method and device for analyzing application collapse |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9104796B2 (en) * | 2012-12-21 | 2015-08-11 | International Business Machines Corporation | Correlation of source code with system dump information |
| US9442825B2 (en) * | 2013-04-15 | 2016-09-13 | Tencent Technology (Shenzhen) Company Limited | Method and device for signing program crash |
-
2020
- 2020-04-22 CN CN202010322048.XA patent/CN111552586B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017219589A1 (en) * | 2016-06-19 | 2017-12-28 | 乐视控股（北京）有限公司 | Method and system for processing program crash message |
| CN108073495A (en) * | 2016-11-18 | 2018-05-25 | 腾讯科技（深圳）有限公司 | The localization method and device of application crash reason |
| CN110795259A (en) * | 2018-08-01 | 2020-02-14 | 北京京东尚科信息技术有限公司 | Method and device for analyzing application collapse |
| CN109298960A (en) * | 2018-08-15 | 2019-02-01 | 中国平安人寿保险股份有限公司 | Application crashes processing method, device, computer installation and storage medium |
| CN109901941A (en) * | 2018-12-15 | 2019-06-18 | 中国平安人寿保险股份有限公司 | Application crash processing method and processing device, computer installation and storage medium |
| CN109918219A (en) * | 2019-01-28 | 2019-06-21 | 努比亚技术有限公司 | Application crashes repair based reminding method, terminal and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111552586A (en) | 2020-08-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110955409B (en) | Method and device for creating resources on cloud platform | |
| CN113448862B (en) | Software version testing method and device and computer equipment | |
| WO2020000747A1 (en) | Anti-crawler method and terminal and computer readable storage medium | |
| CN107239325B (en) | Document data processing method and device | |
| CN110599305A (en) | Service processing method, device and storage medium | |
| CN112100070A (en) | Version defect detection method and device, server and storage medium | |
| CN111338716A (en) | Data processing method and device based on rule engine and terminal equipment | |
| CN108196975B (en) | Data verification method and device based on multiple checksums and storage medium | |
| CN111552586B (en) | Application crash processing method and device | |
| CN113468212A (en) | Event execution method and device and electronic equipment | |
| CN108111328B (en) | Exception handling method and device | |
| WO2019062020A1 (en) | Asynchronous task unified processing method and apparatus, and storage medium | |
| CN112634973A (en) | Data rereading method and system of storage medium, terminal device and storage medium | |
| CN111367934A (en) | Data consistency checking method, device, server and medium | |
| CN116521405A (en) | sd card state detection method, device, equipment and storage medium | |
| CN110780863A (en) | Cross-platform development method, device, equipment and medium of storage system | |
| CN110688320A (en) | Global variable detection method and device and terminal equipment | |
| CN110647463A (en) | Method and device for restoring test breakpoint and electronic equipment | |
| CN112287643B (en) | Message monitoring method, device, equipment and computer readable storage medium | |
| CN111414270B (en) | Exception handling method and device | |
| CN113609478A (en) | IOS platform application program tampering detection method and device | |
| CN108920219B (en) | Service processing method and device based on open platform | |
| CN112035181A (en) | Method, device, terminal and medium for jumping to application store of android system | |
| CN110727537A (en) | Method and device for uniformly processing response message, computer equipment and storage medium | |
| CN114995861B (en) | Weex-based application program updating method, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |