CN111104185A - File analysis method, device, system and storage medium - Google Patents
File analysis method, device, system and storage medium Download PDFInfo
- Publication number
- CN111104185A CN111104185A CN201911327187.5A CN201911327187A CN111104185A CN 111104185 A CN111104185 A CN 111104185A CN 201911327187 A CN201911327187 A CN 201911327187A CN 111104185 A CN111104185 A CN 111104185A
- Authority
- CN
- China
- Prior art keywords
- file
- crash
- target
- crash file
- time
- 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.)
- Pending
Links
- 238000004458 analytical method Methods 0.000 title claims abstract description 58
- 238000000034 method Methods 0.000 claims abstract description 47
- 238000012216 screening Methods 0.000 claims abstract description 22
- 238000001514 detection method Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 6
- 230000000977 initiatory effect Effects 0.000 claims description 2
- 238000011161 development Methods 0.000 description 13
- 230000002159 abnormal effect Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 239000002699 waste material Substances 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000015556 catabolic process Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000007619 statistical method Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a file analysis method, a device, a system and a storage medium, wherein the method comprises the following steps: when the application software is started every time, detecting whether a first crash file corresponding to the application software exists in a system; if the first crash file exists, updating the first file name of the first crash file according to the generation time of the first crash file to obtain a second crash file; and sending the second crash file to the server side so that the server side performs time classification on the second crash file according to the second file name of the second crash file received each time, and when an analysis triggering instruction is detected, screening each second crash file under each target time category to determine a target crash file, and analyzing the target crash file. By the technical scheme of the invention, the analysis efficiency can be improved, and the utilization rate of equipment resources is also improved.
Description
Technical Field
The embodiment of the invention relates to computer technology, in particular to a file parsing method, a device, a system and a storage medium.
Background
With the rapid development of computer technology, more and more application software is developed to meet the increasing demands of users.
Abnormal breakdown conditions, such as flash back and crash, may occur in the running process of the application software, so that developers need to perform abnormal analysis on the abnormal breakdown conditions, so as to avoid reoccurrence of the abnormal conditions, and improve user experience. When the application program is in an abnormal crash condition, the operating system can generate a corresponding crash file. Since the crash file is an encrypted file, the crash file needs to be analyzed, so as to determine a specific crash reason based on the analyzed crash information.
In the prior art, each client installed with application software generally sends a generated crash file to a server, and a developer analyzes each crash file received by the server in real time. However, since the number of crash files is large, and a plurality of crash files generated due to the same crash are also analyzed one by one, the analysis efficiency is reduced, and the device resources are wasted.
Disclosure of Invention
The embodiment of the invention provides a file parsing method, a file parsing device, a file parsing system and a storage medium, which are used for improving parsing efficiency and improving equipment resource utilization rate.
In a first aspect, an embodiment of the present invention provides a file parsing method, applied to a client, including:
when application software is started every time, detecting whether a first crash file corresponding to the application software exists in a system;
if the first crash file exists, updating the first file name of the first crash file according to the generation time of the first crash file to obtain a second crash file;
and sending the second crash file to a server side so that the server side performs time classification on the second crash file according to the second file name of the second crash file received each time, and when an analysis trigger instruction is detected, screening each second crash file under each target time category to determine a target crash file, and analyzing the target crash file.
In a second aspect, an embodiment of the present invention further provides a file parsing method, applied to a server, including:
receiving a second crash file corresponding to application software sent by a client, wherein a second file name of the second crash file comprises the generation time of the first crash file;
time classification is carried out on the currently received second crash file according to the second file name;
and when an analysis triggering instruction is detected, screening the second crash files under each target time category to determine a target crash file, and analyzing the target crash file.
In a third aspect, an embodiment of the present invention further provides a file parsing apparatus, integrated in a client, where the apparatus includes:
the system comprises a first crash file detection module, a second crash file detection module and a crash file detection module, wherein the first crash file detection module is used for detecting whether a first crash file corresponding to application software exists in a system when the application software is started every time;
the file name updating module is used for updating the first file name of the first crash file according to the generation time of the first crash file if the first crash file exists, so as to obtain a second crash file;
and the second crash file sending module is used for sending the second crash file to a server so that the server performs time classification on the second crash file according to the second file name of the second crash file received each time, screens the second crash files in each target time category to determine a target crash file when an analysis triggering instruction is detected, and analyzes the target crash file.
In a fourth aspect, an embodiment of the present invention further provides a file parsing apparatus, integrated in a server, including:
the second crash file receiving module is used for receiving a second crash file corresponding to the application software sent by the client, wherein a second file name of the second crash file comprises the generation time of the first crash file;
the second crash file classification module is used for performing time classification on the currently received second crash file according to the second file name;
and the target crash file analysis module is used for screening the second crash files under each target time category to determine a target crash file and analyzing the target crash file when an analysis trigger instruction is detected.
In a fifth aspect, an embodiment of the present invention further provides a file parsing system, where the system includes multiple clients and a server;
wherein each of the clients is configured to execute the file parsing method according to the first aspect of the present invention;
the server is used for executing the file parsing method provided by the second aspect of the invention.
In a sixth aspect, the embodiments of the present invention further provide a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the file parsing method provided in any embodiment of the present invention.
The embodiment of the invention detects whether a first crash file corresponding to the application software exists in the system when the application software is started each time; if so, updating the first file name of the first crash file according to the generation time of the first crash file, sending the second crash file obtained after updating to the server, wherein the server can perform time classification on the second crash file according to the second file name of the second crash file received each time, and when an analysis trigger instruction is detected, screening each second crash file under the target time category to determine a target crash file, and analyzing the target crash file, so that the current target crash file with analysis value can be analyzed by the time classification and the screening of each second crash file under the target time category, for example, each target crash file with different crash reasons can be analyzed, thereby avoiding the situation that a plurality of crash files generated due to the same crash reason are analyzed for a plurality of times, therefore, the analysis efficiency is improved, the waste of equipment resources is avoided, and the utilization rate of the equipment resources is improved.
Drawings
Fig. 1 is a flowchart of a file parsing method according to an embodiment of the present invention;
fig. 2 is a flowchart of a file parsing method according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a file parsing apparatus according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of a file parsing apparatus according to a fourth embodiment of the present invention;
fig. 5 is a schematic structural diagram of a file parsing system according to a fifth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a flowchart of a file parsing method according to an embodiment of the present invention, which is applicable to parsing a crash file (i.e., a crash file) of application software. The method may be performed by a file parsing apparatus integrated on a client, which may be implemented by means of software and/or hardware. The client may refer to a device in which application software is installed, such as a smart phone, a tablet computer, or a handheld game console. As shown in fig. 1, the method specifically includes the following steps:
s110, when the application software is started each time, whether a first crash file corresponding to the application software exists in the system or not is detected.
The application software may refer to any application program (App) installed in the client. For example, the application software may be, but is not limited to, gaming software. The system may refer to an operating system hosted by the client. For example, the system may refer to the apple iOS operating system. The first Crash file, i.e. the Crash file, may refer to a file generated by the system based on the operation information of the application software when the application software is run and crashed. The first crash file may store stack information when the application software runs into a crash, i.e. a specific reason for the crash in the application software. It should be noted that, because the first crash file is stored on the client used by the user, the first crash file generated by the system is a ciphertext file, and the specific content can be checked only after parsing is performed, so as to ensure the security of the data.
Specifically, if the application software in the client is running crashed after being started, the system of the client may generate a first crash file based on the running information of the application software at the time of the crash. The embodiment can detect whether the application software is started again in real time, that is, whether the application process corresponding to the application software is started again, and if so, detect whether a first crash file corresponding to the application software exists in the system based on the software name of the application software, so as to determine whether an abnormal crash situation occurs when the application software is started last time.
S120, if the first crash file exists, updating the first file name of the first crash file according to the generation time of the first crash file to obtain a second crash file.
The generation time of the first crash file may refer to the time when the system generates the first crash file, that is, the time when the application software crashes. For example, the generation time of the first crash file may be: 2019-12-17_10-53-06, which shows that the first crash file was generated at 10 o 'clock, 17 o' clock, 53 min 06 sec, 12/month, 2019. The second crash file may refer to the first crash file after updating the first file name.
Specifically, if it is detected that a first crash file corresponding to the application software exists in the system, it indicates that an abnormal crash situation occurs when the application software is started last time, at this time, the generation time of the first crash file may be obtained, and the generation time is added to a preset position in a first file name of the first crash file in a preset time format, such as a head or a tail of the file name, so as to update the first file name, so that the obtained second file name of the second crash file includes the generation time of the first crash file.
S130, the second crash files are sent to the server side, so that the server side carries out time classification on the second crash files according to the second file names of the second crash files received each time, and when an analysis triggering instruction is detected, the second crash files under the target time classification are screened to determine target crash files, and the target crash files are analyzed.
The server may refer to a server for analyzing a crash file corresponding to the application software. The parsing trigger instruction may be an instruction to instruct file parsing of the crash file. For example, the parsing trigger command may be generated by manual triggering based on user operation, or may be generated by automatic triggering at regular time, so that automatic parsing may be performed periodically without human intervention. The time category may refer to a category corresponding to each generation time period set in advance. The present embodiment may include multiple time categories. The target time category may be a specific time category of all time categories, which may be set based on traffic demand and scenario. The target time category in this embodiment may be set in real time based on the parsing trigger instruction. For example, the time category corresponding to the generation time period closest to the generation time of the analysis trigger instruction may be determined as the target time category. For example, assuming that every three days corresponds to a time category, when the analysis trigger instruction is generated in No. 10/month 17, the time categories corresponding to the generation time periods from No. 10/month 14 to No. 16 may be determined as the target time categories, so that statistics may be performed on crash files generated in the last three days, and the target crash files may be screened out. The target crash file may refer to each second crash file to be parsed under the target time category. For example, the target crash file may refer to a second crash file generated based on a different crash reason in the target time category.
Specifically, there are multiple clients installed with the same application software, and each client performs the operations of S110 to S130, so that each client sends all the obtained second crash files to the server. The server side can obtain the generation time of the crash files according to the second file names of the second crash files received each time, and can perform time classification on the second crash files based on the generation time, so that before the analysis trigger instruction is not detected, all the received second crash files can be subjected to time classification in real time, and each second crash file in each time category can be updated in real time. When the server detects an analysis trigger instruction, the server may perform statistical screening on each second crash file in the target time category to determine a target crash file to be analyzed, for example, a second crash file generated based on different crash reasons in the target time category. By only analyzing the target crash file, repeated analysis of the repeated crash file can be avoided, the analysis efficiency is improved, and the resource utilization rate can be improved.
According to the technical scheme of the embodiment, when the application software is started each time, whether a first crash file corresponding to the application software exists in the system is detected; if so, updating the first file name of the first crash file according to the generation time of the first crash file, sending the second crash file obtained after updating to the server, wherein the server can perform time classification on the second crash file according to the second file name of the second crash file received each time, and when an analysis trigger instruction is detected, screening each second crash file under the target time category to determine a target crash file, and analyzing the target crash file, so that the current target crash file with analysis value can be analyzed by the time classification and the screening of each second crash file under the target time category, for example, each target crash file with different crash reasons can be analyzed, thereby avoiding the situation that a plurality of crash files generated due to the same crash reason are analyzed for a plurality of times, therefore, the analysis efficiency is improved, the waste of equipment resources is avoided, and the utilization rate of the equipment resources is improved.
On the basis of the foregoing technical solution, the updating the first file name of the first corrupted file according to the generation time of the first corrupted file in S120 may include: acquiring login user information of application software; and updating the first file name of the first crash file according to the generation time and the login user information of the first crash file, so that the second file name of the second crash file obtained after updating comprises the generation time and the login user information.
The login user information may refer to user information for logging in the application software in the client. Illustratively, the login user information may be, but is not limited to, a login user identification in order to distinguish between different login users.
Specifically, if it is detected that a first crash file corresponding to the application software exists in the system, login user information of the current login user of the application software may be obtained through an application program process, and the login user information is also added to a first file name of the first crash file to identify that the first crash file is generated when the user logs in, so that the user can subsequently query the crash file of a specific user based on the file name of the crash file, and query efficiency is improved.
For example, in this embodiment, the device information of the client may also be added to the first file name of the first crash file, where the device information may include operating system information, model information, and the like, so as to identify the device information that generates the first crash file, and facilitate subsequent screening and query of the crash file based on the service requirement, thereby implementing diversity of screening methods and meeting personalized requirements of users.
Example two
Fig. 2 is a flowchart of a file parsing method according to a second embodiment of the present invention, which is applicable to parsing a crash file (i.e., a crash file) of application software. The method can be executed by a file parsing apparatus integrated on a server, and the apparatus can be implemented by software and/or hardware. The server may be a server for analyzing a crash file corresponding to the application software. As shown in fig. 2, the method specifically includes the following steps:
s210, receiving a second crash file corresponding to the application software sent by the client, wherein a second file name of the second crash file comprises the generation time of the first crash file.
The application software may refer to any application program (App) installed in the client. The first Crash file, i.e. the Crash file, may refer to a file generated by the system based on the operation information of the application software when the application software is run and crashed. The second crash file may be a crash file obtained by the client updating the first file name of the first crash file in advance based on the generation time of the first crash file, and thus the second file name of the second crash file may include the generation time of the first crash file.
Specifically, each client obtains a second crash file based on a first crash file when detecting that the system has the first crash file corresponding to the application software each time, and sends the second crash file to the server, so that the server can receive the second crash file corresponding to the application software sent by each client.
S220, time classification is carried out on the second crash file received currently according to the second file name.
Wherein, each time category can be preset based on the service requirement and the scene so as to classify the time. The time category may be a category set corresponding to each generation period set in advance. Each time category may be used to store a respective second crash file generated within the generation time period corresponding to the time category. Wherein the generation time period may be set based on the time interval of parsing the trigger instruction generation, so that the crash file generated in each time interval may be obtained. The present embodiment may include multiple time categories. Illustratively, the generation time period may be set to three days, so that every third day corresponds to one time category, for example, the time categories corresponding to 10 month 14 to 16 may be used to store all the second crash files generated by the client within 10 month 14 to 16. For example, each time category may correspond to a folder, and the name of the folder may be the generation time period corresponding to the time category, so that the corresponding second crash file is stored by using the folder, thereby achieving time classification.
Specifically, each received second crash file may be time-classified based on the generation time period corresponding to each time category, so as to update the second crash files included in each time category in real time.
Illustratively, S220 may include: and determining the current time category corresponding to the second crash file according to the generation time period corresponding to each time category and the generation time of the first crash file in the second file name, and adding the second crash file to the current time category.
Specifically, the generation time of the first collapsed file may be obtained according to the received second file name of the second collapsed file, the generation time period corresponding to each time category is matched with the obtained generation time, the time category corresponding to the generation time period in which the generation time is located is determined, the time category is used as the current time category, and the second collapsed file is stored and added to the current time category. Similarly, the server may perform time classification on each received second crash file.
And S230, when the analysis triggering instruction is detected, screening each second crash file in the target time category to determine a target crash file, and analyzing the target crash file.
The parsing triggering instruction may be an instruction for instructing to perform file parsing on the crash file. For example, the parsing trigger command may be generated by manual triggering based on user operation, or may be generated by automatic triggering at regular time, so that automatic parsing may be performed periodically without human intervention. The trigger period may be a preset time interval after the application software is updated on line based on the crash reason, so that the running condition of the updated application software can be monitored. The target time category may be a specific time category of all time categories, which may be set based on traffic demand and scenario. The target time category in this embodiment may be set in real time based on the parsing trigger instruction. For example, the time category corresponding to the generation time period closest to the generation time of the analysis trigger instruction may be determined as the target time category. For example, assuming that every three days corresponds to a time category, when the analysis trigger instruction is generated in No. 10/month 17, the time categories corresponding to the generation time periods from No. 10/month 14 to No. 16 may be determined as the target time categories, so that statistics may be performed on crash files generated in the last three days, and the target crash files may be screened out. The target crash file may refer to each second crash file to be parsed under the target time category. For example, the number of the target crash files may be one or more, and the crash reasons corresponding to each target crash file are different.
Specifically, when the server detects an analysis trigger instruction, the server may perform statistical screening on each second crash file in the target time category to determine a target crash file to be analyzed, for example, a second crash file generated based on different crash reasons in the target time category. By only analyzing the target crash file, repeated analysis of the repeated crash file can be avoided, the analysis efficiency is improved, and the resource utilization rate can be improved.
For example, the screening of the second crash files in the target time category in S230 to determine the target crash file may include: acquiring crash thread information in each second crash file under the target time category; combining the second crash files with the same crash thread information, and determining each combination result as a crash file set belonging to the same crash reason; and determining a target crash file in the crash file set according to each crash file set.
The second crash file is a ciphertext file in a text txt format, so that the encrypted crash content in the second crash file, namely the crash thread information, can be checked. Crash thread information may refer to stack information of a thread that was run when the application software ran a crash. If the crash thread information in the at least two second crash files is the same, it indicates that the crash reasons corresponding to the at least two second crash files are also the same. A set of crash files can refer to a set consisting of a second crash file generated based on the same crash reason.
Specifically, information of each second crash file in the target time category can be read, crash thread information in each second crash file is obtained, each crash thread information is compared, each second crash file with the same crash thread information is determined and combined, each combination result can be obtained, each combination result is a crash file set belonging to the same crash reason, the crash reasons corresponding to each crash file set are different, and therefore statistical analysis of the crash reasons corresponding to each second crash file in the target time category is achieved. In this embodiment, a second crash file may be randomly selected from each crash file set as a target crash file, or a second crash file corresponding to the current closest generation time may be selected as a target crash file, so that target crash files to be analyzed with different crash reasons may be obtained. When the number of the crash file sets is larger than the preset number, the number of second crash files in each crash file set can be counted, each crash file set is arranged in a descending order based on the number of the second crash files, the crash file sets with the preset number are obtained after arrangement, and a target crash file is determined from each acquired crash file set with the preset number, so that the target crash files with more times of occurrence of crash reasons, namely the target crash files with higher analysis value, can be analyzed, the number of the target crash files is reduced, and the analysis efficiency is further improved.
For example, if the second file name of the second crash file includes the device information and/or the user login information of the client, the second crash files in the target time category may be screened based on the device information and/or the user login information of the client to determine the target crash file. For example, the second crash file corresponding to the specified device information and/or the specified user information in the target time category may be determined as a target crash file, so as to analyze the second crash file of the specified device information and/or the specified user information, thereby implementing diversity of screening methods and meeting personalized requirements of users.
For example, parsing the target crash file in S230 may include: acquiring a file identifier of a target crash file; determining a target symbol table file corresponding to the target crash file according to the file identifier; and analyzing the target crash file according to the target symbol table file.
Wherein the file identification may be an identification that uniquely characterizes the crash file. For the apple iOS operating system, a Universal Unique Identifier (UUID) corresponding to each development version of the application software may be used as a file Identifier of the crash file, so as to distinguish different crash files. After a new development version of application software is packaged, a universal unique identification code UUID is distributed to the development version, a software installation file and a symbol table file are generated aiming at the development version, and therefore the universal unique identification code UUID can be used as file identifications of the software installation file and the symbol table file. Wherein the software installation file is used for installing the application software in the client. The symbol table file, i.e., the dSYM file, may be a transit file that stores the 16-ary function address mapping information after compilation. The symbol table file may be used to decrypt the crash file, so that the crash file is converted from a ciphertext file to a plaintext file, facilitating viewing of the specific crash content. The symbol table file is stored in the server side, cannot be externally placed and is a private file for developers, so that the safety of data is guaranteed.
It should be noted that, as the development version of the application software is updated iteratively, more and more symbol table files corresponding to the same application software exist, so that a target symbol table file corresponding to the application software in the current development version needs to be accurately queried, so that a crash file of the application software can be successfully analyzed by using the target symbol table file.
Specifically, the target crash file includes a file identifier in plaintext, so that the file identifier of the target crash file can be obtained in a command line manner. And according to the corresponding relation between the file identifier and the symbol table file and the file identifier of the target crash file, determining the target symbol table file corresponding to the target crash file from the plurality of symbol table files. For example, if the UUID file identifier is represented by a universal unique identifier, the target symbol table file corresponding to the UUID of the target crash file may be pulled from the module for storing the symbol table file. The embodiment can automatically analyze the target crash file by using the target symbol table file. For example, the server may be pre-loaded with a Mac operating system, so that the target crash file may be automatically analyzed through the target symbol table file by using an Xcode integration development tool running on the Mac operating system, manual analysis is not required, and the analysis efficiency is further improved.
For example, the service end in this embodiment may include a first service end and a second service end, so as to improve data processing efficiency. The first server may be a dump server, and is configured to perform time classification on the currently received second crash files according to the second file names, and when an analysis trigger instruction is detected, screen each second crash file in the target time category to determine a target crash file, and send the target crash file to the second server. The second server may be a server dedicated to parsing the crash file, and is configured to automatically parse the target crash file sent by the first server.
In the technical solution of this embodiment, the server may, according to the second file name of the second corrupted file received each time, time classification is carried out on the second crash files, when an analysis triggering instruction is detected, the second crash files under the target time category are screened to determine a target crash file, the target crash file is analyzed, so that by means of time classification and screening of the second crash files under the target time category, the target crash files currently having parsing value, such as the target crash files with different crash reasons, thereby avoiding the situation that a plurality of crash files generated due to the same crash are analyzed for a plurality of times, therefore, the analysis efficiency is improved, the waste of equipment resources is avoided, and the utilization rate of the equipment resources is improved.
On the basis of the above technical solution, after determining the target crash file in the crash file set, the method may further include: determining the occurrence frequency of the crash reasons corresponding to the target crash files according to the number of second crash files contained in the crash file set corresponding to the target crash files; accordingly, after S230, the method may further include: and sending the analyzed target crash file and the crash reason occurrence frequency corresponding to the target crash file to an initiating terminal corresponding to a developer.
The occurrence frequency of the crash reasons may refer to the number and/or frequency of times of occurrence of the crash phenomenon due to the same crash reason in the generation time period. The developer may refer to a person who analyzes the crash reason of the application software so as to update the version of the application software.
Specifically, for each target crash file, the number of second crash files included in the crash file set in which the target crash file is located may be determined, and the number of second crash files is determined as the number of times of occurrence of a crash reason corresponding to the target crash file; and determining the ratio of the number of the second crash files to the total number of the second crash files in the target time category as the occurrence frequency of the crash reasons corresponding to the target crash files. The analyzed target crash files and the crash reasons corresponding to the target crash files are sent to the development ends corresponding to the developers, so that the developers can quickly analyze and locate the crash reasons and know the severity of the crash reasons based on the crash reasons, the application software can be subjected to version development, the application software corresponding to a newly developed version is online after the development, the situation that the application software is abnormally crashed due to the same crash reasons again is avoided, and the user experience is improved.
On the basis of the technical scheme, the second file name of the second crash file also comprises login user information of the application software; accordingly, the method may further comprise: and if the crash file query instruction is received, querying a second crash file corresponding to the target user information from each second crash file according to the target user information in the crash file query instruction and the login user information in the second file name of each second crash file.
The crash file query instruction may refer to an instruction for querying information of a target user. Specifically, when the user feeds back that the application software logged in by the user has an abnormal crash condition, a crash file query instruction can be generated according to the target user information fed back by the user. The second file name of each second crash file comprises the user login information, so that all second crash files corresponding to the target user information can be quickly searched based on the second file name, whether each second crash file is analyzed or not is detected and inquired, if not, the unanalyzed second crash files are analyzed, statistical analysis is carried out according to all analyzed second crash files corresponding to the target user, the specific reason of the crash phenomenon of the application software used by the target user is determined, and the specific reason is fed back to the target user, so that the target user can know the specific reason, and the user experience is improved.
The following is an embodiment of the file parsing apparatus integrated in the client according to the embodiment of the present invention, and the apparatus and the file parsing method provided in the first embodiment belong to the same inventive concept, and details that are not described in detail in the embodiment of the file parsing apparatus may refer to the first embodiment.
EXAMPLE III
Fig. 3 is a schematic structural diagram of a file parsing apparatus according to a third embodiment of the present invention, which is applicable to parsing a crash file (i.e., a crash file) of application software. The device is integrated in a client, and specifically comprises: a first corrupted file detection module 310, a file name update module 320, and a second corrupted file transmission module 330.
The first crash file detection module 310 is configured to detect whether a first crash file corresponding to the application software exists in the system when the application software is started each time; the file name updating module 320 is configured to update the first file name of the first corrupted file according to the generation time of the first corrupted file if the first corrupted file exists, and obtain a second corrupted file; the second crash file sending module 330 is configured to send the second crash file to the server, so that the server performs time classification on the second crash file according to the second file name of the second crash file received each time, and when an analysis trigger instruction is detected, screens each second crash file in the target time category to determine a target crash file, and analyzes the target crash file.
Optionally, the file name updating module 320 is specifically configured to:
acquiring login user information of application software; and updating the first file name of the first crash file according to the generation time and the login user information of the first crash file, so that the second file name of the second crash file obtained after updating comprises the generation time and the login user information.
The file analysis device provided by the embodiment of the invention can execute the file analysis method provided by the embodiment of the invention, and has the corresponding functional modules and beneficial effects of executing the file analysis method.
It should be noted that, in the embodiment of the file parsing apparatus, the modules included in the embodiment are only divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
The following is an embodiment of the file parsing apparatus integrated in the server according to the embodiment of the present invention, and the apparatus and the file parsing method according to the second embodiment belong to the same inventive concept, and details that are not described in detail in the embodiment of the file parsing apparatus may refer to the second embodiment.
Example four
Fig. 4 is a schematic structural diagram of a file parsing apparatus according to a fourth embodiment of the present invention, which is applicable to parsing a crash file (i.e., a crash file) of application software. The device is integrated in the server, specifically includes: a second crash file receiving module 410, a second crash file categorization module 420, and a target crash file parsing module 430.
The second crash file receiving module 410 is configured to receive a second crash file corresponding to the application software sent by the client, where a second file name of the second crash file includes a generation time of the first crash file; a second crash file classifying module 420, configured to perform time classification on the currently received second crash file according to the second file name; and the target crash file analyzing module 430 is configured to, when an analysis trigger instruction is detected, screen each second crash file in the target time category to determine a target crash file, and analyze the target crash file.
Optionally, the second crash file classifying module 420 is specifically configured to:
and determining the current time category corresponding to the second crash file according to the generation time period corresponding to each time category and the generation time of the first crash file in the second file name, and adding the second crash file to the current time category.
Optionally, the target crash file parsing module 430 includes: the target crash file determining unit is specifically configured to:
acquiring crash thread information in each second crash file under the target time category; combining the second crash files with the same crash thread information, and determining each combination result as a crash file set belonging to the same crash reason; and determining a target crash file in the crash file set according to each crash file set.
Optionally, the target crash file parsing module 430 includes: the target crash file parsing unit is specifically configured to:
acquiring a file identifier of a target crash file; determining a target symbol table file corresponding to the target crash file according to the file identifier; and analyzing the target crash file according to the target symbol table file.
Optionally, the apparatus further comprises:
the crash reason occurrence frequency determining module is used for determining the occurrence frequency of the crash reasons corresponding to the target crash files according to the number of second crash files contained in the crash file set corresponding to the target crash files after the target crash files in the crash file set are determined;
correspondingly, the device also comprises: and the file sending module is used for sending the analyzed target crash file and the crash reason occurrence frequency corresponding to the target crash file to the development end corresponding to the developer after analyzing the target crash file.
Optionally, the second file name of the second crash file further contains login user information of the application software;
correspondingly, the device also comprises:
and the crash file query module is used for querying a second crash file corresponding to the target user information from each second crash file according to the target user information in the crash file query instruction and the login user information in the second file name of each second crash file if the crash file query instruction is received.
The file analysis device provided by the embodiment of the invention can execute the file analysis method provided by the second embodiment of the invention, and has the corresponding functional modules and beneficial effects of executing the file analysis method.
It should be noted that, in the embodiment of the file parsing apparatus, each included module and unit are only divided according to functional logic, but are not limited to the above division, as long as the corresponding function can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
EXAMPLE five
Fig. 5 is a schematic structural diagram of a file parsing system according to a fifth embodiment of the present invention. Referring to fig. 5, the system includes: a plurality of clients 510 and a server 520.
Wherein, each client 510 is used for the file parsing method steps provided in the first embodiment; the server 520 is used for the file parsing method steps as provided in the second embodiment.
In this embodiment, each client 510 and the server 520 may communicate through a web service, so as to realize information interaction.
The working process of the file parsing system provided by the embodiment is as follows:
each client 510 detects whether a first crash file corresponding to the application software exists in the system when the application software is started each time; if the first crash file exists, updating the first file name of the first crash file according to the generation time of the first crash file to obtain a second crash file; the second crash file is sent to the server 520. The server 520 classifies the second crash file according to the second file name of the second crash file received each time, and when an analysis trigger instruction is detected, screens each second crash file under the target time category to determine a target crash file, and analyzes the target crash file, so that repeated analysis of the crash files can be avoided, the analysis efficiency is improved, and the utilization rate of equipment resources is improved.
Optionally, the client 510 is further specifically configured to: acquiring login user information of application software; and updating the first file name of the first crash file according to the generation time and the login user information of the first crash file, so that the second file name of the second crash file obtained after updating comprises the generation time and the login user information.
Optionally, the server 520 is further specifically configured to: and determining the current time category corresponding to the second crash file according to the generation time period corresponding to each time category and the generation time of the first crash file in the second file name, and adding the second crash file to the current time category.
Optionally, the server 520 is further specifically configured to: acquiring crash thread information in each second crash file under the target time category; combining the second crash files with the same crash thread information, and determining each combination result as a crash file set belonging to the same crash reason; and determining a target crash file in the crash file set according to each crash file set.
Optionally, the server 520 is further specifically configured to: acquiring a file identifier of a target crash file; determining a target symbol table file corresponding to the target crash file according to the file identifier; and analyzing the target crash file according to the target symbol table file.
Optionally, the server 520 is further specifically configured to: after determining a target crash file in the crash file set, determining the occurrence frequency of a crash reason corresponding to the target crash file according to the number of second crash files contained in the crash file set corresponding to the target crash file; correspondingly, after the target crash file is analyzed, the analyzed target crash file and the crash reason occurrence frequency corresponding to the target crash file are sent to the development end corresponding to the developer.
Optionally, when the second file name of the second crash file further includes login user information of the application software, the server 520 is further specifically configured to: and if the crash file query instruction is received, querying a second crash file corresponding to the target user information from each second crash file according to the target user information in the crash file query instruction and the login user information in the second file name of each second crash file.
In the file parsing system in this embodiment, the client updates the first file name of the first crash file and sends the second crash file obtained after the update to the server, and the server performs time classification on the second crash file according to the second file name of the second crash file received each time, and when an parsing trigger instruction is detected, filters each second crash file in the target time category to determine a target crash file, and parses the target crash file, so as to parse the target crash file having a current parsing value, for example, parse each target crash file with different crash reasons, thereby avoiding a situation of performing multiple parses on multiple crash files generated due to the same crash reason, therefore, the analysis efficiency is improved, the waste of equipment resources is avoided, and the utilization rate of the equipment resources is improved.
EXAMPLE six
The present embodiment provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the file parsing method provided in the first embodiment of the present invention, and the method includes:
when the application software is started every time, detecting whether a first crash file corresponding to the application software exists in a system;
if the first crash file exists, updating the first file name of the first crash file according to the generation time of the first crash file to obtain a second crash file;
and sending the second crash files to the server side so that the server side performs time classification on the second crash files according to the second file names of the second crash files received each time, and when an analysis triggering instruction is detected, screening each second crash file under the target time category to determine a target crash file, and analyzing the target crash files.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer-readable storage medium may be, for example but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + +, or the like, as well as conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It will be understood by those skilled in the art that the modules or steps of the invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of computing devices, and optionally they may be implemented by program code executable by a computing device, such that it may be stored in a memory device and executed by a computing device, or it may be separately fabricated into various integrated circuit modules, or it may be fabricated by fabricating a plurality of modules or steps thereof into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
An embodiment of the present invention further provides another computer-readable storage medium, where computer-executable instructions, when executed by a computer processor, are configured to implement steps of a file parsing method provided in the second embodiment of the present invention, where the method includes:
receiving a second crash file corresponding to the application software sent by the client, wherein a second file name of the second crash file comprises the generation time of the first crash file;
time classification is carried out on the currently received second crash file according to the second file name;
and when an analysis triggering instruction is detected, screening each second crash file under the target time category to determine a target crash file, and analyzing the target crash file.
Of course, the storage medium provided by the embodiment of the present invention includes computer-executable instructions, and the computer-executable instructions are not limited to the operations of the method described above, and may also perform related operations in the file parsing method provided by the second embodiment of the present invention. The storage medium is described with reference to the explanation of embodiment nine.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (12)
1. A file parsing method is applied to a client and comprises the following steps:
when application software is started every time, detecting whether a first crash file corresponding to the application software exists in a system;
if the first crash file exists, updating the first file name of the first crash file according to the generation time of the first crash file to obtain a second crash file;
and sending the second crash file to a server side so that the server side performs time classification on the second crash file according to the second file name of the second crash file received each time, and when an analysis trigger instruction is detected, screening each second crash file in a target time category to determine a target crash file, and analyzing the target crash file.
2. The method of claim 1, wherein updating the first file name of the first crashed file based on the time of generation of the first crashed file comprises:
acquiring login user information of the application software;
and updating the first file name of the first crash file according to the generation time of the first crash file and the login user information, so that the second file name of the second crash file obtained after updating comprises the generation time and the login user information.
3. A file parsing method is applied to a server and comprises the following steps:
receiving a second crash file corresponding to application software sent by a client, wherein a second file name of the second crash file comprises the generation time of the first crash file;
time classification is carried out on the currently received second crash file according to the second file name;
and when an analysis triggering instruction is detected, screening each second crash file under the target time category to determine a target crash file, and analyzing the target crash file.
4. The method of claim 3, wherein time classifying the currently received second collapsed file according to the second file name comprises:
and determining the current time category corresponding to the second crash file according to the generation time period corresponding to each time category and the generation time of the first crash file in the second file name, and adding the second crash file to the current time category.
5. The method of claim 3, wherein screening each of the second crash files for a target time category to determine a target crash file comprises:
acquiring crash thread information in each second crash file under the target time category;
combining the second crash files with the same crash thread information, and determining each combination result as a crash file set belonging to the same crash reason;
and determining a target crash file in the crash file sets according to each crash file set.
6. The method of claim 3, wherein parsing the target crash file comprises:
acquiring a file identifier of the target crash file;
determining a target symbol table file corresponding to the target crash file according to the file identifier;
and analyzing the target crash file according to the target symbol table file.
7. The method of claim 5, after determining a target crash file in the set of crash files, further comprising:
determining the occurrence frequency of the crash reasons corresponding to the target crash files according to the number of second crash files contained in the crash file set corresponding to the target crash files;
correspondingly, after parsing the target crash file, the method further includes:
and sending the analyzed target crash file and the crash reason occurrence frequency corresponding to the target crash file to an initiating terminal corresponding to a developer.
8. The method of claim 3, wherein the second filename of the second crash file further comprises login user information for the application software;
accordingly, the method further comprises:
and if a crash file query instruction is received, querying a second crash file corresponding to the target user information from each second crash file according to the target user information in the crash file query instruction and the login user information in the second file name of each second crash file.
9. A file parsing device, integrated in a client, comprising:
the system comprises a first crash file detection module, a second crash file detection module and a crash file detection module, wherein the first crash file detection module is used for detecting whether a first crash file corresponding to application software exists in a system when the application software is started every time;
the file name updating module is used for updating the first file name of the first crash file according to the generation time of the first crash file if the first crash file exists, so as to obtain a second crash file;
and the second crash file sending module is used for sending the second crash file to a server so that the server performs time classification on the second crash file according to the second file name of the second crash file received each time, screens the second crash files under the target time category to determine a target crash file when an analysis triggering instruction is detected, and analyzes the target crash file.
10. A file parsing apparatus, integrated in a server, includes:
the second crash file receiving module is used for receiving a second crash file corresponding to the application software sent by the client, wherein a second file name of the second crash file comprises the generation time of the first crash file;
the second crash file classification module is used for performing time classification on the currently received second crash file according to the second file name;
and the target crash file analysis module is used for screening each second crash file under the target time category to determine a target crash file when an analysis trigger instruction is detected, and analyzing the target crash file.
11. A file analysis system is characterized by comprising a plurality of clients and a server;
wherein each of the clients is configured to perform the file parsing method of claim 1 or 2;
the server is used for executing the file parsing method according to any one of claims 3-8.
12. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a file parsing method according to any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911327187.5A CN111104185A (en) | 2019-12-20 | 2019-12-20 | File analysis method, device, system and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911327187.5A CN111104185A (en) | 2019-12-20 | 2019-12-20 | File analysis method, device, system and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111104185A true CN111104185A (en) | 2020-05-05 |
Family
ID=70422704
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911327187.5A Pending CN111104185A (en) | 2019-12-20 | 2019-12-20 | File analysis method, device, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111104185A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160110238A1 (en) * | 2014-10-16 | 2016-04-21 | International Business Machines Corporation | Automated diagnosis of software crashes |
| CN107133143A (en) * | 2017-04-25 | 2017-09-05 | 努比亚技术有限公司 | Restart daily record merging method, method for uploading, system and readable storage medium storing program for executing |
| CN107241212A (en) * | 2017-04-20 | 2017-10-10 | 努比亚技术有限公司 | A kind of log processing method and device, equipment |
| CN110442519A (en) * | 2019-07-23 | 2019-11-12 | 深圳市六度人和科技有限公司 | A kind of crash file processing method, device, electronic equipment and storage medium |
-
2019
- 2019-12-20 CN CN201911327187.5A patent/CN111104185A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160110238A1 (en) * | 2014-10-16 | 2016-04-21 | International Business Machines Corporation | Automated diagnosis of software crashes |
| CN107241212A (en) * | 2017-04-20 | 2017-10-10 | 努比亚技术有限公司 | A kind of log processing method and device, equipment |
| CN107133143A (en) * | 2017-04-25 | 2017-09-05 | 努比亚技术有限公司 | Restart daily record merging method, method for uploading, system and readable storage medium storing program for executing |
| CN110442519A (en) * | 2019-07-23 | 2019-11-12 | 深圳市六度人和科技有限公司 | A kind of crash file processing method, device, electronic equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 张婧;周安民;刘亮;贾鹏;刘露平;: "Crash可利用性分析方法研究综述" * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107704360B (en) | Monitoring data processing method, equipment, server and storage medium | |
| CN108696589B (en) | Block chain data transmission method, device, equipment and storage medium | |
| CN112350854B (en) | Flow fault positioning method, device, equipment and storage medium | |
| CN109684155B (en) | Monitoring configuration method, device, equipment and readable storage medium | |
| US11449488B2 (en) | System and method for processing logs | |
| CN110650503B (en) | Network access method, device, system and computer readable storage medium | |
| US10404568B2 (en) | Agent manager for distributed transaction monitoring system | |
| CN103618626A (en) | Method and system for generating safety analysis report on basis of logs | |
| CN112306802A (en) | Data acquisition method, device, medium and electronic equipment of system | |
| CN110932918A (en) | Log data acquisition method and device and storage medium | |
| KR20180037342A (en) | Application software error monitoring, statistics management service and solution method. | |
| CN114450920A (en) | Distributed security detection system, method, device and storage medium | |
| EP3151124A1 (en) | On-board information system and information processing method therefor | |
| US11636198B1 (en) | System and method for cybersecurity analyzer update and concurrent management system | |
| CN110049004B (en) | Method for generating white list baseline of industrial control environment traffic | |
| CN111158654A (en) | Algorithm calling method, device, server and storage medium | |
| CN115729727A (en) | Fault repairing method, device, equipment and medium | |
| CN113630418A (en) | Network service identification method, device, equipment and medium | |
| CN109067622A (en) | State detection method, apparatus and network server | |
| CN112306871A (en) | Data processing method, device, equipment and storage medium | |
| US11308212B1 (en) | Adjudicating files by classifying directories based on collected telemetry data | |
| CN112148545A (en) | Security baseline detection method and security baseline detection system of embedded system | |
| CN110275785B (en) | Data processing method and device, client and server | |
| US20170223136A1 (en) | Any Web Page Reporting and Capture | |
| CN110213310B (en) | Method, device and storage medium for acquiring path of network service |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200505 |
|
| RJ01 | Rejection of invention patent application after publication |