CN107678938A - The adjustment method and equipment of a kind of application program - Google Patents

Abstract

This specification discloses a debugging method and equipment for an application program. After the debugging instruction is determined, the debugging instruction is sent to the target client, so that the target client can debug the running status of the installed application program according to the debugging instruction, and obtain the debugging result. After receiving the debugging result sent by the target client, analyze whether the application program is abnormal based on the debugging result.

Description

Application program debugging method and device

technical field

The present application relates to the field of computer technology, in particular to a method and device for debugging an application program.

Background technique

With the development of Internet technology, smart devices are becoming more and more popular, especially mobile smart devices. Usually, an operating system is installed on the smart device, based on the operating system, various application programs (Application, APP for short) can be run, so as to realize corresponding operation or control functions.

In practical applications, there are many types of smart devices, and the same version of the operating system can be installed on smart devices of different models. Therefore, the same application program may run on smart devices of different models. In addition, for different models or the same model, the versions of the installed operating systems are also different, and the same application program may run based on different versions of the operating system.

Therefore, the industry urgently needs a solution that can remotely debug an application program.

Contents of the invention

In view of this, the embodiments of this specification provide a method and device for debugging an application program, which are used to effectively implement a solution for debugging an application program.

The embodiment of this description adopts the following technical solutions:

The embodiment of this specification provides a debugging method for an application program, including:

Determine the debugging instructions;

Send the debugging instruction to the target client, so that the target client can debug the operation of the installed application program according to the debugging instruction, and obtain a debugging result;

receiving the debugging result sent by the target client, and analyzing whether the application program is abnormal based on the debugging result.

The embodiment of this specification also provides a debugging method for an application program, including:

Receive debugging instructions sent by the server;

Debugging the running status of the installed application program based on the debugging instruction, and obtaining a debugging result;

The debugging result is sent to the server, so that the server analyzes whether the application program is abnormal according to the debugging result.

The embodiment of this specification also provides an application program debugging device, including:

Determine the module and determine the debugging instruction;

The sending module sends the debugging instruction to the target client, so that the target client can debug the operation of the installed application program according to the debugging instruction, and obtain the debugging result;

The receiving module receives the debugging result sent by the target client, and analyzes whether the application program is abnormal based on the debugging result.

The embodiment of this specification also provides an application program debugging device, including:

The receiving module receives the debugging instructions sent by the server;

The debugging module, based on the debugging instruction, debugs the operation of the installed application program, and obtains the debugging result;

The sending module sends the debugging result to the server, so that the server analyzes whether the application program is abnormal according to the debugging result.

The embodiment of this specification also provides an application program debugging device, including at least one processor and a memory, the memory stores a program, and is configured to perform the following steps by the at least one processor:

Determine the debugging instructions;

Send the debugging instruction to the target client, so that the target client can debug the operation of the installed application program according to the debugging instruction, and obtain a debugging result;

receiving the debugging result sent by the target client, and analyzing whether the application program is abnormal based on the debugging result.

The embodiment of this specification also provides an application program debugging device, including at least one processor and a memory, the memory stores a program, and is configured to perform the following steps by the at least one processor:

Receive debugging instructions sent by the server;

Debugging the running status of the installed application program based on the debugging instruction, and obtaining a debugging result;

The debugging result is sent to the server, so that the server analyzes whether the application program is abnormal according to the debugging result.

The above at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects:

On the server side, determine the debugging instruction, and send it to the target client; on the target client side, debug the operating status of the installed application program based on the debugging instruction, and obtain the debugging result. Afterwards, on the server side, analyze whether the application program is abnormal based on the debugging results, which may include judging the abnormality in the application program and/or determining the cause of the abnormality in the application program, and then eliminating the abnormality according to the analysis result. In particular, but not limited to, if the problem event generated by the running of the application is related to the running environment, it is inoperable to reproduce the problem event on the development side, or the development of the same running environment on the development side to reproduce the problem event If the cost is relatively high, the technical solutions recorded in the embodiments of this specification can be used to remotely debug the target client, which is easy to implement.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of this specification and constitute a part of this specification. The schematic embodiments and descriptions of this specification are used to explain this application and do not constitute an improper limitation of this application. In the attached picture:

FIG. 1 is a timing diagram of an application program debugging method provided by an embodiment of this specification;

FIG. 2 is a flow chart of an application program debugging method provided by an embodiment of this specification;

FIG. 3 is a flow chart of an application program debugging method provided by an embodiment of this specification;

FIG. 4 is a flow chart of an application program debugging method proposed by an embodiment of this specification;

FIG. 5 is a structural diagram of an application program debugging device proposed in the embodiment of this specification;

FIG. 6 is a structural diagram of an application program debugging device proposed by the embodiment of this specification.

detailed description

In real-world applications, differences between smart devices may cause individual differences between operating systems, and there may also be individual differences between different versions of operating systems. These individual differences between operating systems make the running of the same application There are differences between environments, so the running results may be different. For example, on some smart devices, problems such as incompatibility, failure to display running results, and wrong running results may occur. At this time, it is necessary to debug the application program in which the problem event occurs, so as to eliminate the problem event corresponding to the specific operating environment. However, the dilemma encountered in the debugging process is that due to the difference in the operating environment, it is not feasible to reproduce specific problem events one by one on the development end of the application, or to develop the same operating environment on the development end to reproduce the problem Events are expensive to develop.

In view of this, the embodiments of this specification provide a method and device for debugging an application program. FIG. 1 is a sequence diagram of an application program debugging method provided by an embodiment of this specification, and the debugging method is as follows.

Step 101: The target client sends a problem event to the server. The problem event may be an abnormal result when the user operates the target client, such as compatibility issues, failure to display running results, and wrong running results.

Step 103: Based on the problem event, the server determines the debugging object and the debugging instruction for the debugging object. There is an exception in a specific application program or a specific subroutine in the application program in the target client, causing a specific problem event. Therefore, the debugging object targeted by the debugging instruction can be an installed application program or a subroutine of the application program. program.

Step 105: the server sends the debugging instruction to the target client.

Step 107: Based on the debugging instruction, the target client debugs the running status of the installed application program, and obtains a debugging result.

Step 109: The server receives the debugging result from the target client, and analyzes whether the application program is abnormal based on the debugging result, and can further analyze the cause of the abnormality in the application program. Afterwards, developers can fix and update the application to resolve problematic events on the target client.

In the embodiment of this specification, a debugging instruction can be added to the target client, and the target client can debug the entire operation of the application program based on the debugging instruction, and obtain the debugging result. Debugging results include but are not limited to collecting log data during the running of the application. Using these log data, the execution logic of the application can be analyzed to determine the relationship between the execution logic and problem events, so as to find out whether there is an exception in the application and whether the application is abnormal. Evidence of the reason for the existence of the exception. In particular, but not limited to, if the problem event is related to the operating environment of the application, it is inoperable to reproduce the problem event at the development end, or the development cost of developing the same operating environment to reproduce the problem event at the development end is relatively low. If it is high, the debugging method described in the embodiment of this specification can be used to perform remote debugging on the target client, which is easy to implement.

Fig. 2 is a flow chart of an application program debugging method provided by the embodiment of this specification, which is summarized as follows. The debugging method recorded in the embodiment of this specification roughly includes the following four periods: development period I, compilation period II, debugging period III and Analysis Period IV. In the development phase I and the compilation phase II, the debug object and the debugging instructions for the debug object can be determined. In the debugging phase III, the debugging object is debugged by using the debugging command. In analysis phase IV, the application is analyzed for anomalies using the debugging results. The technical solutions that occurred in the above four periods described in the embodiments of this specification will be described in detail below.

In order to make the purpose, technical solution and advantages of this specification clearer, the technical solution of this application will be clearly and completely described below in conjunction with specific embodiments of this specification and corresponding drawings. Apparently, the described embodiments are only some of the embodiments in this specification, not all of them. Based on the embodiments in this specification, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present application.

The technical solutions provided by each embodiment of this specification will be described in detail below in conjunction with the accompanying drawings.

FIG. 3 is a flow chart of a debugging method for an application program provided by an embodiment of this specification, and the debugging method is as follows. The execution subject of the debugging method may be a server.

Step 302: Determine the debugging instruction.

In the embodiment of this specification, the timing of generating the debugging instruction may be to determine the debugging instruction based on a problem event generated by the target client, or to determine the debugging instruction based on the debugging requirements for the current version of the target client application program.

If the debugging instruction is determined based on the problem event, then determining the debugging instruction may include:

Determining the problem event corresponding to the target client;

Generate debug instructions corresponding to problem events.

The problem events recorded in the embodiments of this manual include but are not limited to problems such as the page cannot be displayed, the page is displayed incompletely, and the target client is compatible with the smart device. The correspondence between the problem event and the target client means that the problem event occurs during the process of using the target client to implement an operation or a function. Specifically, the problem event may be generated due to an abnormal operation result of a specific installed application program or a subprogram in the application program in the target client

Wherein, determining the problem event corresponding to the target client may be that the user directly reports to the server through the target client, may be determined according to user complaints received by the developer of the target client, or may be determined by the server monitoring the target client. It can also be determined through other channels, which is not specifically limited here.

In the embodiment of this specification, determining the problem event corresponding to the target client may be completed in the development phase I (refer to FIG. 2 ).

The function to be realized by the debugging instruction described in the embodiment of this specification is to debug the operation status of the installed application program in the target client, and obtain the debugging result, which can be used to analyze whether the application program is abnormal. If the debugging instruction is determined based on the problem event, the application program needs to reproduce the problem event again during the running process, then the specific functions of the debugging instruction can include but are not limited to: on the premise of not affecting and interfering with the running process of the application program , to obtain the log data generated during the running of the application.

In the embodiment of this specification, the specific steps of determining the debugging instruction may include:

Determine the debugging object and the debugging code corresponding to the debugging object;

Based on the debug code, the debug instruction is generated.

The debugging object described in the embodiment of this specification includes but is not limited to an application program installed on the target client, a subroutine in the application program, a section of code or a section of function, which is not specifically limited here. The debugging object may be determined based on the determined problem event, or may be determined automatically based on the debugging requirement by the developer of the target client application program.

In the embodiment of this specification, the object relationship between the debug object and the debug code may mean that the operation or function corresponding to the debug object can be realized by running the debug code, and the running status of the debug object can be debugged at the same time. For example, if the debugging object is an application program installed in the target client, when the application program is executed, the debugging code is run to realize an operation or function corresponding to the application program, and at the same time, the running status of the application program is debugged.

In the embodiment of this specification, determining the debugging code corresponding to the debugging object includes:

Determine the source code corresponding to the debugging object, which can be obtained from the code repository;

Edit the source code without changing the operating logic of the source code to obtain the debug code. Wherein, editing the source code may be adding patch codes to the source code.

Preferably, determining the debugging code corresponding to the debugging object includes:

Determine the source code corresponding to the debugging object;

Edit the first breakpoint identifier and the second breakpoint identifier in the source code, and execute the compilation operation on the edited source code to obtain the debug code corresponding to the debug object;

Wherein, the first breakpoint identifier is used to represent the start of debugging, and the second breakpoint identifier is used to represent the end of debugging.

Among them, the first breakpoint identifier can be inserted into the start position of the source code corresponding to the debugging object, or inserted into the entry position of the target function corresponding to the specific problem event, so that when the source code starts to run, the input parameters can be collected based on the first breakpoint identifier. parameter. The second breakpoint mark is used to insert the end position of the source code, or insert the exit position of the target function corresponding to the specific problem event, so that when the source code running process ends, the parameters are collected based on the second breakpoint mark, and the collection ends log data.

In the development period I (refer to FIG. 2), the developer can add the first breakpoint identifier and the second breakpoint identifier in the source file; or the server corresponding to the development platform receives the editing instruction sent by the developer, and according to the editing instruction, the Add the first breakpoint mark and the second breakpoint mark in the source file.

In the compilation phase II (refer to Figure 2), the server corresponding to the development platform can use the compilation tool to automatically compile the first breakpoint identifier, obtain the coded first breakpoint identifier, and automatically translate the second breakpoint identifier , to obtain the coded second breakpoint identifier.

In the embodiment of this specification, the method for forming the first breakpoint identifier and the second breakpoint identifier may include: compiling manually during the development period I, which is not specifically limited here.

Preferably, before compiling the edited source code, the debugging method may further include:

Edit the debug result sending switch in the source code;

Wherein, the switch state of the debugging result sending switch is used to determine whether to send the debugging result to the server.

In the compilation phase II (refer to FIG. 2 ), use the compilation platform to configure the debugging result sending switch in the source code. Among them, the so-called debugging result sending switch can be set to be turned on based on specific needs, so that the log data in the debugging result can be sent to the server in a timely manner, so as to save the traffic consumption of the target client. Specifically, the debugging result sending switch is turned on during the debugging process, so that the log data in the debugging result obtained in real time is sent to the server in real time.

Optionally, a debug result sending switch can be inserted at the entry and exit positions of the corresponding function in the source code to ensure that each time one or a set of log data is input or output, the debug result sending switch is turned on to send the log data to the server in real time . When no log data is generated, the debugging result sending switch is turned off, and no log data is returned to the server.

Optionally, the debugging result sending switch can be configured to remain open during a running cycle of the debugging file, so that the debugging results during the running of the application are packaged and returned to the server after being received during the running process.

The debugging result sending switch described in the embodiment of this specification may exist in the form of code, for example, it may be a piece of code in the debugging code.

Preferably, before compiling the edited source code, the debugging method may further include:

Edit the debugging process start instruction in the source code;

Wherein, the instruction for starting the debugging process is used to instruct the terminal device to start the debugging process for the debugging object.

In the compilation phase II (refer to FIG. 2 ), the debugging process start instruction is configured in the source code by using the compilation platform. Wherein, the so-called debugging process start instruction can be configured to start the debugging process according to needs, so as to avoid affecting the running status of the application program. Specifically, the instruction for starting the debugging process can be set to control the target client to start the debugging process when the application starts, so as to allocate resources for running the debugging code. At this point, the debugging process can be allocated sufficient resources to ensure that the debugging code runs smoothly. This can avoid the problem of insufficient resource allocation that may exist when the debugging process is started during the running of the application.

In this embodiment of the specification, the instruction to start the debugging process may exist in the form of code, for example, it may be a piece of code in the debugging code. Specifically, this piece of code can be inserted into the beginning of the corresponding source code of the application program, which can ensure that when the application program is started, this piece of code can be run immediately to start the debugging process.

In the embodiment of this specification, the debugging instruction is generated based on the debugging code, so that the debugging instruction can be implemented through code; the debugging instruction can also be implemented through the communication protocol between the target client and the server, which is not specifically limited here .

Further, generating debugging instructions based on the debugging code may include:

Process the debug code to get the debug file;

The debugging instruction is generated based on the debugging file.

In this way, the debugging instruction is implemented in the form of a debugging file, so that the target client can load the debugging file and run the debugging code in the debugging file to debug the operation of the installed application program.

Preferably, the debug code is processed to obtain a debug file, which may include:

Encapsulate the debugged code into an object file;

Compare the difference between the source file and the target file corresponding to the debugging object, and obtain the debugging file based on the difference.

In the development stage, the source files corresponding to the debugging objects are backed up and stored in the database. The smart device downloads the source file corresponding to the target client application program from the database and stores it locally, and implements an operation or function by calling the source file stored in the smart device. In the development period I (refer to FIG. 2 ), after the debugging object is determined, the source file corresponding to the debugging object is obtained from the database, and the source file contains the source code corresponding to the debugging object. Edit the source file, for example, add patch code to the source code to obtain the target file, so that the target file contains both the source code and the patch code. Based on the function to be realized by the final debugging instruction, it should be ensured that the execution logic of the source code in the object file will not change. Afterwards, the developer can store the target file back into the database for subsequent use.

In the compilation phase II (refer to Figure 2), the source file and the target file are retrieved from the database; the difference between the source file and the target file is compared using the Diff tool, and a patch (Patch) file can be automatically generated, and the patch file is a debug file. document. In this case, during the debugging process, it is not necessary to upgrade the current version of the target client in full, but only incrementally upgrade the current version of the target client in the form of a patch file, which has the advantage of reducing development costs and debugging cost.

Step 304: Send the debugging instruction to the target client, so that the target client can debug the running status of the installed application program according to the debugging instruction, and obtain the debugging result.

Before sending the debugging instruction to the target client, the debugging instruction can be encrypted. In this way, the target client can decrypt and verify the debugging instructions to verify the reliability and security of the debugging instructions.

In the embodiment of this specification, the debugging instructions are sent to the target client, including:

determine the user identity and/or device identity of the target client;

Send the debugging instruction to the target client corresponding to the user ID and/or device ID.

The debugging instruction can be sent to a specific target client, and the specific target client can be the client sending the problem event, thereby realizing one-to-one remote debugging of a specific target client application program; the specific target client can also be It is the specific version of the client corresponding to the same operating environment determined on the development side, so as to realize the remote debugging of the specific version of the target client application.

If the target client is the one sending the problem event, determine the user ID and/or device ID of the target client, which may include:

If the problem event carries the user ID and/or the device ID, the user ID and/or the device ID are parsed from the problem event.

If the target client is a client corresponding to the same operating environment, the device identification and/or user identification corresponding to the same operating environment is obtained from the database.

Step 306: Receive the debugging result sent by the target client, and analyze whether the application program is abnormal based on the debugging result.

Using the application program debugging method described in the embodiments of this specification, the remote debugging of the target client application program can be implemented at the development end, and whether the application program is abnormal is analyzed based on the obtained debugging results. The debugging results include but are not limited to one or more of the user behavior data during the running of the application and the running data of the application. This is the most direct basis for analyzing the application. It can analyze the execution logic of the application and determine the application The relationship between problem events caused by program exceptions and execution logic. In particular, but not limited to, if the problem event is related to the operating environment of the application, it is inoperable to reproduce the problem event at the development end, or the development cost of developing the same operating environment to reproduce the problem event at the development end is relatively low. If it is high, the debugging method described in the embodiment of this specification can be used to perform remote debugging on the target client, which is easy to implement.

FIG. 4 is a flow chart of an application program debugging method proposed by the embodiment of this specification, and the debugging method is as follows. The execution subject of the debugging method may be a client, hereinafter referred to as a target client.

Step 401: Receive a debugging instruction sent by the server.

For the content of the debugging instruction, reference may be made to the content of step 302 above, which will not be repeated here.

In the embodiment of this specification, before receiving the debugging instruction sent by the server, the debugging method further includes:

identify problem events;

Send problem events to the server.

In this case, the server can generate debug instructions based on the problem event, the debug instructions being specific to the problem event.

Preferably, sending problem events to the server may include:

Send the problem event carrying the user ID and/or device ID to the server, so that the server returns a debugging instruction based on the user ID and/or device ID.

In this case, precise remote control of specific target clients can be achieved.

Step 403: Based on the debugging instruction, debug the running status of the installed application program, and obtain the debugging result.

In the embodiment of this specification, based on the debugging instruction, the running status of the installed application program is debugged, including:

Determine the debugging code based on the debugging instruction;

Run the debug code to debug the operation of the installed application.

Refer to the description of the debugging code in step 304 above. If on the server side, the debugging instruction is determined based on the debugging code, then on the target client side, the debugging code can be determined based on the debugging instruction. The debugging code can be the It is obtained by inserting the patch code into the source code of .

Preferably, based on the debugging instruction, the running condition of the installed application program is debugged, which may also include:

Determine the debug file based on the debug command;

The debugging file is loaded to determine the debugging code based on the debugging file, and run the debugging code to debug the operation of the installed application program.

Refer to the description of the debugging file in step 304 above. If the debugging instruction is obtained based on the debugging file on the server side, the target client can determine the debugging file based on the debugging instruction, and when loading the debugging file, make the corresponding The patch code is inserted into the source code corresponding to the debug object to obtain the debug code. When the application program is running the corresponding source code, run the patch code, so as to debug the operation of the application program.

Preferably, the debugging code is run to debug the operation of the installed application program, including:

If the debugging code includes the first breakpoint identification and the second breakpoint identification, when the first breakpoint identification is read, the trigger starts to collect the debugging results; when the second breakpoint identification is read, the trigger Stop collecting debugging results.

When starting to debug the debug object based on the first breakpoint identifier, the input parameter data of the debug object is obtained. When the debugging of the debug object ends based on the second breakpoint identifier, output parameter data of the debug object is obtained. Afterwards, the obtained debugging result includes the input parameter data and output parameter data.

Preferably, running the debugging code may also include:

Judging the switch state of the debugging result sending switch in the debugging code;

If the switch state is on, the collected adjustment result is sent to the server.

Preferably, running the debugging code may also include:

A debugging process is started, and the debugging code is run through the debugging process.

Referring to the above step 304 about the instruction to start the debugging process, if the debugging code includes the instruction to start the debugging process, the terminal device where the target client is located starts the debugging process for the debugger based on the instruction to start the debugging process.

The timing of starting the debugging process for the debug object is determined based on the debugging process starting instruction, including:

When the debuggee starts, determine the debug process start command;

The debugging process is started based on the determined debugging process starting instruction.

In the embodiment of this specification, the debugging method also includes:

If the debugging instruction is an encrypted instruction, the debugging instruction is decrypted and verified;

If the decryption result is passed, then based on the decrypted debugging instruction, the running status of the installed application program is debugged to obtain a debugging result.

Wherein, the debugging result includes, but is not limited to, one or more of user behavior data during the running of the application program and running data of the application program.

Step 405: Send the debugging result to the server, so that the server analyzes whether the application program is abnormal according to the debugging result.

The debugging method of the application program described in the above-mentioned embodiments of this manual occurs in the debugging phase III (refer to FIG. 2 ), and the target client can reproduce the problem event that occurs during the running process, and returns the debugging result to the server based on the debugging command. Realize the purpose of being remotely debugged.

FIG. 5 is a structural diagram of a debugging device for an application program provided by an embodiment of this specification. The debugging device includes:

Determining module 51, determining the debugging instruction;

The sending module 52 sends the debugging instruction to the target client, so that the target client can debug the operation of the installed application program according to the debugging instruction, and obtain the debugging result;

The receiving module 53 receives the debugging result sent by the target client, and analyzes whether the application program is abnormal based on the debugging result.

Optionally, the determining module 51 determines debugging instructions, including:

Determining the problem event corresponding to the target client;

Generate debug instructions corresponding to problem events.

Optionally, the sending module 52 sends the debugging instructions to the target client, including:

determine the user identity and/or device identity of the target client;

Send the debugging instruction to the target client corresponding to the user ID and/or device ID.

Optionally, the determining module 51 determines debugging instructions, including:

Determine the debugging object and the debugging code corresponding to the debugging object;

Based on the debug code, a debug instruction is generated.

Optionally, the determining module 51 generates debugging instructions based on the debugging code, including:

Process the debug code to get the debug file;

Generate debug instructions based on a debug file.

Optionally, the determination module 51 processes the debug code to obtain a debug file, including:

Encapsulate the debug code into an object file;

Compare the difference between the source file and the target file corresponding to the debugging object, and obtain the debugging file based on the difference.

Optionally, the determining module 51 determines the debugging code corresponding to the debugging object, including:

Determine the source code corresponding to the debugging object;

Edit the first breakpoint identifier and the second breakpoint identifier in the source code, and execute the compilation operation on the edited source code to obtain the debug code corresponding to the debug object;

Wherein, the first breakpoint identifier is used to represent the start of debugging, and the second breakpoint identifier is used to represent the end of debugging.

Optionally, before performing the compiling operation on the edited source code, the determination module 51 edits the debugging result sending switch in the source code;

Wherein, the switch state of the debugging result sending switch is used to determine whether to send the debugging result to the server.

Optionally, before the compilation operation is performed on the edited source code, the determination module 51 edits the debugging process start instruction in the source code;

Wherein, the instruction for starting the debugging process is used to instruct the terminal device to start the debugging process for the debugging object.

Optionally, the debugging equipment also includes:

The encryption module 54 is configured to encrypt the debugging instructions.

It should be noted that the control device of the application program described in the embodiments of this specification can be realized by software or by hardware, which is not specifically limited here.

Using the control device of the application program described in this manual, the target client can be effectively remotely controlled.

Based on the same inventive concept, the embodiment of this specification also provides an application control device, including at least one processor and a memory, the memory stores a program, and is configured to perform the following steps by at least one processor:

Determine the debugging instructions;

Send the debugging instruction to the target client, so that the target client can debug the operation of the installed application program according to the debugging instruction, and obtain the debugging result;

Receive the debugging result sent by the target client, and analyze whether the application is abnormal based on the debugging result.

For other functions of the processor, reference may also be made to the contents recorded in the foregoing embodiments, and details will not be repeated here.

Based on the same inventive concept, the embodiment of this specification also provides a computer-readable storage medium, the computer-readable storage medium includes a program used in combination with an electronic device, and the program can be executed by a processor to complete the following steps:

Determine the debugging instructions;

Send the debugging instruction to the target client, so that the target client can debug the operation of the installed application program according to the debugging instruction, and obtain the debugging result;

Receive the debugging result sent by the target client, and analyze whether the application is abnormal based on the debugging result.

For other functions of the processor, reference may also be made to the contents recorded in the foregoing embodiments, and details will not be repeated here.

FIG. 6 is a structural diagram of a debugging device for an application program provided by an embodiment of this specification. The debugging device includes:

The receiving module 61 receives the debugging instruction sent by the server;

The debugging module 62, based on the debugging instruction, debugs the running situation of the installed application program, and obtains the debugging result;

The sending module 63 sends the debugging result to the server, so that the server analyzes whether the application program is abnormal according to the debugging result.

Optionally, the debugging equipment also includes:

Determining module 64, before receiving the debugging instruction sent by the server, determining the problem event;

Sending module 63, sending the problem event to the server.

Optionally, the sending module 63 sends the problem event carrying the user ID and/or device ID to the server, so that the server returns a debugging instruction based on the user ID and/or device ID.

Optionally, the debugging module 62, based on the debugging instruction, debugs the operation of the installed application program, including:

Determine the debugging code based on the debugging instruction;

Run the debug code to debug the operation of the installed application.

Optionally, the debugging module 62, based on the debugging instruction, debugs the operation of the installed application program, including:

Determine the debug file based on the debug command;

The debug file is loaded to determine the debug code based on the debug file and run the debug code to debug the operation of the installed application program.

Optionally, the debugging module 62 runs debugging codes to debug the operation of the installed application program, including:

If the debugging code contains the first breakpoint identifier and the second breakpoint identifier, when the first breakpoint identifier is read, the trigger starts to collect the debugging results; when the second breakpoint identifier is read, the trigger stops the collection Debug results.

Optionally, the debugging module 62, running the debugging code, also includes:

Judging the switch state of the debugging result sending switch in the debugging code;

If the switch state is on, the collected adjustment result is sent to the server.

Optionally, the debugging module 62, running the debugging code, includes:

Start the debugging process and run the debugging code through the debugging process.

Optionally, the debugging module 62 debugs the running conditions of the installed application programs to obtain the debugging results, including:

Decrypt and verify the encrypted debugging instructions;

If the decryption result is passed, then based on the decrypted debugging instruction, the running status of the installed application program is debugged to obtain a debugging result.

It should be noted that the control device of the application program described in the embodiments of this specification can be realized by software or by hardware, which is not specifically limited here.

Using the application program debugging device described in the embodiments of this specification, the debugging result after debugging the installed application program can be fed back to the server, so that the server can remotely debug the target client.

Based on the same inventive concept, the embodiment of this specification also provides an application control device, including at least one processor and a memory, the memory stores a program, and is configured to perform the following steps by at least one processor:

Receive debugging instructions sent by the server;

Based on the debugging instruction, debug the running status of the installed application program, and obtain the debugging result;

Send the debugging result to the server, so that the server analyzes whether there is an exception in the application program according to the debugging result.

For other functions of the processor, reference may also be made to the contents recorded in the foregoing embodiments, and details will not be repeated here.

Based on the same inventive concept, the embodiment of this specification also provides a computer-readable storage medium, the computer-readable storage medium includes a program used in combination with an electronic device, and the program can be executed by a processor to complete the following steps:

Receive debugging instructions sent by the server;

Based on the debugging instruction, debug the running status of the installed application program, and obtain the debugging result;

Send the debugging result to the server, so that the server analyzes whether there is an exception in the application program according to the debugging result.

For other functions of the processor, reference may also be made to the contents recorded in the foregoing embodiments, and details will not be repeated here.

In the 1990s, the improvement of a technology can be clearly distinguished as an improvement in hardware (for example, improvements in circuit structures such as diodes, transistors, and switches) or improvements in software (improvement in method flow). However, with the development of technology, the improvement of many current method flows can be regarded as the direct improvement of the hardware circuit structure. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (Programmable Logic Device, PLD) (such as a Field Programmable Gate Array (Field Programmable Gate Array, FPGA)) is such an integrated circuit, and its logic function is determined by programming the device by a user. It is programmed by the designer to "integrate" a digital system on a PLD, instead of asking a chip manufacturer to design and make a dedicated integrated circuit chip. Moreover, nowadays, instead of making integrated circuit chips by hand, this kind of programming is mostly realized by "logic compiler (logic compiler)" software, which is similar to the software compiler used when writing programs. The original code of the computer must also be written in a specific programming language, which is called a hardware description language (Hardware Description Language, HDL), and there is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language) , AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., currently the most commonly used is VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. It should also be clear to those skilled in the art that only a little logical programming of the method flow in the above-mentioned hardware description languages and programming into an integrated circuit can easily obtain a hardware circuit for realizing the logic method flow.

The controller may be implemented in any suitable way, for example the controller may take the form of a microprocessor or processor and a computer readable medium storing computer readable program code (such as software or firmware) executable by the (micro)processor , logic gates, switches, Application Specific Integrated Circuit (ASIC), programmable logic controllers, and embedded microcontrollers, examples of controllers include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the memory's control logic. Those skilled in the art also know that, in addition to realizing the controller in a purely computer-readable program code mode, it is entirely possible to make the controller use logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded The same function can be realized in the form of a microcontroller or the like. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as structures within the hardware component. Or even, means for realizing various functions can be regarded as a structure within both a software module realizing a method and a hardware component.

The systems, devices, modules, or units described in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementing device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or Combinations of any of these devices.

For the convenience of description, when describing the above devices, functions are divided into various units and described separately. Of course, when implementing the present application, the functions of each unit can be implemented in one or more pieces of software and/or hardware.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Accordingly, the present invention can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

Memory may include non-permanent storage in computer readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read only memory (ROM) or flash RAM. Memory is an example of computer readable media.

Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information. Information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cartridge, tape magnetic disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.

It should also be noted that the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus comprising a set of elements includes not only those elements, but also includes Other elements not expressly listed, or elements inherent in the process, method, commodity, or apparatus are also included. Without further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article or apparatus comprising said element.

This application may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The application may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including storage devices.

Each embodiment in this specification is described in a progressive manner, the same and similar parts of each embodiment can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and for relevant parts, refer to part of the description of the method embodiment.

The above descriptions are only examples of the present application, and are not intended to limit the present application. For those skilled in the art, various modifications and changes may occur in this application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.

Claims (20)

1. a kind of adjustment method of application program, including：

Determine debugging instruction；

The debugging instruction is sent to destination client, makes the destination client according to the debugging instruction to mounted The running situation of application program is debugged, and obtains debugging result；

The debugging result that the destination client is sent is received, and analyze the application program based on the debugging result to be It is no exception to be present.

2. adjustment method as claimed in claim 1, the determination debugging instruction, including：

It is determined that problem incident corresponding with the destination client；

The generation debugging instruction corresponding with described problem event.

3. adjustment method as claimed in claim 1, debugging instruction is determined, including：

Determine debugging code corresponding to debugger object and the debugger object；

The debugging code is handled, obtains debugging file；

The debugging instruction is generated based on the debugging file.

4. adjustment method as claimed in claim 3, handling the debugging code, debugging file is obtained, including：

The debugging code is encapsulated into file destination；

Compare the difference between source file and the file destination corresponding to the debugger object, and be based on the difference, obtain Debugging file.

5. the adjustment method as described in claim 3 or 4, debugging code corresponding to the debugger object is determined, including：

Determine source code corresponding to the debugger object；

The first breakpoint mark and the second breakpoint mark are edited in the source code, and volume is performed to the source code after editor Operation is translated, obtains debugging code corresponding to the debugger object；

Wherein, first breakpoint identifies starts for characterizing debugging, and second breakpoint identifies to be terminated for characterizing debugging.

6. adjustment method as claimed in claim 5, before the source code after to editor performs compilation operations, the tune Method for testing also includes：

Debugging result is edited in the source code and sends switch；

Wherein, the debugging result sends the on off state switched and is used to determine whether the debugging result sending server.

7. adjustment method as claimed in claim 5, before the source code after to editor performs compilation operations, the tune Method for testing also includes：

Debugging process open command is edited in the source code；

Wherein, the debugging process open command is used for instruction terminal equipment for debugger object unlatching debugging process.

8. adjustment method as claimed in claim 1, sent by the debugging instruction to before destination client, the debugging Method also includes：

The debugging instruction is encrypted.

9. user's row in application program running is included adjustment method as claimed in claim 1, in the debugging result For the one or more in the service data of data and the application program.

10. a kind of adjustment method of application program, including：

The debugging instruction that the reception server is sent；

Based on the debugging instruction, the running situation of mounted application program is debugged, obtains debugging result；

The debugging result is sent to the server, server is analyzed the application program according to the debugging result is It is no exception to be present.

11. adjustment method as claimed in claim 10, before the debugging instruction that the reception server is sent, the adjustment method Also include：

Determine problem incident；

Described problem event is sent to server.

12. adjustment method as claimed in claim 10, based on the debugging instruction, the operation feelings to mounted application program Condition is debugged, including：

Based on the debugging instruction, debugging code is determined；

The debugging code is run, the running situation of mounted application program is debugged.

13. adjustment method as claimed in claim 10, based on the debugging instruction, the operation feelings to mounted application program Condition is debugged, in addition to：

Based on the debugging instruction, debugging file is determined；

The debugging file is loaded, to determine debugging code based on the debugging file, and the debugging code is run, to having pacified The running situation of the application program of dress is debugged.

14. the adjustment method as described in claim 12 or 13, the debugging code is run, including：

If the debugging code includes the first breakpoint mark and the second breakpoint mark, the first breakpoint mark is being read When, triggering starts to gather the debugging result；In the case where reading the second breakpoint mark, triggering stops described in collection Debugging result.

15. the adjustment method as described in claim 12 or 13, the debugging code is run, including：

Judge that the debugging result in the debugging code sends the on off state of switch；

If the on off state is opening, the regulation result collected is sent to the server.

16. the adjustment method as described in claim 12 or 13, the debugging code is run, including：

Start-up and Adjustment process, the debugging code is run by the debugging process.

17. a kind of commissioning device of application program, including：

Determining module, determine debugging instruction；

Sending module, the debugging instruction is sent to destination client, makes the destination client according to the debugging instruction The running situation of mounted application program is debugged, obtains debugging result；

Receiving module, the debugging result that the destination client is sent is received, and based on described in debugging result analysis Application program is with the presence or absence of abnormal.

18. a kind of commissioning device of application program, including：

Receiving module, the debugging instruction that the reception server is sent；

Debugging module, based on the debugging instruction, the running situation of mounted application program is debugged, obtain debugging knot Fruit；

Sending module, the debugging result is sent to the server, makes server according to debugging result analysis Application program is with the presence or absence of abnormal.

19. a kind of commissioning device of application program, including at least one processor and memory, the memory storage have journey Sequence, and be configured to by least one computing device following steps：

Determine debugging instruction；

The debugging instruction is sent to destination client, makes the destination client according to the debugging instruction to mounted The running situation of application program is debugged, and obtains debugging result；

The debugging result that the destination client is sent is received, and analyze the application program based on the debugging result to be It is no exception to be present.

20. a kind of commissioning device of application program, including at least one processor and memory, the memory storage have journey Sequence, and be configured to by least one computing device following steps：

The debugging instruction that the reception server is sent；

Based on the debugging instruction, the running situation of mounted application program is debugged, obtains debugging result；

The debugging result is sent to the server, server is analyzed the application program according to the debugging result is It is no exception to be present.