CN111090593A - Method, device, electronic equipment and storage medium for determining crash attribution - Google Patents
Method, device, electronic equipment and storage medium for determining crash attribution Download PDFInfo
- Publication number
- CN111090593A CN111090593A CN202010218782.1A CN202010218782A CN111090593A CN 111090593 A CN111090593 A CN 111090593A CN 202010218782 A CN202010218782 A CN 202010218782A CN 111090593 A CN111090593 A CN 111090593A
- Authority
- CN
- China
- Prior art keywords
- crash
- sdk
- address
- information
- attribution
- 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
Images
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
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 invention discloses a method for determining crash attribution, which relates to the technical field of computers and comprises the following steps: acquiring collapse information; analyzing the collapse information to obtain a calling address; obtaining an SDK compiling file, and calculating to obtain an SDK operation address interval based on the SDK compiling file; and judging whether the calling address is in the SDK operation address interval or not, if so, storing the crash information, and uploading the crash information to a remote server. According to the method, whether the calling address corresponding to the crash information falls in the SDK operation address interval or not is analyzed and judged, the SDK where the crash exists can be determined quickly and accurately, the troubleshooting time and workload of the SDK crash are reduced, the efficiency of analyzing the SDK crash is improved, and the development cost is reduced; reporting the SDK crash in time is beneficial to accelerating the speed of processing the crash by an SDK developer, and then optimizing and improving the SDK in time, thereby improving the stability of the SDK. The invention also discloses a device for determining the crash attribution, electronic equipment and a computer storage medium.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method and an apparatus for determining crash attribution, an electronic device, and a storage medium.
Background
With the heat tide of the development of the mobile platform SDK, the online breakdown caused by the SDK in the application program is always a hot topic to be discovered in time. in the iOS operating system, SDK is divided into two types, static library and dynamic library (Embedded Framework). Therefore, when the method crashes in the calling SDK, the name of the dynamic library SDK is displayed in the information of the crash stack, and whether the method crashes caused by the current SDK can be determined by comparing the SDK names.
The code of the static library and the code of the application program belong to the same binary module, and the code of the static library and the code of the application program are added into the code segment of the application program. When the application crashes and the method in the SDK is called to crash, the name displayed in the crash stack is the executable file name of the application program, which is the same as the crash caused by the code in the application program, so that the SDK developer cannot distinguish, and the SDK developer cannot optimize and improve the SDK.
At present, the crash caused by the application program is collected by fully capturing the crash of the static library, and relevant information is screened and analyzed, so that the SDK where the crash is located is determined.
Disclosure of Invention
In order to overcome the defects of the prior art, an object of the present invention is to provide a method for determining crash attribution, which compares a call address obtained by analyzing crash information with an SDK operation address interval to determine, quickly locates an SDK where the crash is located, and reports the crash information in time, so that an SDK developer performs optimization and improvement.
One of the purposes of the invention is realized by adopting the following technical scheme:
acquiring collapse information;
analyzing the collapse information to obtain a calling address;
obtaining an SDK compiling file, and calculating to obtain an SDK running address interval based on the SDK compiling file;
and judging whether the calling address is in the SDK operation address interval or not, if so, storing the crash information, and uploading the crash information to a remote server.
Further, obtaining crash information includes: and capturing abnormal information and equipment information by registering a crash capture function, and recording a crash call stack.
Further, the crash information includes a crash stack, a crash occurrence time, a device version, a device model, a CPU architecture, a network state, a crash type, and a crash reason.
Further, calculating an SDK operation address interval based on the SDK compiled file, including:
analyzing the SDK compiling file to obtain the address offset of the starting function of the SDK running address interval;
acquiring a starting address and an ending address of the SDK operation address interval;
and obtaining the SDK operation address interval according to the starting address, the address offset and the ending address.
Further, parsing the SDK compiled file includes: and analyzing the SDK compiled file through disassembling software to obtain the address offset of the starting function of the SDK running address interval under different architectures.
Further, the step of obtaining the start address and the end address of the SDK operation address interval, where the SDK compiled file includes a first compiled file and a last compiled file, includes:
calling an address obtaining function in the first compiled file to obtain the initial address;
and calling an address acquisition function in the last compiled file to obtain the end address.
Further, saving the crash information and uploading the crash information to a remote server comprises:
saving the crash information to crash the application program;
and re-running the application program, judging whether the crash information exists, and if so, uploading the crash information to a remote server.
The second objective of the present invention is to provide a device for determining crash attribution, which compares and determines the calling address obtained by analyzing the crash information with the SDK operation address interval, rapidly locates the SDK where the crash is located, and reports the crash information in time, so that the SDK developer can perform optimization and improvement.
The second purpose of the invention is realized by adopting the following technical scheme:
a device that determines a crash homing, comprising:
the crash obtaining module is used for obtaining crash information;
the crash analysis module is used for analyzing the crash information to obtain a calling address;
the address interval calculation module is used for acquiring an SDK compiled file and calculating to obtain an SDK operation address interval based on the SDK compiled file;
and the crash judgment processing module is used for judging whether the calling address is in the SDK operation address interval or not, if so, storing the crash information, and uploading the crash information to a remote server.
It is a further object of the invention to provide an electronic device comprising a processor, a storage medium and a computer program, the computer program being stored in the storage medium, the computer program, when being executed by the processor, being a method of determining a crash attribution of one of the objects of the invention.
It is a further object of the present invention to provide a computer readable storage medium storing one of the objects of the invention, having a computer program stored thereon, which, when executed by a processor, implements the method of determining crash attribution of one of the objects of the invention.
Compared with the prior art, the invention has the beneficial effects that:
according to the method and the device, whether the calling address corresponding to the crash information falls in the SDK operation address interval or not is judged, the SDK where the crash exists can be determined rapidly and accurately, the troubleshooting time and workload of the SDK crash are reduced, the efficiency of analyzing the SDK crash is improved, and the development cost is reduced; reporting the SDK crash in time is beneficial to accelerating the speed of processing the crash by an SDK developer, and then optimizing and improving the SDK in time, thereby improving the stability of the SDK.
Drawings
FIG. 1 is a flowchart illustrating a method for determining crash attribution according to a first embodiment of the present invention;
FIG. 2 is a block diagram of an apparatus for determining crash attribution according to a second embodiment of the present invention;
fig. 3 is a block diagram of an electronic device according to a third embodiment of the present invention.
Detailed Description
The present invention will now be described in more detail with reference to the accompanying drawings, in which the description of the invention is given by way of illustration and not of limitation. The various embodiments may be combined with each other to form other embodiments not shown in the following description.
Example one
The embodiment provides a method for determining crash attribution, which aims to compare and judge a calling address obtained by analyzing crash information with an SDK (software development kit) running address interval, quickly locate an SDK where the crash exists and report the crash information in time. According to the method, whether the calling address corresponding to the crash information falls in the SDK operation address interval or not is analyzed and judged, the SDK where the crash exists can be determined quickly and accurately, the troubleshooting time and workload of the SDK crash are reduced, the efficiency of analyzing the SDK crash is improved, and the development cost is reduced; reporting the SDK crash in time is beneficial to accelerating the speed of processing the crash by an SDK developer, and then optimizing and improving the SDK in time, thereby improving the stability of the SDK.
Referring to fig. 1, a method for determining crash attribution includes the following steps:
and S110, acquiring the crash information.
By registering a crash capture function or a crash monitoring function, when an application program crashes, abnormal information and equipment information are captured, and a crash call stack is recorded so as to collect crash information in the application program. The acquired crash information includes, but is not limited to, a crash stack, crash occurrence time, device version, device model, CPU architecture, network state, crash type, and crash reason, and can completely restore the relevant information of the device call stack when the crash occurs.
And S120, analyzing the collapse information to obtain a calling address.
And analyzing the acquired collapse information by an analysis tool or calling a corresponding analysis function, and screening out a calling address corresponding to the binary file name of the application program.
S130, obtaining the SDK compiling file, and calculating to obtain the SDK operation address interval based on the SDK compiling file.
The SDK operation address interval refers to the final operation address interval of the SDK. A static library of an iOS operating system may be simply understood as a packed aggregate of a stack of object files (i.e., ". o files"). The application runs two very important processes including compilation and linking. When a class in the SDK is compiled, the file is compiled into an o file of the corresponding class. The o files are linked into the application executable in compile-time order, and the addresses assigned during run-time for all declaration functions within an SDK are contiguous. Therefore, the SDK operation address interval can be obtained through calculation according to the SDK compiling file, and whether the crash is caused by the SDK or not can be quickly judged.
And compiling the file according to the SDK to obtain the starting address and the ending address of the address interval in the operation of the SDK. The SDK compiled file includes a first compiled file and a last compiled file. Only one function for acquiring the self address is reserved in the first compiling file of the SDK, and the function for acquiring the self address is called to obtain the initial address of the SDK operation address interval. And only one function for acquiring the self address is reserved in the last compiled file of the SDK, and the function for acquiring the self address is called to obtain the end address of the SDK operation address interval. The two functions in the first compiled file and the last compiled file, which acquire the self addresses, have different names and the same functions and are used for acquiring the address of the current function.
And analyzing the SDK compiled file through disassembling software to obtain the address offset of the initial function in the address interval in the SDK operation under different architectures. The disassembling software includes but is not limited to IDA, Hopper. In this embodiment, the SDK packet is analyzed by IDA.
According to the starting address, the address offset and the ending address, the SDK operation address interval obtained by calculation is as follows: the initial address + address offset and the end address are used for judging whether the crash information falls in the SDK operation address interval or not, so that the crash attribution is accurately judged.
S140, judging whether the calling address is in the SDK operation address interval, if so, storing the crash information, and uploading the crash information to a remote server.
And comparing the calling address corresponding to the crash information with the SDK operation address interval, and judging whether the calling address falls in the SDK operation address interval according to the comparison result, so that the SDK where the crash exists can be quickly and accurately determined, the troubleshooting time and workload of the SDK crash are reduced, the efficiency of analyzing the SDK crash is improved, and the development cost is reduced.
Preferably, the comparison result is returned through the Boolean value, and when the Boolean value is true, the calling address is judged to be in the SDK operation address interval; and when the Boolean value is false, judging that the calling address is not in the SDK operation address interval.
And determining whether to store the crash information to the local according to the judgment result of whether the calling address is in the SDK operation address interval. When the calling address is judged to be in the SDK operation address interval, calling a corresponding processing function, storing the collapse information to a local storage position, and enabling the application program to collapse; and when the calling address is judged not to be in the SDK operation address interval, the collapse information is not processed, and the application program is collapsed.
And the application program is reopened to run, and whether the crash information is uploaded to the remote server is determined by checking whether the crash information exists in the local storage position. If the storage position is judged to have the crash information, calling a corresponding uploading function, and uploading the crash information to a remote server; if the storage position does not have the crash information, no processing is carried out. The timely reporting of the SDK crash is beneficial to accelerating the speed of the SDK developer for processing the crash, and then the SDK is optimized and improved in time, so that the stability of the SDK is improved.
Example two
An embodiment two discloses a device for determining crash attribution corresponding to the above embodiment, which is a virtual device structure of the above embodiment, as shown in fig. 2, and includes:
a crash acquisition module 210, configured to acquire crash information;
a crash analysis module 220, configured to analyze the crash information to obtain a call address;
an address interval calculation module 230, configured to obtain an SDK compiled file, and calculate an SDK operation address interval based on the SDK compiled file;
and the crash judgment processing module 240 is configured to judge whether the call address is within the SDK operation address interval, and if so, save the crash information and upload the crash information to a remote server.
The crash obtaining module 210 captures the abnormal information and the device information by registering a crash capture function, and records a crash call stack to obtain crash information, where the crash information includes, but is not limited to, a crash stack, a crash occurrence time, a device version, a device model, a CPU architecture, a network state, a crash type, and a crash reason.
The address interval calculation module 230 obtains a function according to the self address in the compiled files of the first compiled file and the last compiled file of the SDK, respectively, to obtain a start address and an end address of the SDK operation address interval; analyzing the SDK compiling file through disassembling software to obtain address offset of an initial function of an SDK running address interval under different architectures; and calculating to obtain the SDK operation address interval according to the starting address, the address offset and the ending address.
When the crash determination processing module 240 determines that the call address obtained in the crash analysis module 220 is within the SDK operation address interval obtained in the address interval calculation module 230, it saves the crash information to the local storage location, and makes the application program crash; and re-opening the application program to run, and uploading the crash information to the remote server when the crash information exists in the local storage position.
Whether the calling address corresponding to the crash information falls in the SDK operation address interval is judged through analysis, the SDK where the crash exists is quickly and accurately determined, the troubleshooting time and workload of the SDK crash are reduced, the efficiency of analyzing the SDK crash is improved, and the development cost is reduced; reporting the SDK crash in time is beneficial to accelerating the speed of processing the crash by an SDK developer, and then optimizing and improving the SDK in time, thereby improving the stability of the SDK.
EXAMPLE III
Fig. 3 is a schematic structural diagram of an electronic device according to a third embodiment of the present invention, as shown in fig. 3, the electronic device includes a processor 310, a memory 320, an input device 330, and an output device 340; the number of the processors 310 in the computer device may be one or more, and one processor 310 is taken as an example in fig. 3; the processor 310, the memory 320, the input device 330 and the output device 340 in the electronic apparatus may be connected by a bus or other means, and the connection by the bus is exemplified in fig. 3.
The memory 320 is a computer-readable storage medium, and can be used to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to the method for determining crash attribution in the embodiment of the present invention (for example, the crash obtaining module 210, the crash analyzing module 220, the address space calculating module 230, and the crash determining processing module 240 in the device for determining crash attribution). The processor 310 executes various functional applications and data processing of the electronic device by executing the software programs, instructions and modules stored in the memory 320, that is, the method for determining crash attribution in the first embodiment is implemented.
The memory 320 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 for at least one function; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 320 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 non-volatile solid state storage device. In some examples, the memory 320 may further include memory located remotely from the processor 310, which may be connected to the electronic device through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input device 330 may be used to receive crash information, an SDK compiled file, and the like. The output device 340 may include a display device such as a display screen.
Example four
A fourth embodiment of the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, perform a method for determining crash attribution, the method comprising:
acquiring collapse information;
analyzing the collapse information to obtain a calling address;
obtaining an SDK compiling file, and calculating to obtain an SDK running address interval based on the SDK compiling file;
and judging whether the calling address is in the SDK operation address interval or not, if so, storing the crash information, and uploading the crash information to a remote server.
Of course, the storage medium provided by the embodiment of the present invention contains computer-executable instructions, and the computer-executable instructions are not limited to the method operations described above, and may also perform related operations in the method for determining the crash attribution provided by any embodiment of the present invention.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes instructions for enabling an electronic device (which may be a mobile phone, a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It should be noted that, in the embodiment of the apparatus for determining a crash attribution, each unit and each module included in the embodiment are only divided according to functional logic, but are not limited to the above division, as long as the corresponding function can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
Various other modifications and changes may be made by those skilled in the art based on the above-described technical solutions and concepts, and all such modifications and changes should fall within the scope of the claims of the present invention.
Claims (10)
1. A method of determining crash attribution, characterized by: the method comprises the following steps:
acquiring collapse information;
analyzing the collapse information to obtain a calling address;
obtaining an SDK compiling file, and calculating to obtain an SDK running address interval based on the SDK compiling file;
and judging whether the calling address is in the SDK operation address interval or not, if so, storing the crash information, and uploading the crash information to a remote server.
2. A method of determining crash attribution as recited in claim 1, wherein: obtaining crash information, comprising: and capturing abnormal information and equipment information by registering a crash capture function, and recording a crash call stack.
3. A method of determining crash attribution as recited in claim 2, wherein: the crash information comprises a crash stack, crash occurrence time, equipment version, equipment model, CPU architecture, network state, crash type and crash reason.
4. A method of determining crash attribution as recited in claim 1, wherein: calculating to obtain an SDK operation address interval based on the SDK compiled file, wherein the step comprises the following steps:
analyzing the SDK compiling file to obtain the address offset of the starting function of the SDK running address interval;
acquiring a starting address and an ending address of the SDK operation address interval;
and obtaining the SDK operation address interval according to the starting address, the address offset and the ending address.
5. A method of determining crash attribution, as recited in claim 4, wherein: analyzing the SDK compiled file, including: and analyzing the SDK compiled file through disassembling software to obtain the address offset of the starting function of the SDK running address interval under different architectures.
6. A method of determining crash attribution, as recited in claim 4, wherein: the step of obtaining the starting address and the ending address of the SDK operation address interval, wherein the SDK compilation file comprises a first compilation file and a last compilation file, and comprises the following steps:
calling an address obtaining function in the first compiled file to obtain the initial address;
and calling an address acquisition function in the last compiled file to obtain the end address.
7. A method of determining crash attribution as claimed in any one of claims 1 to 6, wherein: saving the crash information and uploading the crash information to a remote server, comprising:
saving the crash information to crash the application program;
and re-running the application program, judging whether the crash information exists, and if so, uploading the crash information to a remote server.
8. An apparatus that determines a crash homing, comprising:
the crash obtaining module is used for obtaining crash information;
the crash analysis module is used for analyzing the crash information to obtain a calling address;
the address interval calculation module is used for acquiring an SDK compiled file and calculating to obtain an SDK operation address interval based on the SDK compiled file;
and the crash judgment processing module is used for judging whether the calling address is in the SDK operation address interval or not, if so, storing the crash information, and uploading the crash information to a remote server.
9. An electronic device comprising a processor, a storage medium, and a computer program, the computer program being stored in the storage medium, wherein the computer program, when executed by the processor, performs the method of determining crash attribution of any one of claims 1 to 7.
10. A computer storage medium having a computer program stored thereon, characterized in that: the computer program when executed by a processor implements the method of determining crash attribution of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010218782.1A CN111090593A (en) | 2020-03-25 | 2020-03-25 | Method, device, electronic equipment and storage medium for determining crash attribution |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010218782.1A CN111090593A (en) | 2020-03-25 | 2020-03-25 | Method, device, electronic equipment and storage medium for determining crash attribution |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111090593A true CN111090593A (en) | 2020-05-01 |
Family
ID=70400625
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010218782.1A Pending CN111090593A (en) | 2020-03-25 | 2020-03-25 | Method, device, electronic equipment and storage medium for determining crash attribution |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111090593A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111782504A (en) * | 2020-05-20 | 2020-10-16 | 车智互联（北京）科技有限公司 | Application program abnormity diagnosis method, mobile terminal and readable storage medium |
| CN113806233A (en) * | 2021-10-11 | 2021-12-17 | 成都觅瑞科技有限公司 | Method and device for acquiring program crash information, electronic equipment and storage medium |
| CN114020505A (en) * | 2021-10-19 | 2022-02-08 | 北京五八信息技术有限公司 | Data processing method and device, electronic equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104503918A (en) * | 2015-01-12 | 2015-04-08 | 北京国双科技有限公司 | Handling method and device for abnormal information |
| CN107861865A (en) * | 2017-08-29 | 2018-03-30 | 平安普惠企业管理有限公司 | SDK localization methods, equipment and computer-readable recording medium |
-
2020
- 2020-03-25 CN CN202010218782.1A patent/CN111090593A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104503918A (en) * | 2015-01-12 | 2015-04-08 | 北京国双科技有限公司 | Handling method and device for abnormal information |
| CN107861865A (en) * | 2017-08-29 | 2018-03-30 | 平安普惠企业管理有限公司 | SDK localization methods, equipment and computer-readable recording medium |
Non-Patent Citations (1)
| Title |
|---|
| 米米狗: "iOS如何区分App和SDK内部crash", 《HTTP://WWW.COCOACHINA.COM/CMS/WAP.PHP?ACTION=ARTICLE&ID=26804》 * |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111782504A (en) * | 2020-05-20 | 2020-10-16 | 车智互联（北京）科技有限公司 | Application program abnormity diagnosis method, mobile terminal and readable storage medium |
| CN111782504B (en) * | 2020-05-20 | 2023-12-01 | 车智互联（北京）科技有限公司 | Application program abnormality diagnosis method, mobile terminal and readable storage medium |
| CN113806233A (en) * | 2021-10-11 | 2021-12-17 | 成都觅瑞科技有限公司 | Method and device for acquiring program crash information, electronic equipment and storage medium |
| CN114020505A (en) * | 2021-10-19 | 2022-02-08 | 北京五八信息技术有限公司 | Data processing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107193750B (en) | Script recording method and device | |
| CN111090593A (en) | Method, device, electronic equipment and storage medium for determining crash attribution | |
| CN105426310B (en) | A kind of method and apparatus for the performance for detecting target process | |
| CN108491321B (en) | Method and device for determining test case range and storage medium | |
| CN105607986A (en) | Acquisition method and device of user behavior log data | |
| CN110554962A (en) | Regression testing process covering method, server and computer readable storage medium | |
| CN110688358B (en) | Log collection method, device and equipment and readable storage medium | |
| CN112149136A (en) | loT device firmware vulnerability detection method and system and electronic device | |
| CN108446224B (en) | Performance analysis method of application program on mobile terminal and storage medium | |
| CN110941632A (en) | Database auditing method, device and equipment | |
| CN115686961A (en) | Processor testing method and device and electronic equipment | |
| CN113110965A (en) | Abnormal information monitoring method and device, computer storage medium and terminal | |
| CN110311806B (en) | Mobile application program interface response delay diagnosis method, system and terminal | |
| CN111597111A (en) | Application program starting speed monitoring method and device | |
| CN103514086A (en) | Extraction method and device for software error report | |
| CN115878358A (en) | Abnormal log analysis method and device, electronic equipment and storage medium | |
| CN109684220A (en) | A kind of browser compatibility analysis method based on event replay | |
| CN115309661A (en) | Application testing method and device, electronic equipment and readable storage medium | |
| CN107102938B (en) | Test script updating method and device | |
| CN114422186A (en) | Attack detection method and device, electronic equipment and storage medium | |
| CN112860469A (en) | Method, device, equipment and storage medium for collecting information of katon log | |
| CN114281596A (en) | Method and device for repairing abnormal data, electronic equipment and storage medium | |
| CN112000543A (en) | Method, device and equipment for detecting time delay performance of storage system | |
| CN111212029A (en) | Sensitive data monitoring and tracking method | |
| CN114741325B (en) | Recording method and device of test script for application system test |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200501 |