CN106294175A - A kind of program performs behavior method for visualizing and system - Google Patents
A kind of program performs behavior method for visualizing and system Download PDFInfo
- Publication number
- CN106294175A CN106294175A CN201610694677.9A CN201610694677A CN106294175A CN 106294175 A CN106294175 A CN 106294175A CN 201610694677 A CN201610694677 A CN 201610694677A CN 106294175 A CN106294175 A CN 106294175A
- Authority
- CN
- China
- Prior art keywords
- program
- execution
- event
- 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
- 238000000034 method Methods 0.000 title claims abstract description 72
- 238000012544 monitoring process Methods 0.000 claims abstract description 38
- 238000012800 visualization Methods 0.000 claims abstract description 9
- 238000004458 analytical method Methods 0.000 claims abstract description 4
- 230000006399 behavior Effects 0.000 claims description 22
- 238000007794 visualization technique Methods 0.000 claims description 8
- 230000006870 function Effects 0.000 claims description 5
- 230000003247 decreasing effect Effects 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 1
- 230000008520 organization Effects 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/3636—Software debugging by tracing the execution of the program
-
- 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/3644—Software debugging by instrumenting at runtime
-
- 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
This application discloses a kind of program and perform behavior method for visualizing, including: utilize program debugger, the execution process of program source code is monitored；If monitoring program source code the execution event corresponding with presetting monitoring objective occurs in the process of implementation, then on program source code, indicate the code line corresponding with execution event；If execution event is failure classes event, then stack trace information is resolved, obtain corresponding failure cause, then on the screen of local terminal, stack frame, stack trace information and failure cause are shown.The application can allow software developer know the reason causing failure classes event intuitively, and takes the mode of manual analysis source code to know failure cause without software developer.Visible, that the application is required during decreasing the debugging of program source code manpower.It addition, the application further correspondingly discloses a kind of program performs behavior visualization system.
Description
Technical Field
The invention relates to the technical field of program code supervision, in particular to a method and a system for visualizing program execution behaviors.
Background
Currently, with the rapid development of computer technology, people can enjoy convenient services brought by more and more application software, and people's clothes and people can not leave services provided by various application software more and more.
When developing application software, software developers need to frequently debug the execution process of corresponding program source codes, and enterprises can put corresponding application software into the market only on the basis of ensuring that the program source codes have enough reliability.
However, when debugging the execution process of the program source code, if a fault event occurs, a software developer cannot intuitively know the reason of the fault event, and the software developer needs to manually analyze the relevant code lines to determine the corresponding fault type. For applications with many hundreds of thousands of lines of code, the debugging process described above is undoubtedly labor intensive.
From the above, it can be seen that how to reduce the manpower required in the debugging process of the program source code is a problem to be solved at present.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a method and a system for visualizing a program execution behavior, which reduce manpower required in a debugging process of a program source code. The specific scheme is as follows:
a method of program execution behavior visualization, comprising:
monitoring the execution process of the program source code by using a program debugger;
if the execution event corresponding to a preset monitoring target occurs in the execution process of the program source code, pausing the execution process of the program source code, and marking a code line corresponding to the execution event on the program source code; the preset monitoring target is a monitoring target preset on the program debugger;
if the execution event is a fault event, acquiring a stack frame and stack trace information corresponding to the execution event by using the program debugger, analyzing the stack trace information to obtain a corresponding fault reason, and displaying the stack frame, the stack trace information and the fault reason on a local terminal screen.
Preferably, the program debugger is a GDB debugger.
Preferably, the preset monitoring target is a stack overflow event, a program interrupt event or a memory access error event.
Preferably, the program interruption event is an interruption event caused by a line breakpoint, a function breakpoint, a condition breakpoint or an event breakpoint.
Preferably, after the process of analyzing the stack trace information to obtain the corresponding failure cause, the method further includes:
determining the fault severity level corresponding to the execution event according to the fault reason;
and if the fault severity level is greater than a preset level, sending the stack frame, the stack tracking information and the fault reason to a pre-specified target equipment terminal.
Preferably, the step of sending the stack frame, the stack trace information, and the failure cause to a pre-specified target device terminal includes:
capturing a screen of a display area on the local terminal screen, wherein the display area displays the stack frame, the stack tracking information and the fault reason to obtain corresponding screen capturing picture information;
and sending the screen capture picture information to the target equipment terminal.
Preferably, the method further comprises:
and acquiring information fed back by the target equipment terminal after receiving the stack frame, the stack tracking information and the fault reason, and displaying the fed back information on a local terminal screen in real time.
The invention also discloses a program execution behavior visualization system, which comprises:
the execution process monitoring module is used for monitoring the execution process of the program source code by using the program debugger;
the execution process pausing module is used for pausing the execution process of the program source code when monitoring that an execution event corresponding to a preset monitoring target occurs in the execution process of the program source code; the preset monitoring target is a monitoring target preset on the program debugger;
the code marking module is used for marking a code line corresponding to the execution event on the program source code;
the information acquisition module is used for acquiring a stack frame and stack tracking information corresponding to the execution event by using the program debugger when the execution event is a fault event;
the information analysis module is used for analyzing the stack tracking information to obtain a corresponding fault reason;
and the information display module is used for displaying the stack frame, the stack tracking information and the fault reason on a local terminal screen.
Preferably, the system further comprises:
the fault severity level determining module is used for determining the fault severity level corresponding to the execution event according to the fault reason after the information analyzing module obtains the fault reason;
and the information sending module is used for sending the stack frame, the stack tracking information and the fault reason to a pre-specified target equipment terminal when the fault severity level is greater than a preset level.
Preferably, the information sending module includes:
the screen capture unit is used for capturing a screen of a display area for displaying the stack frame, the stack tracking information and the fault reason on the local terminal screen to obtain corresponding screen capture picture information;
and the information sending unit is used for sending the screen capture picture information to the target equipment terminal.
In the invention, the program execution behavior visualization method comprises the following steps: monitoring the execution process of the program source code by using a program debugger; if the execution event corresponding to the preset monitoring target occurs in the execution process of the program source code, pausing the execution process of the program source code, and marking a code line corresponding to the execution event on the program source code; the preset monitoring target is a monitoring target preset on a program debugger; if the execution event is a fault event, acquiring a stack frame and stack trace information corresponding to the execution event by using a program debugger, analyzing the stack trace information to obtain a corresponding fault reason, and displaying the stack frame, the stack trace information and the fault reason on a local terminal screen. Therefore, in the invention, when a specific execution event occurs in the execution process of the program source code, the code line corresponding to the execution event is identified, and when the specific execution event is a fault event, the stack trace information is analyzed to obtain a corresponding fault reason, and finally, the stack frame, the stack trace information and the fault reason corresponding to the fault event are displayed on the local terminal screen, so that a software developer can intuitively know the reason causing the fault event without manually analyzing the source code to obtain the fault reason. Therefore, the method and the device reduce the manpower required in the debugging process of the program source code.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for visualizing a program execution behavior according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a program execution behavior visualization system according to an embodiment of the present invention.
Detailed Description
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 only a part of the embodiments of the present invention, 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 invention.
The embodiment of the invention discloses a program execution behavior visualization method, which is shown in a figure 1 and comprises the following steps:
step S11: and monitoring the execution process of the program source code by using a program debugger.
It is understood that the program debugger in this embodiment may be a program debugger existing in the prior art, for example, the program debugger in this embodiment may employ a GDB debugger issued by a GUN open source organization. Of course, the program debugger in this embodiment may also be a newly developed program debugger.
In addition, in this embodiment, the execution process of the program source code refers to an operation process of the program source code when debugging the program source code.
Step S12: if the execution event corresponding to the preset monitoring target occurs in the execution process of the program source code, pausing the execution process of the program source code, and marking a code line corresponding to the execution event on the program source code; the preset monitoring target is a monitoring target preset on a program debugger.
It is understood that the preset monitoring target may be a fault event, and of course, may also be a non-fault event that is artificially and purposely required to be concerned.
Step S13: if the execution event is a fault event, acquiring a stack frame and stack trace information corresponding to the execution event by using a program debugger, analyzing the stack trace information to obtain a corresponding fault reason, and displaying the stack frame, the stack trace information and the fault reason on a local terminal screen.
In this embodiment, when the execution event corresponding to the preset monitoring target is a fault event, a program debugger is used to obtain a corresponding stack frame and stack trace information, and then the stack trace information is analyzed to obtain a corresponding fault reason.
It can be seen that, in the embodiment of the present invention, when it is monitored that a specific execution event occurs in an execution process of a program source code, a code line corresponding to the execution event is identified, and when the specific execution event is a fault event, stack trace information is analyzed to obtain a corresponding fault cause, and finally, a stack frame, stack trace information, and a fault cause corresponding to the fault event are displayed on a local terminal screen, so that a software developer can intuitively know a cause of the fault event, and the software developer does not need to manually analyze the source code to obtain the fault cause. Therefore, the embodiment of the invention reduces the manpower required in the debugging process of the program source code.
The embodiment of the invention discloses a specific program execution behavior visualization method, and compared with the previous embodiment, the embodiment further explains and optimizes the technical scheme. Specifically, the method comprises the following steps:
the preset monitoring target in the previous embodiment may specifically be a stack overflow event, a program interrupt event, or a memory access error event.
The program interruption event is an interruption event caused by a line breakpoint, a function breakpoint, a condition breakpoint or an event breakpoint. It should be understood that the line breakpoint refers to a breakpoint that suspends the execution of the program when the program source code is executed to a specified line, the function breakpoint refers to a breakpoint that suspends the execution of the program when the program source code is executed to the first line code corresponding to the specified function, the condition breakpoint refers to a breakpoint that suspends the execution of the program if a specific condition is true during the execution of the program source code, and the time breakpoint refers to a breakpoint that suspends the execution of the code if a specific event occurs during the execution of the program source code.
In step S13 of the previous embodiment, when the execution event corresponding to the preset monitoring target is a fault event, the stack trace information is analyzed to obtain a corresponding fault reason. After the process of analyzing the stack trace information to obtain the corresponding fault reason, the method further includes:
and determining a fault severity level corresponding to the execution event according to the fault reason, and if the fault severity level is greater than a preset level, sending the stack frame, the stack tracking information and the fault reason to a pre-specified target equipment terminal.
That is, when the fault degree corresponding to the execution event is high, the corresponding stack frame, the stack trace information and the fault reason are sent to a pre-specified target device terminal, so that the intelligence of other software developers can be collected to solve the fault events together. It is understood that the target device terminal may be a personal computer, an intelligent mobile terminal, or the like.
More specifically, the process of sending the stack frame, the stack trace information, and the failure cause to the pre-specified target device terminal may include:
and capturing a screen of a display area for displaying the stack frame, the stack tracking information and the fault reason on a local terminal screen to obtain corresponding screen capturing picture information, and then sending the screen capturing picture information to a target equipment terminal.
That is, the present embodiment may send the stack frame, the stack trace information, and the failure reason to the target device terminal in a screen capture manner.
Further, the method in this embodiment may further include: and acquiring information fed back by the target equipment terminal after receiving the stack frame, the stack tracking information and the fault reason, and displaying the fed back information on a local terminal screen in real time.
Correspondingly, the embodiment of the present invention further discloses a program execution behavior visualization system, as shown in fig. 2, the system includes:
an execution process monitoring module 21, configured to monitor an execution process of the program source code by using a program debugger;
an execution process suspending module 22, configured to suspend an execution process of the program source code when it is monitored that an execution event corresponding to a preset monitoring target occurs in the execution process of the program source code; the preset monitoring target is a monitoring target preset on a program debugger;
a code marking module 23, configured to mark a code line corresponding to the execution event on the program source code;
an information obtaining module 24, configured to, when the execution event is a fault event, obtain, by using a program debugger, a stack frame and stack trace information corresponding to the execution event;
the information analysis module 25 is used for analyzing the stack tracking information to obtain a corresponding fault reason;
and the information display module 26 is used for displaying the stack frame, the stack tracking information and the fault reason on the local terminal screen.
For more detailed working processes of the modules, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not repeated here.
It can be seen that, in the embodiment of the present invention, when it is monitored that a specific execution event occurs in an execution process of a program source code, a code line corresponding to the execution event is identified, and when the specific execution event is a fault event, stack trace information is analyzed to obtain a corresponding fault cause, and finally, a stack frame, stack trace information, and a fault cause corresponding to the fault event are displayed on a local terminal screen, so that a software developer can intuitively know a cause of the fault event, and the software developer does not need to manually analyze the source code to obtain the fault cause. Therefore, the embodiment of the invention reduces the manpower required in the debugging process of the program source code.
Further, the system in this embodiment may further include a failure severity level determination module and an information sending module; wherein,
the fault severity level determining module is used for determining the fault severity level corresponding to the execution event according to the fault reason after the information analyzing module obtains the fault reason;
and the information sending module is used for sending the stack frame, the stack tracking information and the fault reason to a pre-specified target equipment terminal when the fault severity level is greater than the preset level.
The information sending module can comprise a screen capturing unit and an information sending unit; wherein,
the screen capture unit is used for capturing a screen of a display area for displaying the stack frame, the stack tracking information and the fault reason on the local terminal screen to obtain corresponding screen capture picture information;
and the information sending unit is used for sending the screen capture picture information to the target equipment terminal.
Finally, it should also be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above detailed description is provided for the program execution behavior visualization method and system, and a specific example is applied in the present disclosure to explain the principle and the implementation of the present invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, 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 invention.
Claims (10)
1. A method for visualizing program execution behavior, comprising:
monitoring the execution process of the program source code by using a program debugger;
if the execution event corresponding to a preset monitoring target occurs in the execution process of the program source code, pausing the execution process of the program source code, and marking a code line corresponding to the execution event on the program source code; the preset monitoring target is a monitoring target preset on the program debugger;
if the execution event is a fault event, acquiring a stack frame and stack trace information corresponding to the execution event by using the program debugger, analyzing the stack trace information to obtain a corresponding fault reason, and displaying the stack frame, the stack trace information and the fault reason on a local terminal screen.
2. The method of program execution behavior visualization as defined in claim 1, wherein the program debugger is a GDB debugger.
3. The method for visualizing the execution behavior of a program according to claim 2, wherein the predetermined monitor target is a stack overflow event, a program interrupt event, or a memory access error event.
4. The program execution behavior visualization method according to claim 3, wherein the program interruption event is an interruption event caused by a line breakpoint, a function breakpoint, a condition breakpoint or an event breakpoint.
5. The method for visualizing the execution behavior of the program according to any one of claims 1 to 4, wherein after the process of analyzing the stack trace information to obtain the corresponding failure cause, the method further comprises:
determining the fault severity level corresponding to the execution event according to the fault reason;
and if the fault severity level is greater than a preset level, sending the stack frame, the stack tracking information and the fault reason to a pre-specified target equipment terminal.
6. The program execution behavior visualization method according to claim 5, wherein the process of sending the stack frame, the stack trace information, and the failure cause to a pre-specified target device terminal includes:
capturing a screen of a display area on the local terminal screen, wherein the display area displays the stack frame, the stack tracking information and the fault reason to obtain corresponding screen capturing picture information;
and sending the screen capture picture information to the target equipment terminal.
7. The program execution behavior visualization method according to claim 5, further comprising:
and acquiring information fed back by the target equipment terminal after receiving the stack frame, the stack tracking information and the fault reason, and displaying the fed back information on a local terminal screen in real time.
8. A program execution behavior visualization system, comprising:
the execution process monitoring module is used for monitoring the execution process of the program source code by using the program debugger;
the execution process pausing module is used for pausing the execution process of the program source code when monitoring that an execution event corresponding to a preset monitoring target occurs in the execution process of the program source code; the preset monitoring target is a monitoring target preset on the program debugger;
the code marking module is used for marking a code line corresponding to the execution event on the program source code;
the information acquisition module is used for acquiring a stack frame and stack tracking information corresponding to the execution event by using the program debugger when the execution event is a fault event;
the information analysis module is used for analyzing the stack tracking information to obtain a corresponding fault reason;
and the information display module is used for displaying the stack frame, the stack tracking information and the fault reason on a local terminal screen.
9. The program execution behavior visualization system according to claim 8, further comprising:
the fault severity level determining module is used for determining the fault severity level corresponding to the execution event according to the fault reason after the information analyzing module obtains the fault reason;
and the information sending module is used for sending the stack frame, the stack tracking information and the fault reason to a pre-specified target equipment terminal when the fault severity level is greater than a preset level.
10. The program execution behavior visualization system according to claim 9, wherein the information sending module comprises:
the screen capture unit is used for capturing a screen of a display area for displaying the stack frame, the stack tracking information and the fault reason on the local terminal screen to obtain corresponding screen capture picture information;
and the information sending unit is used for sending the screen capture picture information to the target equipment terminal.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610694677.9A CN106294175A (en) | 2016-08-19 | 2016-08-19 | A kind of program performs behavior method for visualizing and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610694677.9A CN106294175A (en) | 2016-08-19 | 2016-08-19 | A kind of program performs behavior method for visualizing and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN106294175A true CN106294175A (en) | 2017-01-04 |
Family
ID=57661824
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610694677.9A Pending CN106294175A (en) | 2016-08-19 | 2016-08-19 | A kind of program performs behavior method for visualizing and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106294175A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021139469A1 (en) * | 2020-08-07 | 2021-07-15 | 平安科技（深圳）有限公司 | Gdb-based opencv program visualization method and apparatus, and device and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6219782B1 (en) * | 1997-04-29 | 2001-04-17 | Microsoft Corporation | Multiple user software debugging system |
| US20020095660A1 (en) * | 1998-03-02 | 2002-07-18 | O'brien Stephen Caine | Method and apparatus for analyzing software in a language-independent manner |
| CN101261603A (en) * | 2008-04-09 | 2008-09-10 | 中兴通讯股份有限公司 | Fault locating method and device |
| CN101739333A (en) * | 2008-11-25 | 2010-06-16 | 国际商业机器公司 | Method, tool and device for debugging application program |
| CN102053906A (en) * | 2009-10-30 | 2011-05-11 | 国际商业机器公司 | System and method for collecting program runtime information |
| CN102214137A (en) * | 2010-04-06 | 2011-10-12 | 华为技术有限公司 | Debugging method and debugging equipment |
| CN102262584A (en) * | 2010-05-24 | 2011-11-30 | 北大方正集团有限公司 | Method and device for checking program operation error |
| CN102902620A (en) * | 2011-12-23 | 2013-01-30 | 同济大学 | GDB (genome database) based heterogeneous computing and debugging environment realizing system |
| CN105302732A (en) * | 2015-12-10 | 2016-02-03 | 广东欧珀移动通信有限公司 | Automatic mobile terminal testing method and device |
-
2016
- 2016-08-19 CN CN201610694677.9A patent/CN106294175A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6219782B1 (en) * | 1997-04-29 | 2001-04-17 | Microsoft Corporation | Multiple user software debugging system |
| US20020095660A1 (en) * | 1998-03-02 | 2002-07-18 | O'brien Stephen Caine | Method and apparatus for analyzing software in a language-independent manner |
| CN101261603A (en) * | 2008-04-09 | 2008-09-10 | 中兴通讯股份有限公司 | Fault locating method and device |
| CN101739333A (en) * | 2008-11-25 | 2010-06-16 | 国际商业机器公司 | Method, tool and device for debugging application program |
| CN102053906A (en) * | 2009-10-30 | 2011-05-11 | 国际商业机器公司 | System and method for collecting program runtime information |
| CN102214137A (en) * | 2010-04-06 | 2011-10-12 | 华为技术有限公司 | Debugging method and debugging equipment |
| CN102262584A (en) * | 2010-05-24 | 2011-11-30 | 北大方正集团有限公司 | Method and device for checking program operation error |
| CN102902620A (en) * | 2011-12-23 | 2013-01-30 | 同济大学 | GDB (genome database) based heterogeneous computing and debugging environment realizing system |
| CN105302732A (en) * | 2015-12-10 | 2016-02-03 | 广东欧珀移动通信有限公司 | Automatic mobile terminal testing method and device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021139469A1 (en) * | 2020-08-07 | 2021-07-15 | 平安科技（深圳）有限公司 | Gdb-based opencv program visualization method and apparatus, and device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109302522B (en) | Test method, test device, computer system, and computer medium | |
| CN110580226B (en) | Object code coverage rate testing method, system and medium for operating system level program | |
| CN109543417B (en) | Vulnerability mining method and device based on Qemu platform | |
| CN108959064B (en) | Popup window processing method and device for automatic test | |
| CN112148606B (en) | Buried point test method, buried point test device, buried point test equipment and computer readable medium | |
| CN110442519B (en) | Crash file processing method and device, electronic equipment and storage medium | |
| CN105260082A (en) | Display method for test data and development terminal | |
| US9697107B2 (en) | Testing applications | |
| CN112783756A (en) | Automatic test method, terminal, system and storage medium | |
| CN110806965A (en) | Automatic test method, device, equipment and medium | |
| CN111309606B (en) | Page exception handling method and device, computer equipment and storage medium | |
| CN104426945A (en) | Method and system for acquiring application performance data, and device | |
| CN114064144A (en) | Communication plug-in unit for cross-application data acquisition and communication method | |
| CN115543827A (en) | Buried point data display method and device | |
| CN112911283B (en) | Smart television testing method and device | |
| CN106294175A (en) | A kind of program performs behavior method for visualizing and system | |
| CN111913696A (en) | GDB-based OpenCV program visualization method, device, equipment and storage medium | |
| CN115665009B (en) | DNS root server state monitoring method and device, electronic equipment and medium | |
| CN116909904A (en) | Software function automatic test method based on high-flow high-concurrency condition | |
| CN111597111A (en) | Application program starting speed monitoring method and device | |
| CN114510429B (en) | Debugging method, system and medium based on dynamic symbol execution | |
| CN112437348A (en) | State information acquisition method, storage medium and smart television | |
| CN109032928A (en) | embedded software component monitoring method | |
| CN110554969B (en) | Target code coverage rate testing method, system and medium based on preset breakpoints | |
| CN113918422A (en) | Application starting abnormity detection method, medium, device and computing equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into 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: 20170104 |