CN112181695A - Abnormal application processing method, device, server and storage medium - Google Patents
Abnormal application processing method, device, server and storage medium Download PDFInfo
- Publication number
- CN112181695A CN112181695A CN201910584539.9A CN201910584539A CN112181695A CN 112181695 A CN112181695 A CN 112181695A CN 201910584539 A CN201910584539 A CN 201910584539A CN 112181695 A CN112181695 A CN 112181695A
- Authority
- CN
- China
- Prior art keywords
- abnormal
- application
- exception
- information
- stack information
- 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
- 230000002159 abnormal effect Effects 0.000 title claims abstract description 409
- 238000003672 processing method Methods 0.000 title claims description 27
- 238000012545 processing Methods 0.000 claims abstract description 40
- 238000000034 method Methods 0.000 claims abstract description 33
- 230000005856 abnormality Effects 0.000 claims description 40
- 238000004458 analytical method Methods 0.000 claims description 16
- 238000004590 computer program Methods 0.000 claims description 4
- 230000006870 function Effects 0.000 description 13
- 238000007726 management method Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 5
- 230000007547 defect Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- 238000013523 data management Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the application discloses a method, a device, a server and a storage medium for processing abnormal applications, and the embodiment of the application can acquire abnormal information of the abnormal applications; acquiring a symbol table corresponding to abnormal application according to the abnormal information; analyzing the symbol table to obtain abnormal stack information; determining a source file path corresponding to abnormal application and a code position where the abnormal occurs according to the abnormal stack information; and determining a corresponding exception handler according to the source file path and the code position, and informing the exception handler. According to the scheme, the corresponding symbol table is obtained through the abnormal information of the abnormal application, the abnormal stack information is obtained based on the symbol table, and the source file path corresponding to the abnormal application and the code position where the abnormal occurs are quickly positioned according to the abnormal stack information, so that a corresponding abnormal processor is informed to process in time, manual feedback is avoided, the position of the abnormal application can be quickly positioned, and the efficiency of processing the abnormal application is greatly improved.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, a server, and a storage medium for processing an abnormal application.
Background
With the development of the mobile internet, applications on the terminal are more and more abundant, and due to the increase of the applications and the increase of the complexity of the applications, the timeliness of problem repair on the software level on the terminal is greatly challenged. For example, when the application on the terminal is abnormal, the user of the terminal feeds back the abnormal problem to the customer service of the operator, and the customer service contacts the technician to perform abnormal troubleshooting and positioning, so that abnormal positioning corresponding to the abnormal application of the terminal is slow, and the efficiency of processing the abnormal application is low.
Disclosure of Invention
The embodiment of the application provides an abnormal application processing method, an abnormal application processing device, a server and a storage medium, and the abnormal application processing efficiency can be improved.
In a first aspect, an embodiment of the present application provides an abnormal application processing method, including:
acquiring abnormal information of abnormal application;
acquiring a symbol table corresponding to the abnormal application according to the abnormal information;
analyzing the symbol table to obtain abnormal stack information;
determining a source file path corresponding to the abnormal application and a code position where the abnormality occurs according to the abnormal stack information;
and determining a corresponding exception handler according to the source file path and the code position, and informing the exception handler.
In some embodiments, the obtaining exception information for the exception application includes:
receiving abnormal information sent by a terminal, wherein the abnormal information is collected by the terminal when the terminal monitors that the application is abnormal, and the abnormal information comprises an application name, an application version number, an abnormal module name in the application, an abnormal module version number and abnormal stack information.
In some embodiments, the obtaining, according to the exception information, a symbol table corresponding to the exception application includes:
extracting an application version number and an application name from the abnormal information;
and searching a symbol table corresponding to the abnormal application according to the application version number and the application name.
In some embodiments, the determining, according to the exception stack information, a source file path corresponding to the exception application and a code location where the exception occurs includes:
judging whether the abnormal stack information is processed or not;
if the abnormal stack information is not processed, reversely analyzing the abnormal stack information and positioning to a source file path where the abnormality occurs and a code position where the abnormality occurs in the abnormal application.
In some embodiments, after determining whether the exception stack information has been processed, the method further comprises:
and if the exception stack information is processed, updating the number of times of exception occurrence of the exception application.
In some embodiments, the determining whether the exception stack information has been processed comprises:
generating an abstract according to the abnormal stack information;
generating a signature according to the abnormal type and the abstract of the abnormal application, and judging whether the abnormality with the same signature exists or not;
if so, determining that the exception stack information is processed;
and if not, determining that the exception stack information is not processed.
In some embodiments, the reversely analyzing the exception stack information to locate a source file path of the exception occurrence and a code location of the exception occurrence in the exception application comprises:
and reversely analyzing the abnormal stack information according to a strategy that the weight of the internal code is higher than that of the external public code.
In some embodiments, said determining a corresponding exception handler from said source file path and code location, and notifying said exception handler comprises:
determining a corresponding exception handler according to the source file path and the code position;
when the exception handler is a preset internal person, informing the internal person;
and when the exception handler is not a preset internal person, determining a code module corresponding to the code position, and informing a maintainer corresponding to the code module.
In some embodiments, said determining a respective exception handler from said source file path and code location comprises:
acquiring code warehouse information according to the application version number and the abnormal module version number;
and determining a corresponding exception handler according to the source file path, the code position and the code warehouse information.
In some embodiments, said notifying said exception handler comprises:
and establishing an abnormal item to be processed according to the abnormal information, and sending the abnormal item to a client corresponding to an abnormal processor through a mail or a short message so as to inform the abnormal processor to process the abnormal item.
In a second aspect, an embodiment of the present application further provides an abnormal application processing apparatus, including:
the first acquisition module is used for acquiring abnormal information of the abnormal application;
a second obtaining module, configured to obtain, according to the abnormal information, a symbol table corresponding to the abnormal application;
the analysis module is used for analyzing the symbol table to obtain abnormal stack information;
the determining module is used for determining a source file path corresponding to the abnormal application and a code position where the abnormality occurs according to the abnormal stack information;
and the processing module is used for determining a corresponding exception handler according to the source file path and the code position and informing the exception handler.
In some embodiments, the first obtaining module is specifically configured to:
receiving abnormal information sent by a terminal, wherein the abnormal information is collected by the terminal when the terminal monitors that the application is abnormal, and the abnormal information comprises an application name, an application version number, an abnormal module name in the application, an abnormal module version number and abnormal stack information.
In some embodiments, the second obtaining module is specifically configured to:
extracting an application version number and an application name from the abnormal information;
and searching a symbol table corresponding to the abnormal application according to the application version number and the application name.
In some embodiments, the determining module comprises:
the judging unit is used for judging whether the abnormal stack information is processed or not;
and the positioning unit is used for reversely analyzing the abnormal stack information and positioning a source file path in which the abnormality occurs and a code position in which the abnormality occurs in the abnormal application if the abnormal stack information is not processed.
In some embodiments, the determining module further comprises:
and the updating unit is used for updating the abnormal occurrence frequency of the abnormal application if the abnormal stack information is processed.
In some embodiments, the determining unit is specifically configured to:
generating an abstract according to the abnormal stack information;
generating a signature according to the abnormal type and the abstract of the abnormal application, and judging whether the abnormality with the same signature exists or not;
if so, determining that the exception stack information is processed;
and if not, determining that the exception stack information is not processed.
In some embodiments, the positioning unit is specifically configured to:
and reversely analyzing the abnormal stack information according to a strategy that the weight of the internal code is higher than that of the external public code.
In some embodiments, the processing module comprises:
the determining unit is used for determining a corresponding exception handler according to the source file path and the code position;
the first notification unit is used for notifying the internal personnel when the exception handler is preset internal personnel;
and the second notification unit is used for determining the code module corresponding to the code position and notifying a maintainer corresponding to the code module when the exception handler is not a preset internal person.
In some embodiments, the determining unit is specifically configured to:
acquiring code warehouse information according to the application version number and the abnormal module version number;
and determining a corresponding exception handler according to the source file path, the code position and the code warehouse information.
In some embodiments, the processing module is specifically configured to:
determining a corresponding exception handler according to the source file path and the code position; and establishing an abnormal item to be processed according to the abnormal information, and sending the abnormal item to a client corresponding to an abnormal processor through a mail or a short message so as to inform the abnormal processor to process the abnormal item.
In a third aspect, an embodiment of the present application further provides a server, including a memory and a processor, where the memory stores a computer program, and the processor executes any one of the abnormal application processing methods provided in the embodiment of the present application when calling the computer program in the memory.
In a fourth aspect, an embodiment of the present application further provides a storage medium, where the storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute any one of the exception application processing methods provided in the embodiment of the present application.
According to the embodiment of the application, the abnormal information of the abnormal application can be obtained, the symbol table corresponding to the abnormal application is obtained according to the abnormal information, the symbol table is analyzed to obtain the abnormal stack information, at the moment, the source file path corresponding to the abnormal application and the code position where the abnormality occurs can be determined according to the abnormal stack information, and finally, the corresponding abnormality handler is determined according to the source file path and the code position and is informed to the abnormality handler. According to the scheme, the corresponding symbol table is obtained through the abnormal information of the abnormal application, the abnormal stack information is obtained based on the symbol table, and the source file path corresponding to the abnormal application and the code position where the abnormal occurs are quickly positioned according to the abnormal stack information, so that a corresponding abnormal processor is informed to process in time, manual feedback is avoided, the position of the abnormal application can be quickly positioned, and the efficiency of processing the abnormal application is greatly improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of an abnormal application processing method provided in an embodiment of the present application;
fig. 2 is another schematic flow chart of an abnormal application processing method provided in an embodiment of the present application;
FIG. 3 is a system architecture diagram of exception application processing provided by an embodiment of the present application;
fig. 4 is a schematic structural diagram of an abnormal application processing apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a schematic flowchart illustrating an exception application handling method according to an embodiment of the present application. The execution main body of the abnormal application processing method may be the abnormal application processing device provided in the embodiment of the present application, or a server integrated with the abnormal application processing device, where the abnormal application processing device may be implemented in a hardware or software manner. The abnormal application processing method can comprise the following steps:
s101, obtaining abnormal information of abnormal application.
The abnormal application can be an application on the terminal, and the application can include various applications such as an applet, an instant messaging application, a mailbox application, a camera application, a payment application, a shopping application, a search engine application, a map application, an audio and video application and the like on the terminal, and kernels and drivers of various operating systems such as an iOS (internet of things) system, an Android system and an internet of things embedded terminal system.
In some embodiments, obtaining exception information for the exception application may include: the method includes the steps of receiving abnormal information sent by a terminal, wherein the abnormal information is collected when the terminal monitors that own application is abnormal, the abnormal information can include an application name, an application version number, an abnormal module name in the application, an abnormal module version number, abnormal stack information and the like, the abnormal stack information can include a stack path of an execution function with the abnormal occurrence, and the abnormal module can be a module in the abnormal application, for example, for payment application, a payment module, a income module and the like can be included.
And S102, obtaining a symbol table corresponding to the abnormal application according to the abnormal information.
After obtaining the exception information of the abnormal application, a symbol table corresponding to the abnormal application may be obtained, where the symbol table may be a data structure used in a language translator (e.g., a compiler and an interpreter), and each identifier of the program source code is bound with its declaration or usage information, such as its data type, scope, and memory address.
In some embodiments, obtaining, according to the exception information, a symbol table corresponding to the exception application may include: extracting an application version number and an application name from the abnormal information; and searching a symbol table corresponding to the abnormal application according to the application version number and the application name.
The application symbol table can be stored in the database in association with the application version number, the application name and the like, so that the application version number and the application name can be extracted from the abnormal information after the abnormal information is obtained, and then the symbol table corresponding to the abnormal application can be searched from the database according to the application version number and the application name.
And S103, analyzing the symbol table to obtain abnormal stack information.
After the symbol table corresponding to the abnormal application is obtained, the symbol table may be analyzed to obtain the abnormal stack information, for example, the symbol table may be subjected to analysis operations such as confusion resolution and address binding, so that the abnormal stack information of the source code level may be analyzed.
S104, determining a source file path corresponding to the abnormal application and a code position where the abnormality occurs according to the abnormal stack information.
Since the exception stack information may include a stack path of an execution function in which an exception occurs, a source file path corresponding to the exception application, a code position in which the exception occurs, and the like may be determined according to the exception stack information, where the code position may include a function in which the code is located or a line number in which the code is located.
In some embodiments, determining a source file path corresponding to the exception application and a code position where the exception occurs according to the exception stack information may include: judging whether the abnormal stack information is processed or not; if the abnormal stack information is not processed, reversely analyzing the abnormal stack information, and positioning a source file path where the abnormality occurs and a code position where the abnormality occurs in the abnormal application; and if the exception stack information is processed, updating the number of times of exception occurrence of the exception application.
In order to avoid repeatedly processing the same exception application and improve the processing efficiency and reliability of the exception application, after obtaining the exception stack information, it may be determined whether the exception stack information has been processed, and in some embodiments, determining whether the exception stack information has been processed may include: generating an abstract according to the abnormal stack information; generating a signature according to the abnormal type and the abstract of the abnormal application, and judging whether the same signature is abnormal or not; if so, determining that the abnormal stack information is processed; if not, determining that the exception stack information is not processed.
For example, the summary may be generated according to the stack of the abnormal stack information, or the summary may be generated according to the model of the terminal where the stack application of the abnormal stack information is located, the application version number, and the like, and the signature may be generated according to the abnormal type of the abnormal application and the summary, where the abnormal type may include application deadness, insufficient memory, application flash back, and the like. Then, judging whether the abnormity of the same signature exists; if so, determining that the abnormal stack information is processed; if not, determining that the exception stack information is not processed.
And if the exception stack information is processed, updating the number of times of exception occurrence of the exception application. If the abnormal stack information is not processed, the abnormal stack information is reversely analyzed, and a source file path where the abnormality occurs and a code position where the abnormality occurs in the abnormal application are located.
In some embodiments, reversely analyzing the exception stack information, locating a source file path of the exception occurrence and a code location of the exception occurrence in the exception application may include: and reversely analyzing the abnormal stack information according to a strategy that the weight of the internal code is higher than that of the external public code.
For example, the analysis may be performed reversely according to the path in the exception stack information from the most recent function of the stack, so as to trace back to the source file path where the exception occurs, during the analysis, the weight of the internal code is higher than that of the external common system code, the higher the weight, the higher the priority, and the analysis will be prioritized during the analysis, whereas, the lower the weight, the lower the priority, and the analysis will be delayed during the analysis. For example, the internal code is preferentially analyzed in the analysis process, and when the code position of the exception occurrence is the internal code and the external public system code, the exception handler corresponding to the internal code can be preferentially determined, and the exception handler is notified. The internal code can be private code maintained inside the development company, and the external public system code can be common code which can be called by all the development companies.
S105, determining a corresponding exception handler according to the source file path and the code position, and informing the exception handler.
In order to improve the rapidity and flexibility of exception application processing, after a source file path and a code position where an exception occurs are located, a corresponding exception handler can be determined according to the source file path and the code position. For example, the association relationship between the application version number, the version number of the abnormal module, the code warehouse information, the source file path, and other information may be stored in advance, in the process of determining the corresponding abnormal handler, the code warehouse information may be obtained according to the application version number and the version number of the abnormal module, and the code warehouse information may include information of a person related to development or maintenance of the application code, and then the corresponding abnormal handler may be determined according to the source file path, the code position, and the code warehouse information. At this time, the exception handler, which may be a person related to developing or maintaining the code of the application, may be notified in the form of a mail or a short message.
In some embodiments, determining a corresponding exception handler from the source file path and the code location, and notifying the exception handler may include: determining a corresponding exception handler according to the source file path and the code position; when the exception handler is a preset internal person, informing the internal person; and when the exception handler is not a preset inside person, determining a code module corresponding to the code position, and notifying a maintainer corresponding to the code module.
For example, after an exception handler (also referred to as a code author) corresponding to the exception application is analyzed according to the source file path and the code position, in combination with the version number and the code warehouse information of the exception application, it may be determined whether the exception handler is a preset insider, where the preset insider may be an insider of a company that develops or maintains the private code of the application. When the exception handler is a preset internal person, the matching person is finished, and the internal person can be notified; when the exception handler is not the preset insider, the exception handler may be automatically matched to a module responsible person (i.e., inside person), for example, the code module corresponding to the code position may be determined, and since each code module may be provided with the corresponding inside person to follow up, a maintainer corresponding to the code module may be notified, and the maintainer is the inside person who follows up and maintains the code module.
In some embodiments, notifying the exception handler may include: and establishing an abnormal item to be processed according to the abnormal information, and sending the abnormal item to a client corresponding to the abnormal processor through a mail or a short message so as to inform the abnormal processor to process the abnormal item.
For example, an abnormal item to be processed (i.e., a BUG defect) may be established according to the application name, the application version number, the name of the abnormal module in the application, the version number of the abnormal module, the abnormal stack information, and other abnormal information, and then the abnormal item may be sent to the client corresponding to the abnormal handler in a manner of mail or short message, so as to notify the abnormal handler to process the abnormal item in time. And counting according to the exception handler, the exception module, the exception type, the exception occurrence frequency and the like, and informing each related person in a timed manner through a mail or other manners. By automatically acquiring the abnormal information and automatically analyzing and positioning the abnormal occurrence condition, the rapid positioning capability of the abnormal occurrence position of the abnormal application is improved, the circulation flow of the abnormal processing is shortened, and the rapid repair of the application abnormality is promoted.
According to the embodiment of the application, the abnormal information of the abnormal application can be obtained, the symbol table corresponding to the abnormal application is obtained according to the abnormal information, the symbol table is analyzed to obtain the abnormal stack information, at the moment, the source file path corresponding to the abnormal application and the code position where the abnormality occurs can be determined according to the abnormal stack information, and finally, the corresponding abnormality handler is determined according to the source file path and the code position and is informed to the abnormality handler. According to the scheme, the corresponding symbol table is obtained through the abnormal information of the abnormal application, the abnormal stack information is obtained based on the symbol table, and the source file path corresponding to the abnormal application and the code position where the abnormal occurs are quickly positioned according to the abnormal stack information, so that a corresponding abnormal processor is informed to process in time, manual feedback is avoided, the position of the abnormal application can be quickly positioned, and the efficiency of processing the abnormal application is greatly improved.
The exception application handling method described in the above embodiment will be described in further detail below.
Referring to fig. 2, fig. 2 is another schematic flow chart of the abnormal application processing method provided in this embodiment of the present application, and the following takes a server as an example to process an abnormal application on a terminal, as shown in fig. 3, the terminal may include modules such as a terminal application abnormality (i.e., an abnormal application on the terminal) and an application monitoring service, the server may include an application version management system, an abnormality analysis system, a symbol table data management system, a defect management system, a code warehouse system, and the like, and the flow of the abnormal application processing method may be as follows:
s201, the terminal monitors whether the application of the terminal is abnormal or not, and if the application of the terminal is abnormal, abnormal information is collected.
The terminal can monitor whether the application of the terminal is abnormal or not through the application monitoring service, and if the terminal monitors that the application is not abnormal, application abnormity processing is not needed; if the terminal monitors that the application is abnormal, abnormal information such as an application name, an application version number, an abnormal module name in the application, an abnormal module version number, abnormal stack information and the like is collected.
S202, the terminal sends the abnormal information to the server.
The terminal can upload the abnormal information to the abnormal analysis system of the server through the application monitoring service.
And S203, the server acquires the symbol table according to the abnormal information.
Because the applied symbol table can be stored in the database of the symbol table data management system in association with the application version number, the application name and the like, after the abnormal information is obtained, the server can obtain the data request information of the symbol table from the application version management system through the abnormal analysis system based on the information of the application version number, the application name and the like in the abnormal information, and obtain the corresponding symbol table from the symbol table data management system according to the data request information.
And S204, the server analyzes the symbol table to obtain abnormal stack information.
After obtaining the symbol table corresponding to the abnormal application, the server may analyze the symbol table through the abnormal analysis system to obtain the abnormal stack information, for example, may perform analysis operations such as confusion resolution and address binding on the symbol table, so as to analyze the abnormal stack information at the source code level.
S205, the server analyzes the abnormal stack information and positions a source file path and a code position where the abnormality occurs.
Since the exception stack information may include a stack path of an execution function in which an exception occurs, a source file path corresponding to the exception application, a code position in which the exception occurs, and the like may be determined according to the exception stack information, where the code position may include a function in which the code is located or a line number in which the code is located.
In order to improve the processing efficiency and reliability of the abnormal application, after the abnormal stack information is obtained, whether the abnormal stack information is processed or not can be judged, for example, a summary can be generated according to the abnormal stack information; and generating a signature according to the abnormal type and the abstract of the abnormal application, wherein the abnormal type can comprise application jamming, insufficient memory, application flash quit and the like. Then, judging whether the abnormity of the same signature exists; if the stack exception information exists, the exception stack information is determined to be processed, and the number of times of exception occurrence of the exception application can be updated at the moment; if the abnormal stack information does not exist, determining that the abnormal stack information is not processed, and reversely analyzing the abnormal stack information according to a strategy that the weight of the internal code is higher than that of the external public code, and positioning a source file path where the abnormality occurs and a code position where the abnormality occurs in the abnormal application.
S206, the server determines an exception handler according to the source file path and the code position.
S207, the server establishes an abnormal item to be processed.
And S208, the server sends the abnormal item to the client corresponding to the abnormal processor.
In order to improve the rapidity and flexibility of exception application processing, after a source file path and a code position where an exception occurs are located, a corresponding exception handler can be determined according to the source file path and the code position. For example, the code repository information may be obtained from the application version management system based on information such as the application version number and the application name in the exception information, and the exception handler may be obtained from the code repository system according to the code repository information.
After determining the exception handler, it may be determined whether the exception handler is a preset insider, which may be an insider of a company that develops or maintains the application private code. When the exception handler is a preset internal person, the matching person completes the process, an exception item to be processed can be established through the defect management system according to the application name, the application version number, the name of the exception module in the application, the version number of the exception module, the exception stack information and other exception information, and the exception item is sent to the client corresponding to the internal person. When the exception handler is not a preset insider, the exception handler may be automatically matched to a module principal (i.e., an insider), an exception item to be processed may be established by the defect management system, and the exception item may be sent to the client corresponding to the module principal, for example, a code module corresponding to a code position may be determined, and since each code module may be provided with a corresponding inside person to follow up, a maintainer corresponding to the code module may be notified, and the maintainer is an inside person who follows up and maintains the code module.
S209, the abnormal processor processes the abnormal item.
After the client corresponding to the exception handler receives the exception item, the exception handler can check the exception item and process the exception item in time.
According to the method and the device, the server can obtain the abnormal information of the abnormal application on the terminal, then obtains the symbol table corresponding to the abnormal application according to the abnormal information, then analyzes the symbol table to obtain the abnormal stack information, at the moment, the source file path corresponding to the abnormal application and the code position where the abnormality occurs can be determined according to the abnormal stack information, and finally, the corresponding abnormality processor is determined according to the source file path and the code position and is informed to the abnormality processor. According to the scheme, the abnormal information of the abnormal application is automatically acquired, the corresponding symbol table is acquired based on the abnormal information, the abnormal stack information is acquired based on the symbol table, the source file path corresponding to the abnormal application and the code position where the abnormal application occurs are quickly positioned according to the abnormal stack information, so that a corresponding abnormal processor is informed to timely process, the condition where the abnormal application occurs is automatically analyzed and positioned, manual feedback is avoided, the position where the abnormal application occurs can be quickly positioned, the circulation flow of the abnormal processing is shortened, the efficiency of processing the abnormal application is greatly improved, and the quick restoration of the application abnormality is further promoted.
In order to better implement the abnormal application processing method provided in the embodiments of the present application, an embodiment of the present application further provides a device based on the abnormal application processing method. The meaning of the noun is the same as that in the above abnormal application processing method, and the specific implementation details can refer to the description in the method embodiment.
Referring to fig. 4, fig. 4 is a schematic structural diagram of an abnormal application processing apparatus according to an embodiment of the present disclosure, wherein the abnormal application processing apparatus 300 may include a first obtaining module 301, a second obtaining module 302, an analyzing module 303, a determining module 304, a processing module 305, and the like.
The first obtaining module 301 is configured to obtain exception information of an exception application.
A second obtaining module 302, configured to obtain, according to the exception information, a symbol table corresponding to the exception application.
And the analysis module 303 is configured to analyze the symbol table to obtain the abnormal stack information.
The determining module 304 is configured to determine, according to the exception stack information, a source file path corresponding to the exception application and a code position where the exception occurs.
And the processing module 305 is used for determining a corresponding exception handler according to the source file path and the code position and notifying the exception handler.
In some embodiments, the first obtaining module 301 is specifically configured to: and receiving abnormal information sent by the terminal, wherein the abnormal information is collected by the terminal when the terminal monitors that the application is abnormal, and the abnormal information comprises an application name, an application version number, an abnormal module name in the application, an abnormal module version number and abnormal stack information.
In some embodiments, the second obtaining module 302 is specifically configured to: extracting an application version number and an application name from the abnormal information; and searching a symbol table corresponding to the abnormal application according to the application version number and the application name.
In some implementations, the determining module 304 can include:
the judging unit is used for judging whether the abnormal stack information is processed or not;
and the positioning unit is used for reversely analyzing the abnormal stack information and positioning a source file path in which the abnormality occurs and a code position in which the abnormality occurs in the abnormal application if the abnormal stack information is not processed.
In some implementations, the determining module 304 can further include:
and the updating unit is used for updating the abnormal occurrence frequency of the abnormal application if the abnormal stack information is processed.
In some embodiments, the determining unit is specifically configured to: generating an abstract according to the abnormal stack information; generating a signature according to the abnormal type and the abstract of the abnormal application, and judging whether the same signature is abnormal or not; if so, determining that the abnormal stack information is processed; if not, determining that the exception stack information is not processed.
In some embodiments, the positioning unit is specifically configured to: and reversely analyzing the abnormal stack information according to a strategy that the weight of the internal code is higher than that of the external public code.
In some embodiments, the processing module 305 may include:
the determining unit is used for determining a corresponding exception handler according to the source file path and the code position;
the first notification unit is used for notifying the inside personnel when the exception handler is the preset inside personnel;
and the second notification unit is used for determining the code module corresponding to the code position and notifying a maintainer corresponding to the code module when the exception handler is not a preset insider.
In some embodiments, the determining unit is specifically configured to: acquiring code warehouse information according to the application version number and the abnormal module version number; and determining a corresponding exception handler according to the source file path, the code position and the code warehouse information.
In some embodiments, the processing module is specifically configured to: determining a corresponding exception handler according to the source file path and the code position; and establishing an abnormal item to be processed according to the abnormal information, and sending the abnormal item to a client corresponding to the abnormal processor through a mail or a short message so as to inform the abnormal processor to process the abnormal item.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
In the embodiment of the present application, the first obtaining module 301 may obtain exception information of the exception application, the second obtaining module 302 may obtain a symbol table corresponding to the exception application according to the exception information, the parsing module 303 may parse the symbol table to obtain exception stack information, the determining module 304 may determine a source file path and a code position where the exception occurs corresponding to the exception application according to the exception stack information, and the processing module 305 may determine a corresponding exception handler according to the source file path and the code position and notify the exception handler. According to the scheme, the corresponding symbol table is obtained through the abnormal information of the abnormal application, the abnormal stack information is obtained based on the symbol table, and the source file path corresponding to the abnormal application and the code position where the abnormal occurs are quickly positioned according to the abnormal stack information, so that a corresponding abnormal processor is informed to process in time, manual feedback is avoided, the position of the abnormal application can be quickly positioned, and the efficiency of processing the abnormal application is greatly improved.
The embodiment of the present application further provides a server, as shown in fig. 5, which shows a schematic structural diagram of the server according to the embodiment of the present application, specifically:
the server may include components such as a processor 401 of one or more processing cores, memory 402 of one or more computer-readable storage media, a power supply 403, and an input unit 404. Those skilled in the art will appreciate that the server architecture shown in FIG. 5 is not meant to be limiting, and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components. Wherein:
the processor 401 is a control center of the server, connects various parts of the entire server using various interfaces and lines, and performs various functions of the server and processes data by running or executing software programs and/or modules stored in the memory 402 and calling data stored in the memory 402, thereby performing overall monitoring of the server. Optionally, processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 401.
The memory 402 may be used to store software programs and modules, and the processor 401 executes various functional applications and data processing by operating the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data created according to the use of the server, and the like. Further, the memory 402 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 access to the memory 402.
The server further includes a power supply 403 for supplying power to each component, and preferably, the power supply 403 may be logically connected to the processor 401 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The power supply 403 may also include any component of one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.
The server may also include an input unit 404, the input unit 404 being operable to receive input numeric or character information and to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
Although not shown, the server may further include a display unit and the like, which will not be described in detail herein. Specifically, in this embodiment, the processor 401 in the server loads the executable file corresponding to the process of one or more application programs into the memory 402 according to the following instructions, and the processor 401 runs the application program stored in the memory 402, thereby implementing various functions as follows:
acquiring abnormal information of abnormal application; acquiring a symbol table corresponding to abnormal application according to the abnormal information; analyzing the symbol table to obtain abnormal stack information; determining a source file path corresponding to abnormal application and a code position where the abnormal occurs according to the abnormal stack information; and determining a corresponding exception handler according to the source file path and the code position, and informing the exception handler.
In some embodiments, obtaining exception information for the exception application may include: and receiving abnormal information sent by the terminal, wherein the abnormal information is collected by the terminal when the terminal monitors that the application is abnormal, and the abnormal information comprises an application name, an application version number, an abnormal module name in the application, an abnormal module version number and abnormal stack information.
In some embodiments, obtaining, according to the exception information, a symbol table corresponding to the exception application may include: extracting an application version number and an application name from the abnormal information; and searching a symbol table corresponding to the abnormal application according to the application version number and the application name.
In some embodiments, determining a source file path corresponding to the exception application and a code position where the exception occurs according to the exception stack information may include: judging whether the abnormal stack information is processed or not; if the abnormal stack information is not processed, the abnormal stack information is reversely analyzed, and a source file path where the abnormality occurs and a code position where the abnormality occurs in the abnormal application are located.
In some embodiments, after determining whether the exception stack information has been processed, the method further includes: and if the exception stack information is processed, updating the number of times of exception occurrence of the exception application.
In some embodiments, determining whether exception stack information has been processed may include: generating an abstract according to the abnormal stack information; generating a signature according to the abnormal type and the abstract of the abnormal application, and judging whether the same signature is abnormal or not; if so, determining that the abnormal stack information is processed; if not, determining that the exception stack information is not processed.
In some embodiments, reversely analyzing the exception stack information, locating a source file path of the exception occurrence and a code location of the exception occurrence in the exception application may include: and reversely analyzing the abnormal stack information according to a strategy that the weight of the internal code is higher than that of the external public code.
In some embodiments, determining a corresponding exception handler from the source file path and the code location, and notifying the exception handler may include: determining a corresponding exception handler according to the source file path and the code position; when the exception handler is a preset internal person, informing the internal person; and when the exception handler is not a preset inside person, determining a code module corresponding to the code position, and notifying a maintainer corresponding to the code module.
In some embodiments, determining the respective exception handler from the source file path and the code location may include: acquiring code warehouse information according to the application version number and the abnormal module version number; and determining a corresponding exception handler according to the source file path, the code position and the code warehouse information.
In some embodiments, notifying the exception handler may include: and establishing an abnormal item to be processed according to the abnormal information, and sending the abnormal item to a client corresponding to the abnormal processor through a mail or a short message so as to inform the abnormal processor to process the abnormal item.
In the above embodiments, the descriptions of the embodiments have respective emphasis, and parts that are not described in detail in a certain embodiment may refer to the above detailed description of the abnormal application processing method, and are not described herein again.
It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.
To this end, the present application provides a storage medium, in which a plurality of instructions are stored, where the instructions can be loaded by a processor to execute the steps in any one of the exception application processing methods provided in the embodiments of the present application. For example, the instructions may perform the steps of:
acquiring abnormal information of abnormal application; acquiring a symbol table corresponding to abnormal application according to the abnormal information; analyzing the symbol table to obtain abnormal stack information; determining a source file path corresponding to abnormal application and a code position where the abnormal occurs according to the abnormal stack information; and determining a corresponding exception handler according to the source file path and the code position, and informing the exception handler.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
Wherein the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
Since the instructions stored in the storage medium may execute the steps in any abnormal application processing method provided in the embodiments of the present application, beneficial effects that can be achieved by any abnormal application processing method provided in the embodiments of the present application may be achieved, which are detailed in the foregoing embodiments and will not be described herein again.
The foregoing describes in detail a method, an apparatus, a server, and a storage medium for processing abnormal applications provided in the embodiments of the present application, and a specific example is applied in the present application to explain the principles and embodiments of the present application, and the description of the foregoing embodiments is only used to help understand the method and the core idea of the present application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. An abnormal application processing method is characterized by comprising the following steps:
acquiring abnormal information of abnormal application;
acquiring a symbol table corresponding to the abnormal application according to the abnormal information;
analyzing the symbol table to obtain abnormal stack information;
determining a source file path corresponding to the abnormal application and a code position where the abnormality occurs according to the abnormal stack information;
and determining a corresponding exception handler according to the source file path and the code position, and informing the exception handler.
2. The abnormal application processing method according to claim 1, wherein the obtaining of the symbol table corresponding to the abnormal application according to the abnormal information includes:
extracting an application version number and an application name from the abnormal information;
and searching a symbol table corresponding to the abnormal application according to the application version number and the application name.
3. The abnormal application processing method according to claim 1, wherein the determining, according to the abnormal stack information, a source file path and a code position where an abnormality occurs corresponding to the abnormal application comprises:
judging whether the abnormal stack information is processed or not;
if the abnormal stack information is not processed, reversely analyzing the abnormal stack information and positioning to a source file path where the abnormality occurs and a code position where the abnormality occurs in the abnormal application.
And if the exception stack information is processed, updating the number of times of exception occurrence of the exception application.
4. The exception application processing method according to claim 3, wherein said determining whether the exception stack information has been processed comprises:
generating an abstract according to the abnormal stack information;
generating a signature according to the abnormal type and the abstract of the abnormal application;
judging whether an abnormal signature identical to the signature exists or not;
if so, determining that the exception stack information is processed;
and if not, determining that the exception stack information is not processed.
5. The abnormal application processing method according to claim 3, wherein the reversely analyzing the abnormal stack information and locating to a source file path where an abnormality occurs and a code position where an abnormality occurs in the abnormal application comprises:
and reversely analyzing the abnormal stack information according to a strategy that the weight of the internal code is higher than that of the external public code.
6. The abnormal application processing method according to any one of claims 1 to 5, wherein the determining a corresponding abnormal handler according to the source file path and the code position, and notifying the abnormal handler comprises:
determining a corresponding exception handler according to the source file path and the code position;
when the exception handler is a preset internal person, informing the internal person;
and when the exception handler is not a preset internal person, determining a code module corresponding to the code position, and informing a maintainer corresponding to the code module.
7. The abnormal application processing method according to any one of claims 1 to 5, wherein the notifying the abnormal handler includes:
and establishing an abnormal item to be processed according to the abnormal information, and sending the abnormal item to a client corresponding to an abnormal processor through a mail or a short message so as to inform the abnormal processor to process the abnormal item.
8. An abnormal application processing apparatus, comprising:
the first acquisition module is used for acquiring abnormal information of the abnormal application;
a second obtaining module, configured to obtain, according to the abnormal information, a symbol table corresponding to the abnormal application;
the analysis module is used for analyzing the symbol table to obtain abnormal stack information;
the determining module is used for determining a source file path corresponding to the abnormal application and a code position where the abnormality occurs according to the abnormal stack information;
and the processing module is used for determining a corresponding exception handler according to the source file path and the code position and informing the exception handler.
9. A server, comprising a processor and a memory, the memory having a computer program stored therein, the processor executing the exception application processing method according to any one of claims 1 to 7 when calling the computer program in the memory.
10. A storage medium storing a plurality of instructions adapted to be loaded by a processor to perform the exception application handling method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910584539.9A CN112181695A (en) | 2019-07-01 | 2019-07-01 | Abnormal application processing method, device, server and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910584539.9A CN112181695A (en) | 2019-07-01 | 2019-07-01 | Abnormal application processing method, device, server and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112181695A true CN112181695A (en) | 2021-01-05 |
Family
ID=73915283
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910584539.9A Pending CN112181695A (en) | 2019-07-01 | 2019-07-01 | Abnormal application processing method, device, server and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112181695A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113094240A (en) * | 2021-04-26 | 2021-07-09 | 北京顺达同行科技有限公司 | Application program abnormity monitoring method, mobile terminal and storage medium |
| CN114595198A (en) * | 2022-03-15 | 2022-06-07 | 北京字节跳动网络技术有限公司 | Breakdown analysis method and device, electronic equipment and storage medium |
| CN115016968A (en) * | 2022-06-02 | 2022-09-06 | 深圳市元征科技股份有限公司 | Exception handling method, device, equipment and medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030074605A1 (en) * | 2001-10-11 | 2003-04-17 | Hitachi, Ltd. | Computer system and method for program execution monitoring in computer system |
| CN101211309A (en) * | 2006-12-29 | 2008-07-02 | 中兴通讯股份有限公司 | Embedded system progress abnormal tracking position-finding method |
| CN107704356A (en) * | 2017-06-12 | 2018-02-16 | 平安科技（深圳）有限公司 | Exception stack information acquisition method, device and computer-readable recording medium |
| CN108111328A (en) * | 2016-11-24 | 2018-06-01 | 腾讯科技（深圳）有限公司 | A kind of abnormality eliminating method and device |
-
2019
- 2019-07-01 CN CN201910584539.9A patent/CN112181695A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030074605A1 (en) * | 2001-10-11 | 2003-04-17 | Hitachi, Ltd. | Computer system and method for program execution monitoring in computer system |
| CN101211309A (en) * | 2006-12-29 | 2008-07-02 | 中兴通讯股份有限公司 | Embedded system progress abnormal tracking position-finding method |
| CN108111328A (en) * | 2016-11-24 | 2018-06-01 | 腾讯科技（深圳）有限公司 | A kind of abnormality eliminating method and device |
| CN107704356A (en) * | 2017-06-12 | 2018-02-16 | 平安科技（深圳）有限公司 | Exception stack information acquisition method, device and computer-readable recording medium |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113094240A (en) * | 2021-04-26 | 2021-07-09 | 北京顺达同行科技有限公司 | Application program abnormity monitoring method, mobile terminal and storage medium |
| CN113094240B (en) * | 2021-04-26 | 2023-09-29 | 北京顺达同行科技有限公司 | Abnormality monitoring method for application program, mobile terminal and storage medium |
| CN114595198A (en) * | 2022-03-15 | 2022-06-07 | 北京字节跳动网络技术有限公司 | Breakdown analysis method and device, electronic equipment and storage medium |
| CN114595198B (en) * | 2022-03-15 | 2023-09-05 | 抖音视界有限公司 | Crash analysis method and device, electronic equipment and storage medium |
| CN115016968A (en) * | 2022-06-02 | 2022-09-06 | 深圳市元征科技股份有限公司 | Exception handling method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107819627B (en) | System fault processing method and server | |
| US8370816B2 (en) | Device, method and computer program product for evaluating a debugger script | |
| CN107451040B (en) | Method and device for positioning fault reason and computer readable storage medium | |
| CN108804215B (en) | Task processing method and device and electronic equipment | |
| CN112181695A (en) | Abnormal application processing method, device, server and storage medium | |
| CN110851324B (en) | Log-based routing inspection processing method and device, electronic equipment and storage medium | |
| CN109684038B (en) | Docker service container log processing method and device and electronic equipment | |
| CN110502318A (en) | Event-handling method, event processing server, storage medium and device | |
| CN107168844B (en) | Performance monitoring method and device | |
| CN110851471A (en) | Distributed log data processing method, device and system | |
| CN108595178B (en) | Hook-based data acquisition method, device and equipment | |
| CN107463492A (en) | Application failure localization method and device | |
| CN111522744A (en) | Service testing method, device and computer readable storage medium | |
| CN118277221A (en) | System abnormal data acquisition method and device, electronic equipment and storage medium | |
| CN105426544B (en) | Method and device for monitoring database state | |
| CN110597688A (en) | Monitoring information acquisition method and system | |
| CN107908525B (en) | Alarm processing method, equipment and readable storage medium | |
| CN111026794A (en) | Data management method, device, equipment and medium based on data source | |
| US10678749B2 (en) | Method and device for dispatching replication tasks in network storage device | |
| CN111756778A (en) | Server disk cleaning script pushing method and device and storage medium | |
| CN113297149A (en) | Method and device for monitoring data processing request | |
| CN112632559A (en) | Vulnerability automatic verification method, device, equipment and storage medium | |
| CN115185819A (en) | System testing method, device, equipment and computer readable storage medium | |
| CN113238901B (en) | Multi-device automatic testing method and device, storage medium and computer device | |
| CN115454876A (en) | Management method for code test and related equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |