CN112131097A - Debugging information dynamic acquisition method and system - Google Patents
Debugging information dynamic acquisition method and system Download PDFInfo
- Publication number
- CN112131097A CN112131097A CN202010733041.7A CN202010733041A CN112131097A CN 112131097 A CN112131097 A CN 112131097A CN 202010733041 A CN202010733041 A CN 202010733041A CN 112131097 A CN112131097 A CN 112131097A
- Authority
- CN
- China
- Prior art keywords
- debugging
- application program
- command
- control module
- debug
- 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 33
- 230000002159 abnormal effect Effects 0.000 claims description 8
- 238000001514 detection method Methods 0.000 claims description 3
- 230000009286 beneficial effect Effects 0.000 abstract description 3
- 239000012792 core layer Substances 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000018109 developmental process Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/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
Abstract
The invention discloses a method and a system for dynamically acquiring debugging information, wherein the method comprises the following steps: providing a debugging command; the control module sends the debugging command to the application program pointed by the debugging command; the application program opens a preset debugging switch according to the debugging command so as to record and generate corresponding log information; the system comprises: the device comprises a generating unit, a first analyzing unit and a sending unit; the beneficial effects are that: the debugging switch preset by the program is turned on in real time through the debugging command to collect debugging information required when the fault occurs, and meanwhile, the system does not need to be re-installed and restarted, so that the loss of a fault site is avoided, and the fault is positioned more accurately.
Description
Technical Field
The invention relates to the technical field of system debugging, in particular to a method and a system for dynamically acquiring debugging information.
Background
In the prior art, in the process of software system development, the most common solution to software failure is to capture a system log under a userdebug version or a release version, and find a failure cause and locate a failure point through analysis of the system log. However, for mobile terminals such as mobile phones, in order to ensure the performance of the system, too many debug switches cannot be opened to capture enough system logs, so that for software failures that occur occasionally or in complex scenes, it is often difficult to find the true failure cause because the system logs are too few. Secondly, in the prior art, after a software operation fault occurs, an analyst needs to separately start some debugging switches of the software to locate the problem, and then recompile the started version and install the software into the system, such a debugging method is mainly used for tracking some static program faults which inevitably occur, but cannot play a role in solving some problems which occur accidentally or occur only when a certain condition is met in a dynamic state, because the problems often depend on the environment and the triggering condition at that time, such a dynamic problem needs to be solved by dynamically tracking in the dynamic operation of the program, and after the system is reinstalled and restarted, the environment and the condition of the fault are likely to be completely damaged.
Disclosure of Invention
According to the problems in the prior art, a method and a system for dynamically acquiring debugging information are provided, which are used for collecting log information required by a fault by opening a preset debugging switch of a program in real time through a debugging command.
The technical scheme specifically comprises the following steps:
a dynamic obtaining method of debugging information is provided, wherein an operating system is provided, the operating system comprises a control module and at least one application program, and the control module communicates with the application program through system messages;
further comprising the steps of:
step S1, providing a debugging command;
step S2, the control module sends the debugging command to the application program pointed by the debugging command;
and step S3, the application program opens a preset debugging switch according to the debugging command so as to record and generate corresponding log information.
Preferably, the operating system sets the debug switches of all the application programs to an off state at startup.
Preferably, when the application program is started, the control module parses the application program, and adds the application program capable of realizing the control of the debug switch into a main thread.
Preferably, in step S2, the control module sends the debug command to the application program by performing an interface callback on the application program located in the main thread.
Preferably, before executing the step S2, the method further includes:
step S20, the control module analyzes the debug command, and determines whether the debug command is valid:
if yes, go to step S2;
if not, discarding the debugging command and exiting.
Preferably, in the step S20, when the debug command is executable and the application program pointed by the debug command is located in the main thread, the debug command is determined to be valid.
Preferably, in step S1, the operating system automatically generates the debug command when abnormal information is detected.
Preferably, in step S1, the debugging command is generated by a manual input of a user.
A dynamic acquisition system of debugging information comprises a control module and at least one application program, wherein the control module is connected with the application program, the application program comprises at least one preset debugging switch, and when the debugging switch is in an on state, the application program records and generates corresponding log information;
the control module further comprises:
the generating unit is used for generating a debugging command;
the first analysis unit is connected with the generation unit and used for analyzing the debugging command and judging whether the debugging command is effective or not;
the sending unit is connected with the analysis unit and used for sending the debugging command to the application program pointed by the debugging command when the judgment result shows that the debugging command is effective;
and the application program opens the corresponding debugging switch according to the debugging command to generate the log information.
Preferably, when the dynamic debugging information obtaining system is started, the application program sets the debugging switch to be in a closed state.
Preferably, wherein the control module further comprises:
the second analysis unit is used for analyzing the application program when the application program is started so as to judge whether the application program can realize debugging switch control;
and the thread management unit is connected with the second analysis unit and used for generating a main thread and adding the application program capable of realizing the control of the debugging switch into the main thread.
Preferably, the sending unit is further connected to the thread management unit, and the sending unit performs interface callback on the application program located in the main thread, so as to send the debug command to the application program.
Preferably, when the debugging command is executable and the application program pointed by the debugging command is located in the main thread, the first parsing unit determines that the debugging command is valid.
Preferably, wherein the generating unit further comprises:
and the detection subunit is used for automatically generating the debugging command when the abnormal information is detected.
Preferably, wherein the generating unit further comprises:
and the input subunit is used for providing an input interface for a user and generating the debugging command according to the input content of the user.
The beneficial effects of the above technical scheme are that:
the method and the system for dynamically acquiring the debugging information are provided, the debugging switch preset by a program is opened in real time through a debugging command to collect the log information required by the occurrence of the fault, and meanwhile, the system does not need to reinstall the program and restart, so that the loss of a fault site is avoided, and the fault is positioned more accurately.
Drawings
FIG. 1 is a flowchart illustrating steps of a method for dynamically obtaining debugging information according to a preferred embodiment of the present invention;
FIG. 2 is a schematic diagram of a system for dynamically obtaining debug information according to a preferred embodiment of the present invention;
FIG. 3 is a schematic diagram of the internal structure of the control module according to the preferred embodiment of the present invention;
FIG. 4 is a schematic diagram of an internal structure of a generating unit according to a preferred 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.
It should be noted that the embodiments and features of the embodiments may be combined with each other without conflict.
The invention is further described with reference to the following drawings and specific examples, which are not intended to be limiting.
A debug information dynamic acquisition method, wherein provide an operating system, the operating system includes a control module 1 and at least one application program 2, the control module 1 communicates with application program 2 through the system message;
as shown in fig. 1, the method further comprises the following steps:
step S1, providing a debugging command;
step S2, the control module 1 sends the debug command to the application program 2 pointed by the debug command;
in step S3, the application program 2 opens a preset debug switch according to the debug command to record and generate corresponding log information.
In a preferred embodiment of the present invention, before the step S2, the method further includes:
step S20, the control module 1 parses the debug command, and determines whether the debug command is valid:
if yes, go to step S2;
if not, the debugging command is discarded and quit.
As a preferred embodiment, the method is applied to a mobile terminal or a fixed terminal, where an operating system may be an android operating system or a Linux operating system, and the following description will be given by taking the android operating system in the mobile terminal as an example, a control module 1 in the operating system corresponds to a system core layer under an android system architecture, an application program 2 corresponds to an application program 2(APK) installed in the android system, and under the android operating system, the system core layer and the application program package perform communication interaction through system messages.
The application program package is preset with a debugging switch in the development process, the debugging switch is used for controlling the recording and output of logs, a user can open one or all debugging switches of a specific application program package in a user-defined mode through a debugging command so as to record and collect log information required by software running faults, or when an operating system detects corresponding abnormity, the debugging command is automatically generated so as to directly open the debugging switches in related application program packages, and then corresponding debugging information is recorded and generated for output, and research personnel can directly, quickly and accurately find the reasons of faults after obtaining the debugging information and locate the fault occurrence points.
In a specific embodiment of the present invention, in order not to affect the performance of the mobile terminal, in an initial state, a preset debug switch in each application 2 is in a closed state by default, that is, no recording and outputting of a corresponding log is performed, so as to avoid excessive occupation of limited processor resources, when a corresponding software operation fault occurs, the system generates a corresponding debug command, the debug command points to the specific application 2 in which the operation fault occurs, and the debug command is used for assigning values to the corresponding debug switch in the application 2, so as to switch the debug switch from the default closed state to an open state.
In the preferred embodiment of the present invention, the operating system sets the debug switches of all the applications 2 to the off state at startup.
Specifically, in this embodiment, in order not to affect the performance of the mobile terminal, when the user restarts the mobile terminal each time, all the debug switches are reset to the off state, and meanwhile, the user may selectively turn on or turn off the designated debug switch in a manual manner during the normal turning-on process of the system, so that the accurate capture of the debug information is ensured, the normal use of the mobile terminal is not excessively affected, and the finally obtained debug information is uploaded to the background server by the mobile terminal and provided to the manufacturer for tracking the cause of the abnormal problem.
In another embodiment of the present invention, after the mobile terminal turns on the debug switch due to a sudden failure, records and generates corresponding log information, and uploads the log information to the cloud, the user can restore the system to the initial state by restarting the mobile terminal, and during the restart process, the system resets the debug switch in the application program 2 to the off state, so as to avoid affecting the normal use of the user and avoid that the log output occupies too much processor resources.
In the preferred embodiment of the present invention, when the application 2 is started, the control module 1 parses the application 2, and adds the application 2 capable of implementing the debugging switch control into a main thread.
Specifically, in this embodiment, during the starting process of the application 2, the control module 1 parses the application 2, in an embodiment of the present invention, the activity manager service and the package manager service in the control module 1 of the android operating system parse all APKs in the resolvable activity, and if the debugging interface is implemented, the related application 2 is saved in the ActivityThread. In this embodiment, since the application program 2 is an application program package developed by a third party, all APKs need to be analyzed first in the system starting process to determine which APKs can implement the debug interface, that is, the control module 1 may assign values and control the debug switch to the APK to turn on or turn off the corresponding debug switch.
In step S2, the control module 1 sends the debug command to the application 2 by performing an interface call-back to the application 2 located in the main thread.
Specifically, in this embodiment, the control module 1 may parse the generated debug command to determine whether the debug command is valid and executable, discard the invalid debug command, and then perform the next execution on the valid debug command, specifically, perform interface callback on the application program 2 side located in the main thread to send the debug command, and the application program 2 parses the transmitted debug command in the interface callback, and then perform switch value assignment on the corresponding debug switch to implement the turning on and off of the debug switch.
In the preferred embodiment of the present invention, in step S20, when the debug command is executable and the application 2 pointed by the debug command is located in the main thread, it is determined that the debug command is valid.
Specifically, in this embodiment, in the android system architecture, in a first step, the acitvitymanagergshellcommand in the control module 1 parses the received debug command to determine whether the debug command is valid and executable, directly discards an invalid command, and performs a next step on a valid command. Secondly, the activityManagerservice in the control module 1 further analyzes the debugging command, further determines the effectiveness and the executability of the debugging command, and judges whether the application program 2, namely the APK, pointed by the debugging command is positioned in the main thread, if the application program 2 pointed by the debugging command is not positioned in the main thread, the application program 2 does not support the debugging function, and the debugging switch can not be controlled, the debugging command is judged to be invalid. On the contrary, if the application program 2 pointed by the debug command is in the main thread, which indicates that the application program 2 supports the debug function, the debug command is determined to be valid.
In the preferred embodiment of the present invention, in step S1, the operating system automatically generates a debug command when detecting the abnormal information.
In the preferred embodiment of the present invention, in step S1, the debug command is generated by manual input from the user.
Specifically, in the above-described embodiment, the user may manually perform command input through an adb command or a factory mode UI of the mobile terminal to generate the debug command.
A system for dynamically acquiring debugging information is shown in FIG. 2, and comprises a control module 1 and at least one application program 2, wherein the control module 1 is connected with the application program 2, the application program 2 comprises at least one preset debugging switch, and when the debugging switch is in an on state, the application program 2 records and generates corresponding log information;
as shown in fig. 3, the control module 1 further includes:
a generating unit 10, configured to generate a debug command;
the first analysis unit 11 is connected with the generation unit 10 and is used for analyzing the debugging command and judging whether the debugging command is effective or not;
the sending unit 12 is connected to the analysis unit, and is used for sending the debugging command to the application program 2 pointed by the debugging command when the judgment result shows that the debugging command is valid;
the application program 2 opens the corresponding debug switch according to the debug command to generate log information.
As a preferred embodiment, the system is applied to a mobile terminal, a control module 1 in the system corresponds to a system core layer under an android system architecture, an application program 2 corresponds to an application program package installed in the android system, and the system core layer and the application program package perform communication interaction through system messages under an android operating system.
The application program package is preset with a debugging switch in the development process, the debugging switch is used for controlling the recording and output of logs, a user can open one or all debugging switches of a specific application program package in a user-defined mode through a debugging command so as to record and collect log information required by software running faults, or when an operating system detects corresponding abnormity, the debugging command is automatically generated so as to directly open the debugging switches in related application program packages, and then corresponding debugging information is recorded and generated for output, and research personnel can directly, quickly and accurately find the reasons of faults after obtaining the debugging information and locate the fault occurrence points.
In a specific embodiment of the present invention, in order not to affect the performance of the mobile terminal, in an initial state, a preset debug switch in each application 2 is in a closed state by default, that is, no recording and outputting of a corresponding log is performed, so as to avoid excessive occupation of limited processor resources, when a corresponding software operation fault occurs, the generating unit 10 generates a corresponding debug command, where the debug command points to the specific application 2 in which the operation fault occurs, and the debug command is used to assign a value to the corresponding debug switch in the application 2, so as to switch the debug switch from the default closed state to an open state.
In the preferred embodiment of the present invention, when the system for dynamically obtaining debugging information is started, the application 2 sets the debugging switch to the off state.
Specifically, in this embodiment, in order not to affect the performance of the mobile terminal, when the user restarts the mobile terminal each time, all the debug switches are reset to the off state, and meanwhile, the user may selectively turn on or turn off the designated debug switch in a manual manner during the normal turning-on process of the system, so that the accurate capture of the debug information is ensured, the normal use of the mobile terminal is not excessively affected, and the finally obtained debug information is uploaded to the background server by the mobile terminal and provided to the manufacturer for tracking the cause of the abnormal problem.
In another specific embodiment of the present invention, after the mobile terminal turns on the debug switch due to a sudden failure, records and generates corresponding log information, and uploads the log information to the background server, the user can restore the system to the initial state by restarting the mobile terminal, and during the restart process, the system will reset the debug switch in the application program 2 to the off state, so as to avoid affecting the normal use of the user, and avoid that the log output occupies too much processor resources.
In a preferred embodiment of the present invention, the control module 1 further comprises:
a second analyzing unit 13, configured to analyze the application program 2 when the application program 2 is started, so as to determine whether the application program 2 can implement debug switch control;
and the thread management unit 14 is connected with the second analysis unit 13 and is used for generating a main thread and adding the application program 2 capable of realizing the control of the debugging switch into the main thread.
Specifically, in this embodiment, during the starting process of the application 2, the second parsing unit 13 in the control module 1 parses the application 2, the thread management unit 14 creates a main thread in advance, and if the second parsing unit 13 implements a debugging interface, the thread management unit 14 stores the relevant application 2 in the main thread. In this specific embodiment, since the application program 2 is an application program package developed by a third party, the started application program 2 needs to be analyzed first when the program is started to determine which application programs 2 can implement the debugging interface, that is, the control module 1 may assign and control the debugging switch to the application program 2 to turn on or turn off the corresponding debugging switch.
In the preferred embodiment of the present invention, the sending unit 12 is further connected to the thread management unit 14, and the sending unit 12 sends the debug command to the application program 2 by performing an interface call-back on the application program 2 located in the main thread.
Specifically, in this embodiment, the first parsing unit 11 parses the generated debug command to determine whether the debug command is valid and executable, and after discarding the invalid debug command, the sending unit 12 performs interface callback on the application program 2 end located in the main thread to send the debug command, where the application program 2 parses the transmitted debug command in the interface callback, and then performs switch value assignment on the corresponding debug switch to turn on and off the debug switch.
In the preferred embodiment of the present invention, the sending unit 12 determines that the debugging command is valid when the debugging command is executable and the application 2 pointed by the debugging command is located in the main thread.
In a preferred embodiment of the present invention, as shown in fig. 4, the generating unit 10 further includes:
a detection subunit 100, configured to automatically generate a debug command when the abnormal information is detected.
In a preferred embodiment of the present invention, the generating unit 10 further comprises:
and the input subunit 101 is configured to provide an input interface for a user, and generate a debugging command according to input content of the user.
The beneficial effects of the above technical scheme are that:
the debugging information required when a fault occurs is collected by opening a preset debugging switch of a program in real time through a debugging command, and meanwhile, the system does not need to reinstall the program and restart, so that the loss of a fault site is avoided, and the fault is positioned more accurately.
While the invention has been described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention.
Claims (15)
1. A dynamic obtaining method of debugging information is characterized in that an operating system is provided, the operating system comprises a control module and at least one application program, and the control module communicates with the application program through system messages;
further comprising the steps of:
step S1, providing a debugging command;
step S2, the control module sends the debugging command to the application program pointed by the debugging command;
and step S3, the application program opens a preset debugging switch according to the debugging command so as to record and generate corresponding log information.
2. The method according to claim 1, wherein the operating system sets the debug switches of all the applications to an off state when starting up.
3. The method according to claim 1, wherein when the application program is started, the control module parses the application program, and adds the application program that can implement the control of the debug switch into a main thread.
4. The method according to claim 3, wherein in step S2, the control module sends the debug command to the application program by making an interface call back to the application program located in the main thread.
5. The method for dynamically obtaining debugging information according to claim 4, further comprising, before performing step S2:
step S20, the control module analyzes the debug command, and determines whether the debug command is valid:
if yes, go to step S2;
if not, discarding the debugging command and exiting.
6. The method for dynamically obtaining debugging information according to claim 5, wherein in step S20, when the debugging command is executable and the application program pointed by the debugging command is located in the main thread, it is determined that the debugging command is valid.
7. The method for dynamically obtaining debugging information according to claim 1, wherein in step S1, the operating system automatically generates the debugging command when abnormal information is detected.
8. The method for dynamically obtaining debugging information according to claim 1, wherein in step S1, the debugging command is generated by manual input of a user.
9. A dynamic acquisition system of debugging information is characterized by comprising a control module and at least one application program, wherein the control module is connected with the application program, the application program comprises at least one preset debugging switch, and when the debugging switch is in an on state, the application program records and generates corresponding log information;
the control module further comprises:
the generating unit is used for generating a debugging command;
the first analysis unit is connected with the generation unit and used for analyzing the debugging command and judging whether the debugging command is effective or not;
the sending unit is connected with the analysis unit and used for sending the debugging command to the application program pointed by the debugging command when the judgment result shows that the debugging command is effective;
and the application program opens the corresponding debugging switch according to the debugging command to generate the log information.
10. The system according to claim 9, wherein the control module sets the debug switch of the application program to an off state when the system is started.
11. The system for dynamically acquiring debugging information according to claim 9, wherein the control module further comprises:
the second analysis unit is used for analyzing the application program when the application program is started so as to judge whether the application program can realize debugging switch control;
and the thread management unit is connected with the second analysis unit and used for generating a main thread and adding the application program capable of realizing the control of the debugging switch into the main thread.
12. The system according to claim 11, wherein the sending unit is further connected to the thread management unit, and the sending unit sends the debug command to the application program by performing an interface callback on the application program located in the main thread.
13. The system of claim 12, wherein the first parsing unit determines that the debugging command is valid when the debugging command is executable and the application program pointed by the debugging command is located in the main thread.
14. The system for dynamically acquiring debugging information according to claim 9, wherein said generating unit further comprises:
and the detection subunit is used for automatically generating the debugging command when the abnormal information is detected.
15. The system for dynamically acquiring debugging information according to claim 9, wherein said generating unit further comprises:
and the input subunit is used for providing an input interface for a user and generating the debugging command according to the input content of the user.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010733041.7A CN112131097A (en) | 2020-07-27 | 2020-07-27 | Debugging information dynamic acquisition method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010733041.7A CN112131097A (en) | 2020-07-27 | 2020-07-27 | Debugging information dynamic acquisition method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112131097A true CN112131097A (en) | 2020-12-25 |
Family
ID=73850555
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010733041.7A Pending CN112131097A (en) | 2020-07-27 | 2020-07-27 | Debugging information dynamic acquisition method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112131097A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113268274A (en) * | 2021-05-18 | 2021-08-17 | 深圳市广和通无线股份有限公司 | Operating system starting method and device, electronic equipment and storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050022167A1 (en) * | 2003-07-25 | 2005-01-27 | Microsoft Corporation. | Method and system for fast application debugging |
| CN101122880A (en) * | 2007-09-17 | 2008-02-13 | 福建星网锐捷网络有限公司 | Embedded type system of embed type debugging device and embedded type system debugging method |
| CN101398780A (en) * | 2007-09-27 | 2009-04-01 | 国际商业机器公司 | Instantly debugging method and system based on schedule debugger |
| CN102467447A (en) * | 2010-11-16 | 2012-05-23 | 鸿富锦精密工业（深圳）有限公司 | Driver debugging system and method |
| CN104281520A (en) * | 2013-07-10 | 2015-01-14 | 腾讯科技（深圳）有限公司 | Tracking and debugging method, device and system |
| CN106354623A (en) * | 2015-07-16 | 2017-01-25 | 深圳市奇辉电气有限公司 | Linux-based application program debugging method and device |
-
2020
- 2020-07-27 CN CN202010733041.7A patent/CN112131097A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050022167A1 (en) * | 2003-07-25 | 2005-01-27 | Microsoft Corporation. | Method and system for fast application debugging |
| CN101122880A (en) * | 2007-09-17 | 2008-02-13 | 福建星网锐捷网络有限公司 | Embedded type system of embed type debugging device and embedded type system debugging method |
| CN101398780A (en) * | 2007-09-27 | 2009-04-01 | 国际商业机器公司 | Instantly debugging method and system based on schedule debugger |
| CN102467447A (en) * | 2010-11-16 | 2012-05-23 | 鸿富锦精密工业（深圳）有限公司 | Driver debugging system and method |
| CN104281520A (en) * | 2013-07-10 | 2015-01-14 | 腾讯科技（深圳）有限公司 | Tracking and debugging method, device and system |
| CN106354623A (en) * | 2015-07-16 | 2017-01-25 | 深圳市奇辉电气有限公司 | Linux-based application program debugging method and device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113268274A (en) * | 2021-05-18 | 2021-08-17 | 深圳市广和通无线股份有限公司 | Operating system starting method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110515820B (en) | Server fault maintenance method and device, server and storage medium | |
| KR101008977B1 (en) | Method of testing OSGi service platform and test tool thereof | |
| CN106648863B (en) | Android application installation package, application target process keep-alive method and system | |
| CN110309029B (en) | Abnormal data acquisition method and device, computer equipment and storage medium | |
| CN111104315A (en) | Test script generation method and device and computer readable storage medium | |
| WO2018019242A1 (en) | Self-recovery method and self-recovery system for web server | |
| CN111382048B (en) | Management method and device for mobile equipment on true machine test platform | |
| CN108762886B (en) | Fault detection recovery method and system for virtual machine | |
| CN110119350A (en) | Software Development Kit test method, device and equipment and computer storage medium | |
| CN111949368A (en) | Application program control method and device | |
| CN111124761B (en) | Equipment restarting method, device, equipment and medium | |
| CN111813646A (en) | Method and device for injecting application probe in docker container environment | |
| CN111625425A (en) | Data monitoring method, device and system | |
| CN112131097A (en) | Debugging information dynamic acquisition method and system | |
| CN105700973A (en) | Restart method and device for CLI (command line interface) fault | |
| CN111782522A (en) | Output method of trace message, electronic device and storage medium | |
| CN107105100B (en) | Method and system for monitoring mobile terminal game | |
| CN110990221A (en) | Kernel LKM-based Android platform malicious software automatic detection method and system | |
| CN110928787A (en) | Automatic test script recording and playback method, device, equipment and storage medium | |
| KR20140020287A (en) | Software operability service | |
| CN114217925A (en) | Business program operation monitoring method and system for realizing abnormal automatic restart | |
| CN114884840A (en) | Application health state checking method and electronic equipment | |
| WO2010018619A1 (en) | Information processor and hang-up cause investigation information acquiring method | |
| CN111752736A (en) | Remote collection method and system for Linux system downtime information | |
| CN111400094A (en) | Method, device, equipment and medium for restoring factory settings of server system |
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: 20201225 |