CN107463492A - Application failure localization method and device - Google Patents
Application failure localization method and device Download PDFInfo
- Publication number
- CN107463492A CN107463492A CN201710517229.6A CN201710517229A CN107463492A CN 107463492 A CN107463492 A CN 107463492A CN 201710517229 A CN201710517229 A CN 201710517229A CN 107463492 A CN107463492 A CN 107463492A
- Authority
- CN
- China
- Prior art keywords
- format
- code
- file
- abnormal
- control identification
- 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
- 238000000034 method Methods 0.000 title claims abstract description 38
- 230000004807 localization Effects 0.000 title abstract 2
- 230000002159 abnormal effect Effects 0.000 claims abstract description 128
- 230000000007 visual effect Effects 0.000 claims description 10
- 238000000605 extraction Methods 0.000 claims description 7
- 230000005856 abnormality Effects 0.000 abstract description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000003068 static effect Effects 0.000 description 3
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/366—Software debugging using diagnostics
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3636—Software debugging by tracing the execution of the program
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (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 present invention, which provides a kind of application failure localization method and device, this method, to be included：The control mark of preset format is extracted in abnormal log；Obtain the control mark of string format corresponding to the control mark of the preset format；At least a line abnormality code is determined in source code according to the control of string format mark, the abnormality code includes the control mark of the string format；Obtain line number of the file identification and the abnormality code where the abnormality code in corresponding file.For improving the efficiency of application failure positioning.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a method and a device for positioning faults of an application program.
Background
At present, after an application program is released online, some exceptions usually occur in the application program in the process of using the application program by a user, and in order to solve the exceptions of the application program, an operation log of the application program needs to be acquired, and a fault of the application program is located according to the operation log of the application program.
In the prior art, a log collection module is usually arranged in an application program, and the log collection module can acquire log information generated in the running process of the application program and report the log information to a server. When research and development personnel need to locate a fault in an application program, the research and development personnel acquire abnormal log information from a server and analyze the log information by artificial abnormity to determine the type of a control which may have the fault.
However, because the amount of code in the source code library is too large, it takes a lot of time to search the source codes corresponding to all the controls corresponding to the type of the control from the source code library, and it also takes a lot of time to analyze the source codes corresponding to all the controls, so that the efficiency of locating the application program fault is low.
Disclosure of Invention
The embodiment of the invention provides an application program fault positioning method and device, which improve the efficiency of application program fault positioning.
In a first aspect, an embodiment of the present invention provides an application program fault location method, including:
extracting control identification in a preset format from the abnormal log;
acquiring a control identifier in a character string format corresponding to the control identifier in the preset format;
determining at least one row of abnormal codes in a source code according to the control identification in the character string format, wherein the abnormal codes comprise the control identification in the character string format;
and acquiring the file identifier of the abnormal code and the line number of the abnormal code in the corresponding file.
In a possible embodiment, the preset format is a decimal data format; correspondingly, extracting the control identification from the abnormal log comprises the following steps:
obtaining at least one decimal data in the exception log;
and determining the control identification in the preset format in the at least one decimal data according to the digit of each decimal data, wherein the digit of the control identification in the preset format is a preset digit number.
In another possible implementation manner, the preset format is a decimal data format, and correspondingly, obtaining the control identifier in the character string format corresponding to the control identifier in the preset format includes:
converting the control identification in the decimal data format into a control identification in a hexadecimal data format;
and acquiring the control identification in the character string format corresponding to the control identification in the hexadecimal data format in the resource file.
In another possible implementation, determining at least one line of exception code in the source code according to the control identifier in the character string format includes:
acquiring a storage path of a source code;
acquiring a source code file corresponding to the storage path;
sequentially comparing each line of source codes in the source code file with the control identification in the character string format;
and determining the code comprising the control identification in the character string format as the abnormal code.
In another possible implementation manner, after obtaining the file identifier where the exception code is located and the number of lines of the exception code in the corresponding file, the method further includes:
displaying a file identifier where the abnormal code is located and the line number of the abnormal code in a corresponding file in a preset display area of a visual interface;
or,
and storing the file identifier of the abnormal code and the line number of the abnormal code in the corresponding file in a preset file.
In a second aspect, an embodiment of the present invention provides an apparatus for locating an application failure, including an extracting module, a first obtaining module, a determining module, and a second obtaining module, where,
the extraction module is used for extracting control identification in a preset format from the abnormal log;
the first obtaining module is used for obtaining the control identification in the character string format corresponding to the control identification in the preset format;
the determining module is used for determining at least one row of abnormal codes in a source code according to the control identification in the character string format, wherein the abnormal codes comprise the control identification in the character string format;
the second obtaining module is used for obtaining the file identifier of the abnormal code and the line number of the abnormal code in the corresponding file.
In a possible embodiment, the preset format is a decimal data format; correspondingly, the extraction module is specifically configured to:
obtaining at least one decimal data in the exception log;
and determining the control identification in the preset format in the at least one decimal data according to the digit of each decimal data, wherein the digit of the control identification in the preset format is a preset digit number.
In another possible implementation, the preset format is a decimal data format, and accordingly, the first obtaining module is configured to:
converting the control identification in the decimal data format into a control identification in a hexadecimal data format;
and acquiring the control identification in the character string format corresponding to the control identification in the hexadecimal data format in the resource file.
In another possible implementation manner, the determining module is specifically configured to:
acquiring a storage path of a source code;
acquiring a source code file corresponding to the storage path;
sequentially comparing each line of source codes in the source code file with the control identification in the character string format;
and determining the code comprising the control identification in the character string format as the abnormal code.
In another possible embodiment, the apparatus further comprises a display module and a storage module, wherein,
the display module is used for displaying the file identification of the abnormal code and the line number of the abnormal code in the corresponding file in a preset display area of a visual interface after the second acquisition module acquires the file identification of the abnormal code and the line number of the abnormal code in the corresponding file;
or,
the storage module is configured to store the file identifier of the abnormal code and the line number of the abnormal code in the corresponding file in a preset file after the second obtaining module obtains the file identifier of the abnormal code and the line number of the abnormal code in the corresponding file.
According to the application program fault positioning method and device provided by the embodiment of the invention, after the abnormal log is obtained, the control identification in the preset format is extracted from the abnormal log, the control identification in the character string format corresponding to the control identification in the preset format is obtained, the abnormal code comprising the control identification in the character string format is obtained in the source code in a matching manner according to the control identification in the character string format, the abnormal code is a code which is likely to have a fault, and then the file identification where the abnormal code is located and the line number of a line of code in the corresponding file are obtained.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic view of an application scenario of a method for locating a failure of an application according to an embodiment of the present invention;
fig. 2 is a first flowchart illustrating a method for locating a failure of an application according to an embodiment of the present invention;
fig. 3 is a flowchart illustrating a second method for locating a failure of an application according to an embodiment of the present invention;
fig. 4 is a first schematic structural diagram of an application fault location apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a second application fault location apparatus according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. 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 invention.
Fig. 1 is a schematic application scenario diagram of an application program fault location method according to an embodiment of the present invention. Referring to fig. 1, the terminal apparatus 101 and the application server 102 are included. Optionally, the terminal device 101 may be a mobile phone, a computer, a television, or the like, and an application program is installed in the terminal device 101. The application server 102 is a server corresponding to an application installed in the terminal apparatus 101, and the application server 102 is configured to provide a service to the application installed in the terminal apparatus 101.
In the process of running the application program in the terminal device 101, when the application program is abnormal, the terminal device 101 reports an abnormal log generated by the application program to the application server 102. After receiving the abnormal log reported by the terminal device 101, the application server 102 may directly process the abnormal log to determine the abnormal code, or may cache the abnormal log first and process the abnormal log to determine the abnormal code when necessary.
The application server 102 includes a resource file and a source code library corresponding to the application program, the resource file includes control identifiers of all controls in the application program in hexadecimal format and control identifiers in character string format, the source code library includes a source code for implementing the application program, and the control identifiers related to the source code are the control identifiers in character string format. The application server 102 may obtain a control identifier in a character string format of a control that may have an abnormality according to the abnormality log and the resource file, and search the source code library for information of obtaining the abnormal code according to the control identifier in the character string format, for example, a file where the abnormal code is located, a line number of the abnormal code in a corresponding file, and the like. In the process, after the abnormal log is obtained, the abnormal log can be automatically analyzed, the information of the abnormal code is determined in the source code library, and the efficiency of fault location is improved.
The technical means shown in the present application will be described in detail below with reference to specific examples. It should be noted that the following specific embodiments may be combined with each other, and description of the same or similar contents is not repeated in different embodiments.
Fig. 2 is a first flowchart illustrating an application fault location method according to an embodiment of the present invention. Referring to fig. 2, the method may include:
s201, extracting control identification in a preset format from the abnormal log.
The execution main body of the embodiment of the invention is an application program fault positioning device (hereinafter referred to as a fault positioning device for short), and the fault positioning device can be realized by software, or the fault positioning device can be realized by the combination of software and hardware.
Optionally, the fault locating apparatus may execute the technical scheme shown in the embodiment of fig. 2 after obtaining the abnormal log, may also periodically execute the technical scheme shown in the embodiment of fig. 2, and may also execute the technical scheme shown in the embodiment of fig. 2 under the trigger of a user, which is not specifically limited in this embodiment of the present invention.
And after the fault positioning device obtains the abnormal log, extracting a control identification in a preset format from the abnormal log. The preset format is the same as the format of the control identifier included in the abnormal log. For example, when a control included in an application-generated exception log is identified as a decimal, the preset format is also a decimal. In an actual application process, the preset format may be determined according to a format of a control identifier included in an exception log generated by an application program.
When the preset format is a decimal data format, semantic analysis can be carried out on the abnormal log so as to obtain at least one piece of decimal data in the abnormal log, a control identifier in the preset format is determined in the at least one piece of decimal data according to the digit of each piece of decimal data, and the digit of the control identifier in the preset format is the preset digit. Optionally, when the application program applies the Android system, the preset number of bits may be 10 bits.
It should be noted that, in the actual application process, the control identifier in the preset format may also be manually obtained from the abnormal log, and the manually obtained control identifier in the preset format is input into the fault locating device, and accordingly, the fault locating device may display the control identifier input box through the visual interface, so that the user may input the control identifier in the preset format into the control identifier input box.
S202, acquiring a control identification in a character string format corresponding to the control identification in the preset format.
When the preset format is a decimal data format, the control identifier in the character string format corresponding to the control identifier in the preset format can be obtained through the following feasible implementation modes: and converting the control identification in the decimal data format into a control identification in a hexadecimal data format, and acquiring the control identification in the character string format corresponding to the control identification in the hexadecimal data format from the resource file.
Optionally, the resource file includes control identifiers in hexadecimal format of all the controls in the application program, and a control identifier in character string format corresponding to each control identifier in hexadecimal format. For an application program in the Android system, a resource file is generally an R class, for example, the R class may be as follows:
Public final class R{
Public static final int searcherHistoryListView＝0x7f8b078e；
Public static final int searcherHistoryTextView＝0x7f8b075e；
Public static final int searcherHistoryLayout＝0x7f8b048e；
……
}
please refer to the above code, the R class is a resource file, and in the resource file, "0 x7f8b078 e", "0 x7f8b075 e" and "0 x7f8b048 e" are control ids in hexadecimal format, "searchlistorylist view", "searchlistorytextview" and "searchloyout" are control ids in string format. And each control identification in the character format has a control identification in a hexadecimal format corresponding to the control identification in the character format.
After the control identification in the decimal format is converted into the control identification in the hexadecimal format, the control identification in the character string format corresponding to the control identification in the hexadecimal format is searched in the resource file.
S203, matching and obtaining at least one row of abnormal codes in the source codes according to the control identification in the character string format, wherein the abnormal codes comprise the control identification in the character string format.
Optionally, a storage path of the source code may be obtained first, and a source code file corresponding to the storage path is obtained, where the source code file includes multiple lines of codes for implementing the application program, each line of source codes in the source code file is sequentially compared with the control identifier in the character string format, and a code including the control identifier in the character string format is determined as an abnormal code.
Alternatively, the storage path of the source code may be preset. Of course, the storage path of the source code may also be manually input, and accordingly, the fault location device may display a storage path input box or a storage path selection box through the visual interface, so that the user may input the storage path of the source code through the storage path input box or the storage path selection box.
S204, acquiring the identification of the file where the abnormal code is located and the line number of the abnormal code in the corresponding file.
After the abnormal code is obtained, the file where the abnormal code is located and the line number of the abnormal code in the corresponding file are obtained.
Of course, in an actual application process, other information of the exception code may also be obtained, for example, a class name of a class where the exception code is located may be obtained, which is not specifically limited in the embodiment of the present invention.
After the file where the abnormal code is located and the line number of the abnormal code in the corresponding file are obtained, the file identifier where the abnormal code is located and the line number of the abnormal code in the corresponding file can be displayed in a preset display area of a visual interface, and the file identifier where the abnormal code is located and the line number of the abnormal code in the corresponding file can also be stored in a preset file.
According to the application program fault positioning method provided by the embodiment of the invention, after the abnormal log is obtained, the control identification in the preset format is extracted from the abnormal log, the control identification in the character string format corresponding to the control identification in the preset format is obtained, the abnormal code comprising the control identification in the character string format is obtained in the source code in a matching manner according to the control identification in the character string format, the abnormal code is a code which is likely to have a fault, then the file identification of the abnormal code and the line number of a line of codes in a corresponding file are obtained, manual participation is not needed in the processes, the user operation is simplified, and the fault positioning efficiency is improved.
On the basis of the embodiment shown in fig. 2, the embodiment shown in fig. 2 is further described in detail below by taking the preset format as the decimal format, and by the embodiment shown in fig. 3.
Fig. 3 is a schematic flowchart of a method for locating a failure of an application according to an embodiment of the present invention. On the basis of the embodiment shown in fig. 2, referring to fig. 3, the method may include:
s301, obtaining an abnormal log.
S302, at least one decimal data is obtained from the abnormal log.
S303, according to the digit of each decimal data, determining a control identification in a decimal format with the digit of 10 in at least one decimal data.
S304, converting the control identification in the decimal format with the digit number of 10 into the control identification in the hexadecimal data format.
S305, acquiring a control identification in a character string format corresponding to the control identification in the hexadecimal data format from the resource file.
S306, acquiring a storage path of the source code.
And S307, acquiring a source code file corresponding to the storage path.
S308, sequentially comparing the source code of each line in the source code file with the control identification in the character string format, and determining the code comprising the control identification in the character string format as an abnormal code.
S309, acquiring the identification of the file where the abnormal code is located and the line number of the abnormal code in the corresponding file.
S310, displaying the file identification where the abnormal code is located and the line number of the abnormal code in the corresponding file in a preset display area of the visual interface.
In the embodiment shown in fig. 3, after obtaining the abnormal log, firstly extracting the control identifier in the decimal format from the abnormal log, converting the control identifier in the decimal format into the control identifier in the hexadecimal format, then obtaining the control identifier in the character string format corresponding to the control identifier in the hexadecimal format, and matching and obtaining the abnormal code in the source code according to the control identifier in the character string format, where the abnormal code includes the control identifier in the character string format, and the abnormal code is a code that may have a fault, and then obtaining the file identifier where the abnormal code is located and the line number of the abnormal code in the corresponding file.
The technical solutions shown in the above method embodiments are described in detail below by specific examples.
For example, assume that the obtained exception log is as follows:
java.lang.IllegalStateException
The content of the adapter has changed but ListView did not receive anotification.Make sure the content of your adapter is not modified from abackground thread,but only from the UI thread.Make sure your adapter callsnotifyDataSetChanged()when its content changes.[in ListView(2139817870，classandroid.widget.ListView)with Adapter(classandroid.widget.HeaderViewListAdapter)]
after obtaining the abnormal log, analyzing the abnormal log to extract a control identifier in a decimal format from the abnormal log: 2139817870.
after getting the control identification 2139817870 in decimal format, 2139817870 is converted to 0x7f8b078e in hexadecimal.
Acquiring a control identifier in a character string format corresponding to a hexadecimal control identifier 0x7f8b078e in a resource file: searcher historyListView.
Acquiring a storage path of the source code: and determining a file under the storage path as a source code file, wherein the source code file comprises a plurality of codes for realizing an application program, comparing each row of source codes in the source code file with a searchlistorylistview, and determining a code comprising the searchlistorylistview as an exception code.
After the abnormal codes are determined, the file identification of each line of the abnormal codes and the line number of the abnormal codes in the corresponding file are obtained, and the file identification of the abnormal codes and the line number of the abnormal codes in the corresponding file are displayed in a preset display area of a visual interface.
Fig. 4 is a first schematic structural diagram of an application fault location apparatus according to an embodiment of the present invention. Referring to fig. 4, the apparatus may include an extracting module 11, a first obtaining module 12, a determining module 13, and a second obtaining module 14, wherein,
the extraction module 11 is configured to extract a control identifier in a preset format from the abnormal log;
the first obtaining module 12 is configured to obtain a control identifier in a character string format corresponding to the control identifier in the preset format;
the determining module 13 is configured to determine at least one row of abnormal codes in a source code according to the control identifier in the character string format, where the abnormal codes include the control identifier in the character string format;
the second obtaining module 14 is configured to obtain a file identifier of the exception code and a line number of the exception code in a corresponding file.
The application program fault locating device provided by the embodiment of the invention can execute the technical scheme shown in the method embodiment, the implementation principle and the beneficial effect are similar, and the detailed description is omitted here.
In a possible embodiment, the preset format is a decimal data format; correspondingly, the extraction module 11 is specifically configured to:
obtaining at least one decimal data in the exception log;
and determining the control identification in the preset format in the at least one decimal data according to the digit of each decimal data, wherein the digit of the control identification in the preset format is a preset digit number.
In another possible embodiment, the preset format is a decimal data format, and accordingly, the first obtaining module 12 is configured to:
converting the control identification in the decimal data format into a control identification in a hexadecimal data format;
and acquiring the control identification in the character string format corresponding to the control identification in the hexadecimal data format in the resource file.
In another possible implementation, the determining module 13 is specifically configured to:
acquiring a storage path of a source code;
acquiring a source code file corresponding to the storage path;
sequentially comparing each line of source codes in the source code file with the control identification in the character string format;
and determining the code comprising the control identification in the character string format as the abnormal code.
Fig. 5 is a schematic structural diagram of a second application fault location apparatus according to an embodiment of the present invention. On the basis of the embodiment shown in fig. 4, referring to fig. 5, the apparatus further comprises a display module 15 and a storage module 16, wherein,
the display module 15 is configured to, after the second obtaining module 14 obtains the file identifier of the abnormal code and the line number of the abnormal code in the corresponding file, display the file identifier of the abnormal code and the line number of the abnormal code in the corresponding file in a preset display area of a visual interface;
or,
the storage module 16 is configured to, after the second obtaining module 14 obtains the file identifier of the exception code and the line number of the exception code in the corresponding file, store the file identifier of the exception code and the line number of the exception code in the corresponding file in a preset file.
The application program fault locating device provided by the embodiment of the invention can execute the technical scheme shown in the method embodiment, the implementation principle and the beneficial effect are similar, and the detailed description is omitted here.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the embodiments of the present invention, and are not limited thereto; although embodiments of the present invention have been described in detail with reference to the foregoing embodiments, those skilled in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the embodiments of the present invention.
Claims (10)
1. An application program fault locating method is characterized by comprising the following steps:
extracting control identification in a preset format from the abnormal log;
acquiring a control identifier in a character string format corresponding to the control identifier in the preset format;
determining at least one row of abnormal codes in a source code according to the control identification in the character string format, wherein the abnormal codes comprise the control identification in the character string format;
and acquiring the file identifier of the abnormal code and the line number of the abnormal code in the corresponding file.
2. The method of claim 1, wherein the preset format is a decimal data format; correspondingly, extracting the control identification from the abnormal log comprises the following steps:
obtaining at least one decimal data in the exception log;
and determining the control identification in the preset format in the at least one decimal data according to the digit of each decimal data, wherein the digit of the control identification in the preset format is a preset digit number.
3. The method according to claim 1 or 2, wherein the preset format is a decimal data format, and accordingly, obtaining the control identifier in the character string format corresponding to the control identifier in the preset format comprises:
converting the control identification in the decimal data format into a control identification in a hexadecimal data format;
and acquiring the control identification in the character string format corresponding to the control identification in the hexadecimal data format in the resource file.
4. The method of claim 1 or 2, wherein determining at least one line of exception code in source code according to the control identification in the string format comprises:
acquiring a storage path of a source code;
acquiring a source code file corresponding to the storage path;
sequentially comparing each line of source codes in the source code file with the control identification in the character string format;
and determining the code comprising the control identification in the character string format as the abnormal code.
5. The method according to claim 1 or 2, wherein after obtaining the file identifier of the exception code and the number of rows of the exception code in the corresponding file, further comprising:
displaying a file identifier where the abnormal code is located and the line number of the abnormal code in a corresponding file in a preset display area of a visual interface;
or,
and storing the file identifier of the abnormal code and the line number of the abnormal code in the corresponding file in a preset file.
6. The application program fault positioning device is characterized by comprising an extraction module, a first acquisition module, a determination module and a second acquisition module, wherein,
the extraction module is used for extracting control identification in a preset format from the abnormal log;
the first obtaining module is used for obtaining the control identification in the character string format corresponding to the control identification in the preset format;
the determining module is used for determining at least one row of abnormal codes in a source code according to the control identification in the character string format, wherein the abnormal codes comprise the control identification in the character string format;
the second obtaining module is used for obtaining the file identifier of the abnormal code and the line number of the abnormal code in the corresponding file.
7. The apparatus of claim 6, wherein the predetermined format is a decimal data format; correspondingly, the extraction module is specifically configured to:
obtaining at least one decimal data in the exception log;
and determining the control identification in the preset format in the at least one decimal data according to the digit of each decimal data, wherein the digit of the control identification in the preset format is a preset digit number.
8. The apparatus according to claim 6 or 7, wherein the preset format is a decimal data format, and accordingly the first obtaining module is configured to:
converting the control identification in the decimal data format into a control identification in a hexadecimal data format;
and acquiring the control identification in the character string format corresponding to the control identification in the hexadecimal data format in the resource file.
9. The apparatus according to claim 6 or 7, wherein the determining module is specifically configured to:
acquiring a storage path of a source code;
acquiring a source code file corresponding to the storage path;
sequentially comparing each line of source codes in the source code file with the control identification in the character string format;
and determining the code comprising the control identification in the character string format as the abnormal code.
10. The apparatus of claim 6 or 7, further comprising a display module and a storage module, wherein,
the display module is used for displaying the file identification of the abnormal code and the line number of the abnormal code in the corresponding file in a preset display area of a visual interface after the second acquisition module acquires the file identification of the abnormal code and the line number of the abnormal code in the corresponding file;
or,
the storage module is configured to store the file identifier of the abnormal code and the line number of the abnormal code in the corresponding file in a preset file after the second obtaining module obtains the file identifier of the abnormal code and the line number of the abnormal code in the corresponding file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710517229.6A CN107463492A (en) | 2017-06-29 | 2017-06-29 | Application failure localization method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710517229.6A CN107463492A (en) | 2017-06-29 | 2017-06-29 | Application failure localization method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107463492A true CN107463492A (en) | 2017-12-12 |
Family
ID=60544090
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710517229.6A Pending CN107463492A (en) | 2017-06-29 | 2017-06-29 | Application failure localization method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107463492A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108304310A (en) * | 2018-02-28 | 2018-07-20 | 厦门美图移动科技有限公司 | A kind of log analysis method and computing device |
| CN111427738A (en) * | 2019-01-09 | 2020-07-17 | 阿里巴巴集团控股有限公司 | Display method, application monitoring module, bytecode enhancement module and display system |
| CN112162917A (en) * | 2020-09-03 | 2021-01-01 | 华为技术有限公司 | Defect positioning method and device of software system |
| CN114328273A (en) * | 2022-03-07 | 2022-04-12 | 统信软件技术有限公司 | Debugging method and device for application program control and computing equipment |
| CN117149476A (en) * | 2023-01-13 | 2023-12-01 | 荣耀终端有限公司 | Fault reporting method and related device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101770422A (en) * | 2008-12-30 | 2010-07-07 | 鸿富锦精密工业（深圳）有限公司 | Software bug tracking method and computer system thereof |
| US20140149435A1 (en) * | 2012-11-27 | 2014-05-29 | Purdue Research Foundation | Bug localization using version history |
| CN105159832A (en) * | 2015-09-29 | 2015-12-16 | 北京奇虎科技有限公司 | Method, apparatus and system for collecting application exception information in application test |
-
2017
- 2017-06-29 CN CN201710517229.6A patent/CN107463492A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101770422A (en) * | 2008-12-30 | 2010-07-07 | 鸿富锦精密工业（深圳）有限公司 | Software bug tracking method and computer system thereof |
| US20140149435A1 (en) * | 2012-11-27 | 2014-05-29 | Purdue Research Foundation | Bug localization using version history |
| CN105159832A (en) * | 2015-09-29 | 2015-12-16 | 北京奇虎科技有限公司 | Method, apparatus and system for collecting application exception information in application test |
Non-Patent Citations (1)
| Title |
|---|
| VIGIBORD: ""Android通过崩溃日志中控件id定位崩溃位置的方法"", 《HTTPS://BLOG.CSDN.NET/ZHAOSHUYU111/ARTICLE/DETAILS/55053130》 * |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108304310A (en) * | 2018-02-28 | 2018-07-20 | 厦门美图移动科技有限公司 | A kind of log analysis method and computing device |
| CN108304310B (en) * | 2018-02-28 | 2021-04-16 | 厦门美图移动科技有限公司 | Log analysis method and computing device |
| CN111427738A (en) * | 2019-01-09 | 2020-07-17 | 阿里巴巴集团控股有限公司 | Display method, application monitoring module, bytecode enhancement module and display system |
| CN111427738B (en) * | 2019-01-09 | 2024-04-05 | 阿里巴巴集团控股有限公司 | Display method, application monitoring module, byte code enhancement module and display system |
| CN112162917A (en) * | 2020-09-03 | 2021-01-01 | 华为技术有限公司 | Defect positioning method and device of software system |
| CN114328273A (en) * | 2022-03-07 | 2022-04-12 | 统信软件技术有限公司 | Debugging method and device for application program control and computing equipment |
| CN114328273B (en) * | 2022-03-07 | 2022-07-12 | 统信软件技术有限公司 | Debugging method and device for application program control and computing equipment |
| CN117149476A (en) * | 2023-01-13 | 2023-12-01 | 荣耀终端有限公司 | Fault reporting method and related device |
| CN117149476B (en) * | 2023-01-13 | 2024-08-27 | 荣耀终端有限公司 | Fault reporting method and related device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107463492A (en) | Application failure localization method and device | |
| US20100199263A1 (en) | Test case pattern matching | |
| CN107992415B (en) | Fault positioning and analyzing method of transaction system and related server | |
| US20140157239A1 (en) | System and method for peer-based code quality analysis reporting | |
| CN106201757B (en) | Exception handling method and device | |
| CN107633433B (en) | Advertisement auditing method and device | |
| CN106897197B (en) | Error log duplicate removal method and device | |
| CN109840192B (en) | Method and device for automatic testing | |
| CN107193747B (en) | Code testing method and device and computer equipment | |
| CN111625471B (en) | Method, device, equipment and medium for executing and processing test cases and locating abnormality | |
| JP6440895B2 (en) | Software analysis apparatus and software analysis method | |
| CN113868126A (en) | Application debugging method, device and storage medium of equipment | |
| CN111324510B (en) | Log processing method and device and electronic equipment | |
| CN110688173B (en) | Positioning method and device of components in cross-platform interface framework and electronic equipment | |
| CN110795332A (en) | Automatic testing method and device | |
| CN107908525B (en) | Alarm processing method, equipment and readable storage medium | |
| CN106294132B (en) | A kind of method and device managing log | |
| CN112181695A (en) | Abnormal application processing method, device, server and storage medium | |
| CN109146096B (en) | Processing method and device for repair event, storage medium and electronic equipment | |
| CN108763053B (en) | Method for generating buried point name and terminal equipment | |
| CN110674491B (en) | Method and device for real-time evidence obtaining of android application and electronic equipment | |
| CN113656210A (en) | Processing method and device for error reporting information, server and readable storage medium | |
| CN113781068A (en) | Online problem solving method and device, electronic equipment and storage medium | |
| CN112685427B (en) | Data access method, device, electronic equipment and storage medium | |
| CN115543227B (en) | Cross-system data migration method, system, electronic device and storage medium |
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: 20171212 |
|
| RJ01 | Rejection of invention patent application after publication |