CN115080297A - Analysis method and device for crash log - Google Patents

Abstract

The application relates to a crash log analysis method and a crash log analysis device. The method comprises the following steps: acquiring an initial crash log and a system file of an application program APP in equipment; modifying the expansion name of the initial crash file to obtain a target crash file; verifying the target crash log based on the system file; and if the target crash log passes the verification, analyzing the target crash log to obtain a target log file, wherein the target log file comprises the accident information of the APP. By adopting the method, the operation difficulty of analyzing the crash logs can be reduced, the labor cost required for analyzing the crash logs is reduced, and the working efficiency of analyzing the crash logs is improved.

Description

Analysis method and device for crash log

technical field

The present application relates to the technical field of artificial intelligence, and in particular, to a crash log parsing method and device thereof.

Background technique

With the rapid development of Internet technology, the electronic equipment industry is also developing rapidly, and the number of applications generated by electronic equipment is also increasing day by day. How to improve the user experience of the application has become the main problem to be solved by the application developers.

There may be some accidents in the daily use of electronic equipment. In order to solve the accident, it is necessary to analyze the crash log corresponding to the accident, and solve the flashback accident according to the analysis result. For example, when an electronic device is in use, a flashback accident may occur. In order to solve the flashback accident, it is necessary to parse the crash log corresponding to the flashback accident, and solve the flashback accident according to the analysis result. In the prior art, developers can perform manual command parsing on crash logs to obtain parsing results.

However, the above-mentioned crash log parsing method is difficult to operate and increases labor costs.

SUMMARY OF THE INVENTION

Based on this, it is necessary to provide a crash log analysis method, apparatus, computer device, computer-readable storage medium and computer program product for the above technical problems.

In a first aspect, the present application provides a crash log parsing method. The method includes:

Get the initial crash log and system files of the application APP in the device;

Modify the extension of the initial crash file to obtain the target crash file;

verifying the target crash log based on the system file;

If the verification is passed, the target crash log is parsed to obtain a target log file, and the target date file includes the accident information of the APP.

In one embodiment, the target crash log is parsed to obtain a target log file, including:

Perform symbolic analysis on the target crash log to obtain the class name and method name of the APP accident;

According to the class name and the method name, an initial log file is generated, and the initial log file is named to obtain the target log file.

In one embodiment, the verifying the target crash log based on the system file includes:

Determine whether the authentication information in the system file is consistent with the authentication information in the target crash file;

If the authentication information in the system file is consistent with the authentication information in the target crash file, it is determined that the authentication is passed;

If the authentication information in the system file is inconsistent with the authentication information in the target crash file, it is determined that the authentication fails.

In one embodiment, the system file includes a program file and a symbol table file, and the determining whether the authentication information in the system file is consistent with the authentication information in the target crash file includes:

Determine whether the authentication information in the program file and the symbol table file is consistent with the authentication information in the target crash file;

If the identity verification information in the program file and the symbol table file is consistent with the identity verification information in the target crash file, it means that the identity verification information in the system file is the same as the identity verification information in the target crash file Verify that the information is consistent.

In one embodiment, it also includes:

If the verification fails, a new target crash file of the APP is re-acquired, and the new target crash file is re-verified based on the system file.

In one embodiment, it includes:

In response to the failure of the identity verification, confirm the reason for the failure of the identity verification;

Based on the reason why the identity verification fails, an error message is outputted.

In one embodiment, the acquisition of the initial crash log and system file of the application APP in the device includes:

obtain a plurality of basic files contained in the device;

displaying the plurality of basic files in the import file preview area of the parsing application program interface, wherein the parsing application program can be installed on the device;

The crash log and the system file in the device are obtained in response to a selected operation on the plurality of base files based on the import file preview area.

In one embodiment, it also includes:

Display the target log file in the generated file preview area of the parsing application program interface;

An export instruction is acquired based on the parsing application program interface, and the target log file is stored according to a target path in response to the export instruction.

In a second aspect, the present application also provides a crash log parsing apparatus. The device includes:

The acquisition module is used to acquire the initial crash log and system files of the application APP in the device;

a modification module, for modifying the extension of the initial crash file to obtain a target crash file;

a verification module, configured to verify the system file based on the target crash log;

A parsing module, configured to parse the system file if the verification is passed, to obtain a target log file, and the target date file includes the accident information of the APP.

In a third aspect, the present application also provides a computer device. The computer device includes a memory and a processor, the memory stores a computer program, and the processor implements the following steps when executing the computer program:

Get the initial crash log and system files of the application APP in the device;

Modify the extension of the initial crash file to obtain the target crash file;

verifying the target crash log based on the system file;

If the verification is passed, the target crash log is parsed to obtain a target log file, and the target date file includes the accident information of the APP.

In a fourth aspect, the present application also provides a computer-readable storage medium. The computer-readable storage medium has a computer program stored thereon, and when the computer program is executed by the processor, the following steps are implemented:

Get the initial crash log and system files of the application APP in the device;

Modify the extension of the initial crash file to obtain the target crash file;

verifying the target crash log based on the system file;

If the verification is passed, the target crash log is parsed to obtain a target log file, and the target date file includes the accident information of the APP.

In a fifth aspect, the present application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the following steps:

Get the initial crash log and system files of the application APP in the device;

Modify the extension of the initial crash file to obtain the target crash file;

verifying the target crash log based on the system file;

If the verification is passed, the target crash log is parsed to obtain a target log file, and the target date file includes the accident information of the APP.

According to the technical solution of the present application, by obtaining the initial crash log and the system file, basic data is provided for the subsequent acquisition of the target log file, and the verification processing of the system file is realized through the target crash file, which ensures the smooth progress of the parsing process and ensures the smooth progress of the subsequent Obtaining the target log file provides guarantee; by parsing the system file, the target log file is obtained, which reduces the operational difficulty of crash log parsing, reduces the labor cost required for parsing crash logs, and increases the work efficiency of parsing crash logs.

Description of drawings

FIG. 1 is an example diagram of a method for parsing a crash log provided by an embodiment of the present application;

2 is a flowchart of a method for parsing a crash log provided by an embodiment of the present application;

3 is a flowchart of another crash log parsing method provided by an embodiment of the present application;

4 is a flowchart of another crash log parsing method provided by an embodiment of the present application;

5 is a flowchart of another crash log parsing method provided by an embodiment of the present application;

6 is a flowchart of another crash log parsing method provided by an embodiment of the present application;

FIG. 7 is a design diagram of a parsing application program interface provided by an embodiment of the present application;

8 is a flowchart of another crash log parsing method provided by an embodiment of the present application;

FIG. 9 is a structural block diagram of an apparatus for parsing a crash log provided by an embodiment of the present application;

10 is a structural block diagram of another crash log parsing apparatus provided by an embodiment of the present application;

11 is a structural block diagram of another crash log parsing apparatus provided by an embodiment of the present application;

12 is a structural block diagram of another crash log parsing apparatus provided by an embodiment of the present application;

Figure 13 is a diagram of the internal structure of a computer device in one embodiment.

reference number

1. Import file preview area; 2. Edit control; 3. Delete control; 4. Import control; 5. Alternative area; 6. Generate file preview area; 7. Export control.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application will be described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application.

In the description of this application, references to the terms "one embodiment," "some embodiments," "example," "specific example," or "some examples", etc. refer to the specific features described in connection with the embodiment or example. , structure, material or feature is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, those skilled in the art may combine and combine the different embodiments or examples described in this specification, as well as the features of the different embodiments or examples, without conflicting each other.

And, in the description of this application, unless otherwise specified, "/" means or means, for example, A/B can mean A or B; "and/or" in this document is only an association to describe the associated object Relation, it means that there can be three kinds of relations, for example, A and/or B can mean that A exists alone, A and B exist at the same time, and B exists alone. The first, second, and other numeral numbers involved in the present application are only for the convenience of description, and are not used to limit the scope of the embodiments of the present application, nor do they indicate the order of precedence.

As shown in Figure 1, when the user's device is in daily use, an accident occurs in the application APP installed in the user's device. At this time, the developer's device receives the initial crash log and system file sent by the accident application APP. The parsing application is installed on the device of the developer. The parsing application obtains the initial crash log and system file from the data storage system of the developer's device, and modifies the extension of the initial crash file to obtain the target crash file. Based on the system file verification The target crash file belongs to the same device and the same application APP. If the verification is passed, the target crash log is symbolized to obtain the class name and method name of the accident. So far, the analysis of the initial crash log is completed.

In the actual use process, electronic equipment may encounter some accidents in the daily use process. In order to solve the accident, the developer needs to parse the crash log manually to obtain the parsing result. However, the manual parsing method is difficult to operate. , increasing labor costs.

Based on the above problems, the present application discloses a crash log parsing method and device. By obtaining an initial crash log and a system file, a target crash log is obtained based on the initial crash log, and the target crash log is verified based on the system file. If passed, the target crash log is parsed, and the target log file is finally obtained. Specifically, a crash log parsing method according to an embodiment of the present application is described below with reference to the accompanying drawings.

2 is a flowchart of a method for parsing a crash log provided by an embodiment of the present application. As shown in FIG. 1 , the method for parsing a crash log includes the following steps:

Step 201: Obtain an initial crash log and system file of an application program APP in the device.

Among other things, the devices may be various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. A device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smart phones, wearable devices, and other similar computing devices.

Optionally, the initial crash log is a file whose extension may be ".ips", and the system file may include: a program file and a symbol table file.

In an embodiment of the present application, it is assumed that the crash log parsing method of the embodiment of the present application can be applied to a device, and a parsing application program is installed on the device. Select, get and resolve.

As an implementation manner, the present application can obtain the initial crash log and system file by setting the information receiving column in the parsing application program interface. When an accident occurs in the application program APP (Application program) in a certain device, the The device can obtain the initial crash log and system file of the accident application APP, and display the initial crash log and system file in the information receiving column, thereby realizing the operation of obtaining the initial crash log and system file.

For example, when an accident occurs when a smartphone is running a short video application, the device can obtain the initial crash log and system file of the short video application, and store the initial crash log and system file of the short video application. Displayed in the information receiving bar, thereby realizing the acquisition of the initial crash log and system files of the short video application in the smartphone. As another implementation manner, the present application can realize the acquisition of initial crash logs and system files by setting a database and a search bar in the parsing application, wherein several initial crash logs and several system files can be stored in the database, and the database can realize For the addition and deletion of initial crash logs and system files, when a certain initial crash log and a certain system file need to be obtained, the initial crash log that best matches the search criteria can be displayed to the user according to the search criteria in the search bar. and system files. The user can select the most suitable initial crash log and system file according to the actual situation, and realize the operation of obtaining the initial crash log and system file. The search conditions may include: the storage time of the initial crash log and the system file, keywords contained in the naming of the initial crash log and the system file, and the like.

For example, when you need to obtain the initial crash log and system file of a short video application in a smartphone, enter the initial crash log and the storage time of the system file in the search bar to obtain a smartphone in the database. Initial crash log and system files for the short video application in .

Step 202: Modify the extension of the initial crash file to obtain the target crash file.

For example, the extension name of the initial crash file is ".ips", but the initial crash file with the extension name ".ips" cannot be visualized, that is, the initial crash file cannot be opened, and subsequent operations cannot be performed based on the initial crash file. Operation process; in order to ensure that the initial crash file can be visualized, and the subsequent implementation can verify the initial crash file according to the system file, the extension name of the initial crash file needs to be changed to ".crash", where the extension name is ". crash” is the initial crash file, which is the target crash file.

Step 203, verifying the target crash date based on the system file log.

It should be noted that, in order to ensure the subsequent analysis and processing of the crash log, it is necessary to ensure that the target crash log and the system file correspond to each other. If the target crash log and the system file do not correspond to each other, the subsequent analysis and processing of the crash log cannot be realized. .

Among them, the target crash log and the system file correspond to each other means: the target crash log and the system file belong to the same device and the same application APP; the target crash log and the system file do not correspond to each other refers to: the target crash log and the system file Do not belong to the same device, and/or, do not belong to the same application APP.

For example, if the target crash log belongs to device A and the system file also belongs to device A, but the target crash log belongs to application M in device A, and the system file belongs to application N in device A, it proves that the target crash log is related to the system The files do not correspond to each other.

In an embodiment of the present application, optionally, by obtaining the first verification information in the target crash log and the second verification information in the system file, and verifying whether the first verification information is consistent with the second verification information, Then it is judged whether the verification of the target crash log by the system file is passed. If the first verification information is consistent with the second verification information, it means that the verification of the target crash log by the system file is passed; if the first verification information is inconsistent with the second verification information, then Indicates that system file validation of the target crash log failed.

Step 204, if the verification is passed, parse the target crash log to obtain a target log file, and the target date file includes the accident information of the APP.

The accident information of the APP may include, but is not limited to: the location coordinates of the accident in the APP, the cause of the accident in the APP, the time when the accident occurred in the APP, and the like.

In an embodiment of the present application, by performing parsing processing on the target crash log, the symbolic processing of the target crash log is realized, so that the data in the target crash log, and thus the hexadecimal data, is parsed into the accident occurred in the APP. Position coordinates. Optionally, the location coordinates of the accident in the APP may include, but are not limited to, the class name and method name of the accident.

According to the analysis method of the crash log of the present application, by obtaining the initial crash log and the system file, basic data is provided for the subsequent acquisition of the target log file, and the verification processing of the system file is realized through the target crash file, so as to ensure the smooth progress of the analysis process. The target log file can be successfully obtained in the follow-up to provide guarantee; by parsing the system file, the target log file can be obtained, which reduces the operational difficulty of crash log parsing, reduces the labor cost required for parsing crash logs, and increases the work of parsing crash logs. efficiency.

It should be noted that the target log file can be obtained by performing symbolic parsing processing on the system file. Optionally, as shown in FIG. 3 , FIG. Flow chart, the method includes the following steps:

Step 301 , perform symbolic analysis based on the target crash log to obtain the class name and method name of the APP accident.

It should be noted that by performing symbolic analysis on the target crash log, symbolic analysis of the hexadecimal data in the target crash log is realized, so as to obtain the class name and method name of the APP accident.

It should be noted that, in order to ensure that the parsing operation of the target crash log can be successfully completed, it is necessary to read the parsing tool based on the target crash log, and realize the parsing operation of the target crash log through the parsing tool, wherein the parsing tool includes the symbolicatecrash tool.

Step 302: Generate an initial log file according to the class name and method name, and perform naming processing on the initial log file to obtain a target log file.

It should be noted that by summarizing the class name and method name, the class name and method name are stored in the same file, and the file is the initial log file. It can be understood that the initial log file includes the class name and method. name.

In an embodiment of the present application, the present application can set a name modification control in the parsing application program interface. When the name of the initial log file needs to be modified, the name modification control of the parsing application program interface can be triggered to open the initial log file. When the modification is completed, the name modification control of the parsing application interface is triggered again, the name of the modified initial log file is saved, and the name modification function of the initial log file is turned off.

For example, assuming that the initial name of the initial log file is 'file 1', when the name of the initial log file needs to be modified, trigger the name modification control of the parsing application interface, enable the name modification function of the initial log file, and enter the modified name After 'file 2', trigger the name modification control of the parsing application interface again to save the name of the modified initial log file.

According to the crash log parsing method of the present application, by performing symbolic parsing of the target crash log, the acquisition of the class name and the method name is completed, thereby realizing the determination of the accident location of the APP, and reducing the labor cost required for parsing the crash log. , which increases the efficiency of parsing crash logs. In addition, by performing naming processing on the initial log file, the convenience of operation is increased, so that the user can rename the initial log file according to actual needs.

It should be noted that the verification of the system file in the target crash log can be realized by comparing the authentication information of the system file and the authentication information of the target crash log. Optionally, as shown in FIG. 3 , FIG. 4 is implemented for this application. The flow chart of another crash log parsing method provided by the example includes the following steps:

Step 401: Determine whether the authentication information in the system file is consistent with the authentication information in the target crash file.

It should be noted that the authentication information of the system file is used to determine the device to which the system file belongs and the application APP to which the system file belongs, and the authentication information of the system file may include: the identity information of the device corresponding to the system file and the system file The identity information of the corresponding application APP.

It should be noted that the authentication information of the target crash file is used to determine the device to which the target crash file belongs and the application APP to which the target crash file belongs, and the authentication information of the target crash file may include: The identity information and the target crash file correspond to the identity information of the application APP.

In an embodiment of the present application, the authentication information of the system file and the authentication information of the target crash file are obtained, and based on the authentication information of the system file and the authentication information of the target crash file, the device and device to which the system file belongs are determined. The application APP to which the target crash file belongs, and the device to which the target crash file belongs and the application APP to which it belongs, by comparing whether the device to which the system file belongs is the same as the device to which the target crash file belongs, and comparing the application APP to which the system file belongs and the target Check whether the APP to which the crash file belongs is consistent, and judge whether the authentication information in the system file is consistent with the authentication information in the target crash file.

It should be noted that if the authentication information in the system file is consistent with the authentication information in the target crash file, the verification is passed; if the authentication information in the system file is inconsistent with the authentication information in the target crash file, the verification fails. pass.

The fact that the authentication information in the system file is consistent with the authentication information in the target crash file means that the application APP to which the system file belongs is consistent with the application APP to which the target crash file belongs, and the authentication information in the system file is consistent Consistent with the authentication information in the target crash file; inconsistency between the authentication information in the system file and the authentication information in the target crash file means that the application APP to which the system file belongs is inconsistent with the application APP to which the target crash file belongs. And/or, the authentication information in the system file does not match the authentication information in the target crash file.

For example, when it is necessary to judge that the system file is verified based on the target crash log, the authentication information in the system file and the authentication information in the target crash file are obtained, and based on the authentication information in the system file, it is determined that the system file belongs to A device and The B application APP determines that the target crash file belongs to the A device and the C application APP based on the authentication information in the target crash file. Therefore, it can be determined that the target crash file and the system file do not belong to the same application APP, that is, the identity in the system file. If the authentication information is inconsistent with the authentication information in the target crash file, the authentication fails.

In an embodiment of the present application, the system file is verified based on the target crash log, and the identity information of the device to which the system file belongs is obtained by acquiring the identity verification information in the system file and based on the identity verification information in the system file. and the identity information of the application APP to which the system file belongs; according to the identity information of the device to which the system file belongs and the identity information of the application APP to which the system file belongs, look for the identity information of the same device and the identity of the application APP in the target crash file. information, if the identity information of the same device and the identity information of the application APP exist in the target crash file, the verification is determined to be passed; if the identity information of the same device does not exist in the target crash file, and/or, the same application does not exist If the identity information of the program APP is used, it is determined that the verification has not passed.

It should be noted that system files include program files and symbol table files. When judging whether the authentication information in the system file is consistent with the authentication information in the target crash file, it can be understood as: judging whether the authentication information in the program file and the symbol table file is consistent with the authentication information in the target crash file; If the authentication information in the program file and the symbol table file is consistent with the authentication information in the target crash file, it means that the authentication information in the system file is consistent with the authentication information in the target crash file.

For example, in response to judging whether the authentication information in the system file is consistent with the authentication information in the target crash file, it is respectively determined whether the authentication information in the program file is consistent with the authentication information in the target crash file, and the symbol table Whether the authentication information in the file is consistent with the authentication information in the target crash file, only the authentication information in the program file is consistent with the authentication information in the target crash file, and the authentication information in the symbol table file is the same as that in the target crash file. If the authentication information in the crash file is inconsistent, it proves that the authentication information in the system file is inconsistent with the authentication information in the target crash file.

It should be noted that if the verification fails, the new target crash file of the APP is re-acquired, and the new target crash file is re-verified based on the system file.

The new target crash file is a file different from the target crash file that fails the verification, that is, the new target crash file and the target crash file that fails the verification are different files.

It should be noted that, in response to the failure of the authentication, the reason for the failure of the authentication is confirmed; based on the reason for the failure of the authentication, an error message is output.

In some embodiments of the present application, the present application can set an error reporting prompt area in the parsing application program interface, and the error reporting prompt area can display prompt information and display the reason why the identity verification failed.

In some embodiments of the present application, there are many forms of outputting error reporting reminder information, wherein, the forms of outputting error reporting reminder information may include but are not limited to: LED (light-emitting diode) prompts, email prompts, and telephone prompts; wherein , LED prompt is specifically used: when the authentication fails, confirm the reason for the failure of the authentication, and the LED can display different luminous colors according to different reasons for the failure of the authentication, for example: green represents the program file authentication information and the target crash The authentication information in the file is inconsistent, and red indicates that the authentication information in the symbol table file is inconsistent with the authentication information in the target crash file. And then realize the output of error reminder information to the on-site personnel through the light of different colors. The email prompt is specifically used to: when the identity verification fails, confirm the reason for the failure of the identity verification, and send the reason for the failure of the identity verification to the preset email address in the form of email through the network, so as to realize the output of the error message. The phone prompt is specifically used to: when the identity verification fails, confirm the reason for the failure of the identity verification, and dial the preset mobile phone number to receive the alarm as soon as possible. Reminder information.

According to the analysis method of the crash log of the present application, by verifying the target crash log based on the system file, it is ensured that the target log file can be obtained smoothly in the follow-up, the smooth progress of the analysis process is ensured, the possibility of successful analysis is increased, and the realization of The automatic verification of the target crash log reduces the operational difficulty of crash log parsing, reduces the labor cost required for parsing the crash log, and increases the work efficiency of parsing the crash log.

It should be noted that the initial crash log and the system file can be obtained through the file preview area. Optionally, as shown in FIG. 5 , FIG. 5 is a flow of another crash log parsing method provided by this embodiment of the present application. Figure, the method includes the following steps:

Step 501: Acquire multiple basic files included in the device.

The multiple basic files refer to multiple initial crash logs and multiple system files that are not selected by the user.

It should be noted that a plurality of basic files can be stored in the local hardware of the device, and/or in an online database, and the storage location of the basic files can be independently selected according to the actual situation.

Step 502, displaying a plurality of basic files in the import file preview area of the parsing application interface, wherein the parsing application can be installed on the device.

It should be noted that the multiple basic files in the file preview area are arranged in sequence according to a preset sorting rule, and the file preview area can display the file extension and file name of the basic files. Wherein, the sorting rules may include but are not limited to: sorting according to the storage time sequence of the basic files, sorting according to the first letters of the file names of the basic files, and the like.

In an embodiment of the present application, as shown in FIG. 5 , the present application can implement editing operations on multiple basic files in the file preview area by setting the editing control 2 and the deletion control 3 in the parsing application program. When editing the basic file, trigger the editing control 2 to realize the editing function of opening the file preview area. At this time, select the basic file to be deleted, and trigger the deletion control 3, so as to realize the deletion operation of the basic file. After the deletion is completed , trigger the editing control 2 again to close the editing function of the file preview area.

Step 503 , in response to the selected operation on the plurality of basic files based on the import file preview area, obtain crash logs and system files in the device.

In an embodiment of the present application, as shown in FIG. 7 , the present application can obtain crash logs and system files by setting an editing control 2 and an importing control 4 in the parsing application. When it is necessary to obtain the crash log and system file, trigger the editing control 2 to realize the editing function of opening the file preview area. At this time, select the crash log and system file to be imported, and trigger the import control 4, so as to realize the selection of the selected crash log and system file. The crash log and system files are imported. When the import is completed, the editing control 2 is triggered again to close the editing function of the file preview area.

In an embodiment of the present application, as shown in FIG. 7 , the present application can obtain crash logs and system files by setting an editing control 2 and an alternative area 5 in the parsing application. When you need to get the crash log and system file, trigger the editing control 2 to realize the editing function of opening the file preview area. At this time, double-click to trigger the crash log and system file to be imported, and save the selected crash log and system file to the backup. Selection area 5, after the selection is completed, trigger the editing control 2 again, close the editing function of the file preview area, and import the file in the selection area 5.

According to the crash log parsing method of the present application, by setting the import file preview area, it is convenient for users to perform operations in the crash log parsing process, which reduces the operational difficulty of parsing crash logs and increases work efficiency.

It should be noted that the storage of the target log file can be realized by generating a file preview area. Optionally, as shown in FIG. 6 , FIG. 6 is a flowchart of another crash log parsing method provided by the embodiment of the present application, The method includes the following steps:

Step 601, displaying the target log file in the generated file preview area of the parsing application interface.

It should be noted that the user can check the target log file through the generated file preview area. If the target log file is checked correctly, the next steps can be performed. If the target log file is checked incorrectly, the delete control can be triggered. The target log file is deleted, and the target log file is retrieved.

In an embodiment of the present application, as shown in FIG. 7 , the present application can implement the delete operation on the target log file by setting the delete control 3 in the parsing application program. After the acquisition of the target log file is completed, the generated file preview area 6 displays the target log file, and the user checks the target log file based on the generated file preview area 6. If there is an error in the target log file, the delete control 3 is triggered to realize the deletion of the target log file. delete operation.

Step 602: Obtain an export instruction based on the parsing application program interface, and store the target log file according to the target path in response to the export instruction.

Among them, in an embodiment of the present application, as shown in FIG. 7 , by setting an export control 7 in the parsing application program, the target log file can be stored according to the target path. When the acquisition of the target log file is completed, the target log file can be stored. The log file is displayed in the generated file preview area 6. When the target log file is checked and found to be correct, the export control 7 is triggered, and then the generated file preview area 6 pops up a storage path preview box. The user can store the target log file in the storage path preview box. The path is modified, and when the export control 7 is triggered again, the target log file is stored according to the target path.

According to the crash log parsing method of the present application, by setting the import file preview area and the generated file preview area, it is convenient for users to perform operations in the crash log parsing process, which reduces the operational difficulty of parsing crash logs and increases work efficiency.

In an embodiment of the present application, as shown in FIG. 8 , when the user's device is in daily use, an accident occurs in the application program APP installed in the user's device:

Step 1: The initial crash log and system file of the accident application APP are analyzed through the import file preview area of the application to complete the import operation of the initial crash log and system file; wherein, the system file includes: program file and symbol table file.

Step 2: Modify the extension of the initial crash file to obtain a target crash file, and obtain a parsing tool based on the target crash file, wherein the parsing tool includes a symbolicatecrash tool.

Step 3: Verify the target crash file based on the system file. If the verification fails, the user is prompted to re-import the system file, or the system file is modified in the import file preview area of the parsing application.

Step 4: If the verification is passed, the target crash log is symbolized to obtain the target log file of the accident, and the name of the target log file can be modified, wherein the target log file includes: class name and method name.

Step 5: The generated file preview area displays the generated target log file.

Step 6: Export the generated file preview area to the specified directory or customize the export path through the generated file preview area.

It should be understood that, although the steps in the flowcharts involved in the above embodiments are sequentially displayed according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, the execution of these steps is not strictly limited to the order, and these steps may be performed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same time, but may be executed at different times. The order of execution of these steps or stages is also not necessarily sequential, but may be performed alternately or alternately with other steps or at least a portion of the steps or stages in the other steps.

Based on the same inventive concept, an embodiment of the present application further provides a crash log parsing apparatus for implementing the above-mentioned crash log parsing method. The implementation solution for solving the problem provided by the device is similar to the implementation solution described in the above method, so the specific limitations in the embodiment of the device for parsing one or more crash logs provided below can refer to the analysis of the crash log above. The limitation of the method is not repeated here.

In one embodiment, as shown in FIG. 9, FIG. 9 is a structural block diagram of a crash log parsing apparatus provided by an embodiment of the present application, which provides a crash log parsing apparatus, including: an acquisition module 910, a modification module 920, a verification module 930 and a parsing module 940, wherein:

The obtaining module 910 is configured to obtain the initial crash log and system file of the application program APP in the device.

The modification module 920 is configured to modify the extension of the initial crash file to obtain the target crash file.

The verification module 930 is configured to verify the system file based on the target crash log.

The parsing module 940 is configured to parse the system file if the verification is passed to obtain a target log file, and the target date file includes the accident information of the APP.

It should be noted that the target log file is displayed in the generated file preview area of the parsing application program interface; the export instruction is obtained based on the parsing application program interface, and the target log file is stored according to the target path in response to the export instruction.

According to the crash log parsing device of the present application, by acquiring the initial crash log and the system file, basic data is provided for the subsequent acquisition of the target log file, and the verification processing of the system file is realized through the target crash file, which ensures the smooth progress of the parsing process, and The target log file can be successfully obtained in the follow-up to provide guarantee; by parsing the system file, the target log file can be obtained, which reduces the operational difficulty of crash log parsing, reduces the labor cost required for parsing crash logs, and increases the work of parsing crash logs. efficiency.

In some embodiments of the present application, as shown in FIG. 10 , FIG. 10 is a structural block diagram of another crash log parsing apparatus provided by an embodiment of the present application. The parsing module 1040 in the crash log parsing apparatus includes: a parsing unit 1041 and generating unit 1042.

The parsing unit 1041 is configured to perform symbolic parsing on the target crash log to obtain the class name and method name of the APP accident.

The generating unit 1042 is configured to generate an initial log file according to the class name and the method name, and perform a naming process on the initial log file to obtain a target log file.

Among them, 1010-1030 in FIG. 10 and 910-930 in FIG. 9 have the same function and structure.

According to the crash log parsing device of the present application, by performing symbolic parsing of the target crash log, the acquisition of the class name and the method name is completed, thereby realizing the determination of the accident location of the APP, and reducing the labor cost required for parsing the crash log. , which increases the efficiency of parsing crash logs. In addition, by performing naming processing on the initial log file, the convenience of operation is increased, so that the user can rename the initial log file according to actual needs.

In some embodiments of the present application, as shown in FIG. 11 , FIG. 11 is a structural block diagram of another crash log parsing apparatus provided by an embodiment of the present application. The verification module 1130 in the crash log parsing apparatus includes: a judging unit 1131.

The determining unit 1131 is configured to determine whether the authentication information in the system file is consistent with the authentication information in the target crash file.

It should be noted that if the authentication information in the system file is consistent with the authentication information in the target crash file, it is determined that the verification is passed; if the authentication information in the system file is inconsistent with the authentication information in the target crash file, it is determined that Verification failed.

It should be noted that the system files include program files and symbol table files; determine whether the authentication information in the program files and symbol table files is consistent with the authentication information in the target crash file; if the authentication information in the program files and symbol table files is consistent If the information is consistent with the authentication information in the target crash file, it means that the authentication information in the system file is consistent with the authentication information in the target crash file.

In an embodiment of the present application, if the verification fails, a new target crash file of the APP is re-acquired, and the new target crash file is re-verified based on the system file.

In an embodiment of the present application, in response to the failure of the identity verification, the reason for the failure of the identity verification is confirmed; based on the reason for the failure of the identity verification, an error notification message is output.

Among them, 1110, 1120 and 1140 in FIG. 11 and 1010, 1020 and 1040 in FIG. 10 have the same function and structure.

According to the crash log parsing device of the present application, by verifying the target crash log based on the system file, it is ensured that the target log file can be obtained smoothly in the follow-up, the parsing process is ensured smoothly, the possibility of successful parsing is increased, and the The automatic verification of the target crash log reduces the operational difficulty of crash log parsing, reduces the labor cost required for parsing the crash log, and increases the work efficiency of parsing the crash log.

In some embodiments of the present application, as shown in FIG. 12 , FIG. 12 is a structural block diagram of another crash log parsing apparatus provided by an embodiment of the present application. The obtaining module 1212 in the crash log parsing apparatus includes: an obtaining unit 1211 , a display unit 1212 and an acquisition unit 1213 .

Wherein, the obtaining unit 1211 is configured to obtain a plurality of basic files included in the device.

The display unit 1212 is configured to display a plurality of basic files in the import file preview area of the parsing application interface, wherein the parsing application can be installed on the device.

The obtaining unit 1213 is configured to obtain the crash log and the system file in the device in response to the selected operation on the plurality of basic files based on the import file preview area.

Among them, 1220-1240 in FIG. 12 and 1120-1140 in FIG. 11 have the same function and structure.

According to the crash log parsing device of the present application, by setting the import file preview area and the generated file preview area, it is convenient for users to perform operations in the crash log parsing process, which reduces the operational difficulty of parsing crash logs and increases work efficiency.

Each module in the above crash log parsing apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

In one embodiment, a computer device is provided, and the computer device may be a server, and its internal structure diagram may be as shown in FIG. 13 . The computer device includes a processor, memory, and a network interface connected by a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes non-volatile storage media and internal memory. The nonvolatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the execution of the operating system and computer programs in the non-volatile storage medium. The computer device's database is used to store crash log parsing data. The network interface of the computer device is used to communicate with an external terminal through a network connection. The computer program is executed by the processor to implement a crash log analysis method.

In one embodiment, a computer device is provided, the computer device may be a terminal, and its internal structure diagram may be as shown in FIG. 13 . The computer equipment includes a processor, memory, a communication interface, a display screen, and an input device connected by a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium, an internal memory. The nonvolatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the execution of the operating system and computer programs in the non-volatile storage medium. The communication interface of the computer equipment is used for wired or wireless communication with an external terminal, and the wireless communication can be realized by WIFI, mobile cellular network, NFC (Near Field Communication) or other technologies. The computer program is executed by the processor to implement a crash log analysis method. The display screen of the computer equipment may be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment may be a touch layer covered on the display screen, or a button, a trackball or a touchpad set on the shell of the computer equipment , or an external keyboard, trackpad, or mouse.

Those skilled in the art can understand that the structure shown in FIG. 13 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. Include more or fewer components than shown in the figures, or combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, including a memory and a processor, a computer program is stored in the memory, and the processor implements the following steps when executing the computer program:

Get the initial crash log and system files of the application APP in the device;

Modify the extension of the initial crash file to get the target crash file;

Validate target crash logs based on system files;

If the verification is passed, the target crash log is parsed to obtain the target log file, and the target date file includes the accident information of the APP.

In one embodiment, the processor further implements the following steps when executing the computer program:

Symbolically parse the target crash log to get the class name and method name of the APP accident;

According to the class name and method name, the initial log file is generated, and the initial log file is named to obtain the target log file.

In one embodiment, the processor further implements the following steps when executing the computer program:

Determine whether the authentication information in the system file is consistent with the authentication information in the target crash file;

If the authentication information in the system file is consistent with the authentication information in the target crash file, it is determined that the authentication is passed;

If the authentication information in the system file is inconsistent with the authentication information in the target crash file, it is determined that the authentication fails.

In one embodiment, the processor further implements the following steps when executing the computer program: wherein the system file includes a program file and a symbol table file;

Determine whether the authentication information in the program file and the symbol table file is consistent with the authentication information in the target crash file;

If the authentication information in the program file and the symbol table file is consistent with the authentication information in the target crash file, it means that the authentication information in the system file is consistent with the authentication information in the target crash file.

In one embodiment, the processor further implements the following steps when executing the computer program:

If the verification fails, the new target crash file of the APP is re-acquired, and the new target crash file is re-verified based on the system file.

In one embodiment, the processor further implements the following steps when executing the computer program:

In response to the authentication failure, confirm the reason why the authentication failed;

An error message is output based on the reason why the authentication failed.

In one embodiment, the processor further implements the following steps when executing the computer program:

Get multiple base files contained in the device;

Display multiple base files in the import file preview area of the parsing application interface, where the parsing application can be installed on the device;

Crash logs and system files in the device are obtained in response to selected operations on the plurality of underlying files based on the import file preview area.

In one embodiment, the processor further implements the following steps when executing the computer program:

Display the target log file in the generated file preview area of the parsing application interface;

Obtain the export instruction based on the parsing application program interface, and store the target log file according to the target path in response to the export instruction.

In one embodiment, a computer-readable storage medium is provided on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

Get the initial crash log and system files of the application APP in the device;

Modify the extension of the initial crash file to get the target crash file;

Validate target crash logs based on system files;

If the verification is passed, the target crash log is parsed to obtain the target log file, and the target date file includes the accident information of the APP.

In one embodiment, the processor further implements the following steps when executing the computer program:

Symbolically parse the target crash log to get the class name and method name of the APP accident;

According to the class name and method name, the initial log file is generated, and the initial log file is named to obtain the target log file.

In one embodiment, the processor further implements the following steps when executing the computer program:

Determine whether the authentication information in the system file is consistent with the authentication information in the target crash file;

If the authentication information in the system file is consistent with the authentication information in the target crash file, it is determined that the authentication is passed;

If the authentication information in the system file is inconsistent with the authentication information in the target crash file, it is determined that the authentication fails.

In one embodiment, the processor further implements the following steps when executing the computer program: wherein the system file includes a program file and a symbol table file;

Determine whether the authentication information in the program file and the symbol table file is consistent with the authentication information in the target crash file;

If the authentication information in the program file and the symbol table file is consistent with the authentication information in the target crash file, it means that the authentication information in the system file is consistent with the authentication information in the target crash file.

In one embodiment, the processor further implements the following steps when executing the computer program:

If the verification fails, the new target crash file of the APP is re-acquired, and the new target crash file is re-verified based on the system file.

In one embodiment, the processor further implements the following steps when executing the computer program:

In response to the authentication failure, confirm the reason why the authentication failed;

An error message is output based on the reason why the authentication failed.

In one embodiment, the processor further implements the following steps when executing the computer program:

Get multiple base files contained in the device;

Display multiple base files in the import file preview area of the parsing application interface, where the parsing application can be installed on the device;

Crash logs and system files in the device are obtained in response to selected operations on the plurality of underlying files based on the import file preview area.

In one embodiment, the processor further implements the following steps when executing the computer program:

Display the target log file in the generated file preview area of the parsing application interface;

Obtain the export instruction based on the parsing application program interface, and store the target log file according to the target path in response to the export instruction.

In one embodiment, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the following steps:

Get the initial crash log and system files of the application APP in the device;

Modify the extension of the initial crash file to get the target crash file;

Validate target crash logs based on system files;

If the verification is passed, the target crash log is parsed to obtain the target log file, and the target date file includes the accident information of the APP.

In one embodiment, the processor further implements the following steps when executing the computer program:

Symbolically parse the target crash log to get the class name and method name of the APP accident;

According to the class name and method name, the initial log file is generated, and the initial log file is named to obtain the target log file.

In one embodiment, the processor further implements the following steps when executing the computer program:

Determine whether the authentication information in the system file is consistent with the authentication information in the target crash file;

If the authentication information in the system file is consistent with the authentication information in the target crash file, it is determined that the authentication is passed;

If the authentication information in the system file is inconsistent with the authentication information in the target crash file, it is determined that the authentication fails.

In one embodiment, the processor further implements the following steps when executing the computer program: wherein the system file includes a program file and a symbol table file;

Determine whether the authentication information in the program file and the symbol table file is consistent with the authentication information in the target crash file;

If the authentication information in the program file and the symbol table file is consistent with the authentication information in the target crash file, it means that the authentication information in the system file is consistent with the authentication information in the target crash file.

In one embodiment, the processor further implements the following steps when executing the computer program:

If the verification fails, the new target crash file of the APP is re-acquired, and the new target crash file is re-verified based on the system file.

In one embodiment, the processor further implements the following steps when executing the computer program:

In response to the authentication failure, confirm the reason why the authentication failed;

An error message is output based on the reason why the authentication failed.

In one embodiment, the processor further implements the following steps when executing the computer program:

Get multiple base files contained in the device;

Display multiple base files in the import file preview area of the parsing application interface, where the parsing application can be installed on the device;

Crash logs and system files in the device are obtained in response to selected operations on the plurality of underlying files based on the import file preview area.

In one embodiment, the processor further implements the following steps when executing the computer program:

Display the target log file in the generated file preview area of the parsing application interface;

Obtain the export instruction based on the parsing application program interface, and store the target log file according to the target path in response to the export instruction.

It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all Information and data authorized by the user or fully authorized by the parties.

Those skilled in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented by instructing relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium , when the computer program is executed, it may include the processes of the above-mentioned method embodiments. Wherein, any reference to a memory, a database or other media used in the various embodiments provided in this application may include at least one of a non-volatile memory and a volatile memory. Non-volatile memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive memory (ReRAM), magnetic variable memory (Magnetoresistive Random Memory) Access Memory, MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (Phase Change Memory, PCM), graphene memory, etc. Volatile memory may include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration and not limitation, the RAM may be in various forms, such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM). The database involved in the various embodiments provided in this application may include at least one of a relational database and a non-relational database. The non-relational database may include a blockchain-based distributed database, etc., but is not limited thereto. The processors involved in the various embodiments provided in this application may be general-purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, data processing logic devices based on quantum computing, etc., and are not limited to this.

The technical features of the above embodiments can be combined arbitrarily. In order to make the description simple, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features It is considered to be the range described in this specification.

The above examples only represent several embodiments of the present application, and the descriptions thereof are relatively specific and detailed, but should not be construed as a limitation on the scope of the patent of the present application. It should be pointed out that for those skilled in the art, without departing from the concept of the present application, several modifications and improvements can be made, which all belong to the protection scope of the present application. Therefore, the scope of protection of the present application should be determined by the appended claims.

Claims (12)

1. A method for parsing a crash log, the method comprising:

acquiring an initial crash log and a system file of an application program APP in equipment;

modifying the expansion name of the initial crash file to obtain a target crash file;

verifying the target crash log based on the system file;

and if the target crash log passes the verification, analyzing the target crash log to obtain a target log file, wherein the target log file comprises the accident information of the APP.

2. The method of claim 1, wherein parsing the target crash log to obtain a target log file comprises:

performing symbolic analysis on the target crash log to obtain a class name and a method name of the APP accident;

and generating an initial log file according to the class name and the method name, and naming the initial log file to obtain the target log file.

3. The method of claim 1 or 2, wherein the validating the target crash log based on the system file comprises:

judging whether the identity authentication information in the system file is consistent with the identity authentication information in the target crash file or not;

if the identity authentication information in the system file is consistent with the identity authentication information in the target crash file, determining that the authentication is passed;

and if the authentication information in the system file is inconsistent with the authentication information in the target crash file, determining that the authentication fails.

4. The method of claim 3, wherein the system file comprises a program file and a symbol table file, and wherein the determining whether the authentication information in the system file is consistent with the authentication information in the target crash file comprises:

judging whether the identity verification information in the program file and the symbol table file is consistent with the identity verification information in the target crash file or not;

and if the identity authentication information in the program file and the symbol table file is consistent with the identity authentication information in the target crash file, indicating that the identity authentication information in the system file is consistent with the identity authentication information in the target crash file.

5. The method of claim 3, further comprising:

and if the verification fails, re-acquiring the new target crash file of the APP, and re-verifying the new target crash file based on the system file.

6. The method of claim 3, comprising:

in response to the authentication failure, confirming a reason for the authentication failure;

and outputting error-reporting reminding information based on the reason that the identity authentication fails.

7. The method according to claim 1 or 2, wherein the obtaining of the initial crash log and the system file of the application program APP in the device comprises:

acquiring a plurality of basic files contained in the equipment;

displaying the plurality of base files in an import file preview area of an analysis application program interface, wherein the analysis application program is installed on the device;

in response to a selected operation on the plurality of base files based on the import file preview area, obtaining the crash log and the system file in the device.

8. The method of claim 7, further comprising:

displaying the target log file in a file preview generation area of the analysis application program interface;

and acquiring an export instruction based on the analysis application program interface, and storing the target log file according to a target path in response to the export instruction.

9. An apparatus for parsing a crash log, the apparatus comprising:

the device comprises an acquisition module, a storage module and a processing module, wherein the acquisition module is used for acquiring an initial crash log and a system file of an application program APP in the device;

the modification module is used for modifying the expansion name of the initial crash file to obtain a target crash file;

a verification module for verifying the system file based on the target crash log;

and the analysis module is used for analyzing the system file to obtain a target log file if the verification is passed, wherein the target log file comprises the accident information of the APP.

10. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 8.

11. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 8.

12. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method of any one of claims 1 to 8 when executed by a processor.

Images