Method for acquiring debugging data of distributed application program

Abstract

The embodiment of the invention discloses a method for acquiring debugging data of a distributed application program. The method comprises the following steps: calling an information capturing interface at a position where debugging information needs to be captured in a to-be-debugged application program, and compiling and linking to obtain a reorganized to-be-debugged application program; configuring the reorganized to-be-debugged application program by utilizing the running container component, loading and starting the reorganized to-be-debugged application program by utilizing the running container component, and loading debugging information or debugging files of the reorganized to-be-debugged application program by utilizing the running container component; when the reorganized to-be-debugged application program runs to the position where debugging information needs to be captured, interruption is generated through the debugging anchor point assembly, the interruption is responded through the running container assembly, address information of the interruption is positioned through the debugger, all local variables and all global variables of the context of a current statement are obtained according to the address information to be coded, and the debugging information is obtained; the operation container assembly is used for outputting coded information; and after the interruption is ended, the running container component restores running.

Description

Technical Field

[0001] The present invention relates to the field of distributed application programs, and more specifically, to a method for acquiring debugging data of distributed application programs. Background Art

[0002] With the continuous advancement of science and technology, especially the rapid development of computer science and technology, computer software or systems have penetrated into every corner of society and become an indispensable and important part of the national economy, national defense and social daily life. In this process, computer applications have shown a trend of increasingly complex architecture, increasingly large system scale, and increasingly complex tasks, which has led to the increasing difficulty in capturing potential software vulnerabilities. The rate of software or system failures caused directly by software errors continues to increase, and software quality issues have become the focus of people's attention. Therefore, it is particularly important to improve the software reliability of computer software or systems.

[0003] The failure or error of software or system is different from that of hardware products. Software does not have mechanical wear and aging problems. If a failure occurs, it is without exception that there are hidden dangers in its design and development process. Therefore, in the early stage of software use, the failure rate is relatively large, but as time goes by and errors are corrected, the potential errors in the software are getting fewer and fewer. From the perspective of the entire product life cycle, after the stable period, its failure rate will remain at a low level for a long time, that is, the software will not be "broken". Defects are inherent attributes of objects, and software is no exception. The number of software errors is related to the personal ability of the programmer. Excellent members have an average of 1 to 2 errors per thousand lines of code; ordinary programmers have an average of 3 to 5 errors per thousand lines of code. Therefore, software debugging technology is the most direct way to improve software reliability.

[0004] Due to the distributed nature of distributed applications, there are certain limitations in the acquisition, collection and verification of debugging information, which increases the difficulty of the already complex debugging work. Distributed software has become a common software form. The development, debugging and even later software maintenance of distributed software all require strong means to support. Distributed software or systems, compared with traditional software, have their own characteristics, including but not limited to, software interaction depends on the network, that is, such software depends on the network environment to run, resulting in a relatively harsh debugging environment; software is not independent, that is, the software depends on other software to run collaboratively, resulting in a complex software debugging process; software interaction data is scattered, resulting in fragmented and incoherent analysis data. In addition, in the debugging of distributed software or systems, it is often the case that one person faces multiple computers at the same time. In general, the difficult scenario of "one person and multiple machines" can be solved through distributed collection and centralized verification methods. However, due to the limitations of the integrity of the collected information, it is difficult for centralized verification to grasp comprehensive debugging information and quickly draw analytical conclusions.

[0005] In summary, there is an urgent need to solve the problem of complete capture of debugging information during multi-node operation of distributed software, and to optimize the solution of distributed software debugging problems from the information acquisition end. Summary of the invention

[0006] The object of the present invention is to provide a method for acquiring debugging data of a distributed application program, so as to solve at least one of the problems existing in the prior art.

[0007] In order to achieve the above object, the present invention adopts the following technical solutions:

[0008] A first aspect of the present invention provides a method for acquiring debugging data of a distributed application program, comprising:

[0009] In the position where the debugging information needs to be captured in the application to be debugged, the capture information interface of the debugging anchor component is called, and the debugging anchor component is compiled and linked to obtain the application to be debugged;

[0010] Using the running container component to configure the running dependency environment, startup parameters and initialization files of the compiled application to be debugged, and using the running container component to load and start the compiled application to be debugged, and using the running container component to load the debugging information or debugging files of the compiled application to be debugged, and running the running container component and the compiled application to be debugged;

[0011] When the reorganized application to be debugged runs to the position where the debugging information needs to be captured, the debugging anchor component is used to generate an interrupt, and the running container component is used to respond to the interrupt, and the debugger of the reorganized application to be debugged is used to locate the address information of the interrupt, and the running container component is used to obtain all local variables and all global variables of the context of the current statement according to the address information, and the running container component is used to encode according to all local variables and all global variables, and the running container component is used to output the encoded information to the application for collecting debugging information and centralized verification;

[0012] After the interruption ends, the running container component resumes running and continues to execute the compiled application program to be debugged.

[0013] Optionally, the location where debugging information needs to be captured in the application to be debugged calls the capture information interface of the debugging anchor component, including:

[0014] The capture information interface provided by the user interface module of the debugging anchor component is called at the location where the debugging information needs to be captured in the application program to be debugged.

[0015] Optionally, the use of the running container component to configure the running dependency environment, startup parameters and initialization files of the compiled application to be debugged includes:

[0016] The application environment configuration module of the running container component is used to configure the running dependency environment, startup parameters and initialization files of the compiled application to be debugged.

[0017] Optionally, the using the running container component to load and start the compiled application to be debugged, and using the running container component to load the debugging information or debugging file of the compiled application to be debugged includes:

[0018] Using the anchor loading module of the running container component to load and start the compiled application to be debugged;

[0019] The debugging information or debugging file of the compiled application to be debugged is loaded by using the anchor loading module of the running container component.

[0020] Optionally, when the compiled application to be debugged runs to the position where the debugging information needs to be captured, the debugging anchor component is used to generate an interruption, including:

[0021] When the compiled application program to be debugged runs to the position where debugging information needs to be captured, an interrupt is generated by utilizing the interrupt management module of the debugging anchor component.

[0022] Optionally, the using the running container component to respond to the interruption, and using the debugger of the compiled application to be debugged to locate the address information of the interruption includes:

[0023] Responding to the interruption using an interruption response module of the running container component;

[0024] The interruption response module of the running container component is used to locate the address information of the interruption according to the debugger of the compiled application program to be debugged.

[0025] Optionally, the using the running container component to obtain all local variables and all global variables of the context of the current statement according to the address information includes:

[0026] The debugging information acquisition module of the running container component is used to acquire all local variables and all global variables of the context of the current statement according to the address information.

[0027] Optionally, the using the running container component to encode according to the all local variables and the all global variables includes:

[0028] The information encoding module of the running container component is used to perform encoding according to all the local variables and all the global variables.

[0029] Optionally, the using the running container component to output the encoded information to an application for collecting debugging information and centralized verification includes:

[0030] The encoded information is outputted to an application program for collecting debugging information and centralized verification by utilizing the information output module of the running container component.

[0031] Optionally, after the interruption ends, the running container component resumes running and continues to execute the compiled application to be debugged, including:

[0032] After the interruption is ended by the interruption response module of the running container component, the running container component resumes running and continues to execute the reorganized application program to be debugged.

[0033] The beneficial effects of the present invention are as follows:

[0034] The technical solution described in the present invention proposes a method for obtaining debugging data information of a single distributed node in a general debugging method of distributed collection and centralized verification; when multiple distributed software are running in collaboration, the method can effectively collect comprehensive debugging information, so that when users face the difficult debugging scenario of "one person and multiple machines", they can effectively concentrate the debugging information in one place and grasp the global information; the debugging data obtained by the method provides users with a diagnostic basis for analyzing errors such as behavioral errors, content errors, and logical interaction coupling errors; the method provides support for expressing the global distributed software interactive collaboration process to a certain extent through a reasonable anchor point layout, and provides a means for distributed overall debugging, optimization and analysis, and has broad application prospects. BRIEF DESCRIPTION OF THE DRAWINGS

[0035] The specific implementation modes of the present invention are further described in detail below in conjunction with the accompanying drawings.

[0036] Figure 1 A schematic diagram showing components of a method for acquiring debugging data of a distributed application program provided by an embodiment of the present invention.

[0037] Figure 2 A swim lane diagram showing a method for acquiring debugging data of a distributed application program provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0038] In order to explain the present invention more clearly, the present invention is further described below in conjunction with embodiments and drawings. Similar components in the drawings are represented by the same reference numerals. It should be understood by those skilled in the art that the content specifically described below is illustrative rather than restrictive, and the protection scope of the present invention should not be limited thereto.

[0039] Due to the distributed nature of distributed applications, there are certain limitations in the acquisition, collection and verification of debugging information, which increases the difficulty of the already complex debugging work. Distributed software has become a common software form. The development, debugging and even later software maintenance of distributed software all require strong means to support. Distributed software or systems, compared with traditional software, have their own characteristics, including but not limited to, software interaction depends on the network, that is, such software depends on the network environment to run, resulting in a relatively harsh debugging environment; software is not independent, that is, the software depends on other software to run collaboratively, resulting in a complex software debugging process; software interaction data is scattered, resulting in fragmented and incoherent analysis data. In addition, in the debugging of distributed software or systems, it is often the case that one person faces multiple computers at the same time. In general, the difficult scenario of "one person and multiple machines" can be solved through distributed collection and centralized verification methods. However, due to the limitations of the integrity of the collected information, it is difficult for centralized verification to grasp comprehensive debugging information and quickly draw analytical conclusions.

[0040] In summary, there is an urgent need to solve the problem of complete capture of debugging information during multi-node operation of distributed software, and to optimize the solution of distributed software debugging problems from the information acquisition end.

[0041] In view of this, an embodiment of the present invention provides a method for obtaining debugging data of a distributed application, comprising calling a capture information interface of a debugging anchor component at a position in the application to be debugged where debugging information needs to be captured, and compiling and linking the debugging anchor component to obtain a reorganized application to be debugged; configuring a running dependency environment, startup parameters, and initialization files of the reorganized application to be debugged by using a running container component, and loading and starting the reorganized application to be debugged by using the running container component, and loading debugging information or debugging files of the reorganized application to be debugged by using the running container component, and running the running container component and the reorganized application to be debugged; when the reorganized application to be debugged When the debugging application runs to the position where the debugging information needs to be captured, the debugging anchor component is used to generate an interrupt, and the running container component is used to respond to the interrupt, and the debugger of the reorganized application to be debugged is used to locate the address information of the interrupt, and the running container component is used to obtain all local variables and all global variables of the context of the current statement according to the address information, and the running container component is used to encode according to all local variables and all global variables, and the running container component is used to output the encoded information to the application that collects debugging information and centrally verifies; after the interruption ends, the running container component resumes running and continues to execute the reorganized application to be debugged.

[0042] In a specific example, Figure 1 As shown, the method includes two components, one is the running container component A; the other is the debugging anchor component B. This method relies on the two components to be completed together, that is, when this method is used, it must include a running container component and a debugging anchor component, and the running container component or the debugging anchor component cannot be missing;

[0043] Furthermore, the running container component is an independently running component, and its physical form is an independently running application, that is, the running of the running container component does not depend on other programs. Furthermore, the running container component is an independently running application, which is used to load the application to be debugged with the debugging anchor component by starting a process, and the debugging related properties can be set in the process options; the running container component manages the application to be debugged with the debugging anchor component. When the running container component is closed, the application to be debugged with the debugging anchor component exits;

[0044] Further, such as Figure 2 As shown, the running container component includes six modules: application environment configuration module 1, anchor loading module 2, interrupt response module 3, debugging information acquisition module 4, information encoding module 5 and information output module 6;

[0045] Furthermore, the application environment configuration module is used to configure the running dependency environment, startup parameters and initialization files of the application to be debugged, so as to ensure that the application to be debugged can be started and run normally; the anchor loading module has the startup loading function of the application with the debugging anchor component, that is, it can load and start the application to be debugged; the interrupt response module has an interrupt response framework and can process the interrupt request issued by the application with the anchor component; the debugging information acquisition module is used to obtain all local variables and all global variable information of the application under the current interrupt condition, including variable type, variable name and variable value; the information encoding module is used to encode the variable information obtained by the debugging information acquisition module, such as json and xml; the information output module is used to output the data output by the information encoding module, such as TCP and IP network data packet mode;

[0046] Furthermore, the debug anchor component is an embedded component, which is in the form of a runtime library in physical form. It needs to be embedded in the application to be debugged for use. The operation of this component depends on the application to be debugged, and the application to be debugged is responsible for loading and unloading. Furthermore, the debug anchor component is in the form of a dynamic link library. As a part of the application to be debugged, it is loaded into the computer memory along with the application to be debugged and runs along with the application to be debugged.

[0047] Further, such as Figure 2 As shown, the debug anchor component includes two modules: a user interface module 7 and an interrupt management module 8;

[0048] Furthermore, the user interface module is used to provide an application programming interface (API) for users, which is called when debugging information needs to be captured; the interrupt management module has the function of generating an interrupt. When the user calls the interface provided by the user interface module, a software interrupt is generated, which is captured by the running container component.

[0049] In a specific example, the application to be debugged (including the debugging anchor component) and the running container component are run on the same computer;

[0050] Furthermore, the operation process of the method includes four stages, namely, a debugging anchor point introduction process, a debugging operation process, a debugging information collection process and a debugging information output process.

[0051] In a specific example, the debugging anchor component and the running container component run on the same computer.

[0052] In a specific example, a running container component can manage one application to be debugged with a debugging anchor component or multiple applications to be debugged with debugging anchor components.

[0053] This embodiment proposes a method for obtaining debugging data information of a single distributed node in a general debugging method of distributed collection and centralized verification; when multiple distributed software are running in collaboration, this method can effectively collect comprehensive debugging information, so that when users face the difficult debugging scenario of "one person and multiple machines", they can effectively concentrate the debugging information in one place and grasp the global information; the debugging data obtained by this method provides users with a diagnostic basis for analyzing errors such as behavioral errors, content errors, and logical interaction coupling errors; through a reasonable anchor point layout, this method provides support for expressing the global distributed software interactive collaboration process to a certain extent, and provides a means for distributed overall debugging, optimization and analysis, and has broad application prospects.

[0054] In a possible implementation, calling the capture information interface of the debug anchor component at the location where debug information needs to be captured in the application to be debugged includes: calling the capture information interface provided by the user interface module of the debug anchor component at the location where debug information needs to be captured in the application to be debugged.

[0055] In a specific example, the debugging anchor point bringing process includes the user using the debugging anchor point component to call a related anchor point interface (API) of the debugging anchor point component at a code line where debugging information needs to be captured;

[0056] Furthermore, the user may use the relevant anchor point interface of the debugging anchor point component once or multiple times in the application to be debugged, that is, the user brings multiple anchor points into the application to be debugged;

[0057] Furthermore, after editing the anchor interface, the user compiles and links the debugging anchor component, so that the debugging anchor component becomes an integral part of the application to be debugged.

[0058] In a specific example, the user uses the relevant information acquisition interface provided by the user interface module 7 of the debugging anchor point component, namely the relevant anchor point interface, to supplement the interface call statement at the location where the debugging information needs to be captured;

[0059] Furthermore, the call statement of the debug information capture interface may be at one or more locations of the application to be debugged;

[0060] Furthermore, the application to be debugged is compiled and linked, so that the debugging anchor component becomes a part of the application to be debugged.

[0061] In a possible implementation, configuring the runtime dependency environment, startup parameters, and initialization files of the compiled application to be debugged by using the running container component includes: configuring the runtime dependency environment, startup parameters, and initialization files of the compiled application to be debugged by using the application environment configuration module of the running container component.

[0062] In a possible implementation, using the running container component to load and start the compiled application to be debugged, and using the running container component to load the debugging information or debugging file of the compiled application to be debugged includes: using the anchor loading module of the running container component to load and start the compiled application to be debugged; using the anchor loading module of the running container component to load the debugging information or debugging file of the compiled application to be debugged.

[0063] In a specific example, the debugging and running process includes the user using the running container component to configure the running dependency environment, startup parameters, and initialization files of the application to be debugged, and loading and starting the application to be debugged that has completed the debugging anchor point introduction process;

[0064] Furthermore, after the application to be debugged is started, the container component and the application to be debugged are run simultaneously.

[0065] In a specific example, the user uses the application environment configuration module 1 of the running container component to configure the running dependency environment, startup parameters, and initialization files of the application to be debugged;

[0066] Further, the anchor loading module 2 of the running container component is used to complete the loading and starting of the application to be debugged with the debugging anchor component, and load the debugging information or debugging file of the application;

[0067] Furthermore, the application to be debugged with the debugging anchor component runs sentence by sentence according to the program settings.

[0068] In a possible implementation, generating an interrupt using the debug anchor component when the reorganized application to be debugged runs to the location where debug information needs to be captured includes: generating an interrupt using the interrupt management module of the debug anchor component when the reorganized application to be debugged runs to the location where debug information needs to be captured.

[0069] In a possible implementation, the using the running container component to respond to the interruption and using the debugger of the reorganized application to be debugged to locate the address information of the interruption includes: using the interruption response module of the running container component to respond to the interruption; using the interruption response module of the running container component to locate the address information of the interruption according to the debugger of the reorganized application to be debugged.

[0070] In a possible implementation, the using the running container component to obtain all local variables and all global variables of the context of the current statement according to the address information includes: using the debugging information acquisition module of the running container component to obtain all local variables and all global variables of the context of the current statement according to the address information.

[0071] In a possible implementation manner, the using the execution container component to encode according to the all local variables and the all global variables includes: using an information encoding module of the execution container component to encode according to the all local variables and the all global variables.

[0072] In a possible implementation, the using the running container component to output the encoded information to an application for collecting debugging information and centralized verification includes: using an information output module of the running container component to output the encoded information to an application for collecting debugging information and centralized verification.

[0073] In a possible implementation, after ending the interruption, the running container component resumes running and continues to execute the reorganized application to be debugged, including: after ending the interruption by using the interrupt response module of the running container component, the running container component resumes running and continues to execute the reorganized application to be debugged.

[0074] In a specific example, the debugging information collection process includes when the application to be debugged runs to an anchor interface statement using a debugging anchor component, the anchor interface triggers a software interrupt;

[0075] Furthermore, the container component is run to obtain all local variables and all global variable information of the current statement context through a debugger, including variable types, variable names, and variable values;

[0076] Further, the container component is run to encode the above information for output;

[0077] Further, the container component is run to resume program operation and continue to execute subsequent statements of the application to be debugged.

[0078] In a specific example, when the relevant information acquisition interface provided by the user interface module 7 of the debug anchor component is run, the interrupt management module 8 of the debug anchor component generates an interrupt;

[0079] Further, the interruption is responded to by the interruption response module 3 of the running container component, and the address information of the statement module is located by the debugger of the programming language related to the application to be debugged;

[0080] Furthermore, the debugging information acquisition module 4 of the running container component acquires all local variables and all global variable information of the current statement context according to the address information, including variable types, variable names and variable values.

[0081] In a specific example, the debugging information output process includes running the container component to complete the debugging information input process;

[0082] Furthermore, the container component is run to encode all local variables and all global variable information obtained, including variable types, variable names, and variable values, into data such as json and xml.

[0083] Furthermore, the running container component can pass the encoded information to the application for collecting debugging information and centralized verification through TCP and IP data packets, files or other forms.

[0084] In a specific example, the information encoding module 5 of the running container component encodes all local variables and all global variable information, including variable types, variable names and variable values, into data encoding, such as json and xml;

[0085] Furthermore, the information output module 6 of the running container component outputs the encoded information, for example, by transmitting it to an application program for collecting debugging information and centralized verification via TCP and IP data packets, files or other forms.

[0086] In the description of the present invention, it should be noted that the terms "upper", "lower", etc. indicate positions or positional relationships based on the positions or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific position, be constructed and operated in a specific position, and therefore cannot be understood as a limitation on the present invention. Unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection, or it can be an indirect connection through an intermediate medium, or it can be a connection between the two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to the specific circumstances.

[0087] It should also be noted that, in the description of the present invention, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0088] Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the present invention, and are not limitations on the embodiments of the present invention. For those skilled in the art, other different forms of changes or modifications can be made based on the above description. It is impossible to list all the embodiments here. All obvious changes or modifications derived from the technical solution of the present invention are still within the protection scope of the present invention.

Claims

1. A method for acquiring debugging data of a distributed application, characterized in that: include In the position where the debugging information needs to be captured in the application to be debugged, the capture information interface of the debugging anchor component is called, and the debugging anchor component is compiled and linked to obtain the application to be debugged; Using the running container component to configure the running dependency environment, startup parameters and initialization files of the compiled application to be debugged, and using the running container component to load and start the compiled application to be debugged, and using the running container component to load the debugging information or debugging files of the compiled application to be debugged, and running the running container component and the compiled application to be debugged; When the reorganized application to be debugged runs to the position where the debugging information needs to be captured, the debugging anchor component is used to generate an interrupt, and the running container component is used to respond to the interrupt, and the debugger of the reorganized application to be debugged is used to locate the address information of the interrupt, and the running container component is used to obtain all local variables and all global variables of the context of the current statement according to the address information, and the running container component is used to encode according to all local variables and all global variables, and the running container component is used to output the encoded information to the application for collecting debugging information and centralized verification; After the interruption ends, the running container component resumes running and continues to execute the compiled application program to be debugged.

2. The method for obtaining debugging data of a distributed application according to claim 1, characterized in that: The capture information interface of the debugging anchor component is called at the location where the debugging information needs to be captured in the application to be debugged, including: The capture information interface provided by the user interface module of the debugging anchor component is called at the location where the debugging information needs to be captured in the application program to be debugged.

3. The method for obtaining debugging data of a distributed application according to claim 1, characterized in that: The configuration of the compiled application to be debugged using the running container component includes: The application environment configuration module of the running container component is used to configure the running dependency environment, startup parameters and initialization files of the compiled application to be debugged.

4. The method for obtaining debugging data of a distributed application according to claim 1, characterized in that: The using of the running container component to load and start the compiled application to be debugged, and using the running container component to load the debugging information or debugging file of the compiled application to be debugged includes: Using the anchor loading module of the running container component to load and start the compiled application to be debugged; The debugging information or debugging file of the compiled application to be debugged is loaded by using the anchor loading module of the running container component.

5. The method for obtaining debugging data of a distributed application according to claim 1, characterized in that: When the compiled application to be debugged runs to the position where the debugging information needs to be captured, the debugging anchor component is used to generate an interruption, which includes When the compiled application program to be debugged runs to the position where debugging information needs to be captured, an interrupt is generated by utilizing the interrupt management module of the debugging anchor component.

6. The method for acquiring debugging data of a distributed application according to claim 1, characterized in that: The using the running container component to respond to the interruption, and using the debugger of the compiled application to be debugged to locate the address information of the interruption includes: Responding to the interruption using an interruption response module of the running container component; The interruption response module of the running container component is used to locate the address information of the interruption according to the debugger of the compiled application program to be debugged.

7. The method for acquiring debugging data of a distributed application according to claim 1, characterized in that: The using the running container component to obtain all local variables and all global variables of the context of the current statement according to the address information includes: The debugging information acquisition module of the running container component is used to acquire all local variables and all global variables of the context of the current statement according to the address information.

8. The method for acquiring debugging data of a distributed application according to claim 1, characterized in that: The using the running container component to encode according to all the local variables and all the global variables includes The information encoding module of the running container component is used to perform encoding according to all the local variables and all the global variables.

9. The method for acquiring debugging data of a distributed application according to claim 1, characterized in that: The step of using the running container component to output the encoded information to an application program for collecting debugging information and centralized verification includes: The encoded information is outputted to an application program for collecting debugging information and centralized verification by utilizing the information output module of the running container component.

10. The method for acquiring debugging data of a distributed application according to claim 1, characterized in that: After the interruption ends, the running container component resumes running and continues to execute the compiled application to be debugged, including After the interruption is ended by the interruption response module of the running container component, the running container component resumes running and continues to execute the reorganized application program to be debugged.

Images