CN106294175A - A kind of program performs behavior method for visualizing and system - Google Patents

Abstract

The present application discloses a method for visualizing program execution behavior, including: using a program debugger to monitor the execution process of the program source code; if an execution event corresponding to a preset monitoring target occurs during the execution of the program source code, Then mark the code line corresponding to the execution event on the source code of the program; if the execution event is a fault event, analyze the stack trace information to obtain the corresponding fault cause, and then analyze the stack frame and stack trace information on the local terminal screen The message and the cause of the fault are displayed. The application allows software developers to intuitively know the causes of fault events without the need for software developers to manually analyze source codes to know the causes of faults. It can be seen that the present application reduces the manpower required in the debugging process of the program source code. In addition, the present application also correspondingly discloses a program execution behavior visualization system.

Description

Method and system for visualizing program execution behavior

technical field

The invention relates to the technical field of program code monitoring, in particular to a method and system for visualizing program execution behavior.

Background technique

At present, with the rapid development of computer technology, people can enjoy more and more convenient services brought by application software, and people's basic necessities of life are increasingly inseparable from the services provided by various application software.

When software developers develop application software, they need to frequently debug the execution process of the corresponding program source code. Only after ensuring that the program source code has sufficient reliability, the enterprise will put the corresponding application software into the market.

However, when debugging the execution process of the program source code, if a fault event occurs, the software developer cannot intuitively know the cause of the fault event, and the software developer needs to manually analyze the relevant code lines to determine corresponding fault type. For application software with more than 100,000 lines of codes at every turn, the above-mentioned debugging process undoubtedly requires a lot of manpower.

From the above, it can be seen that how to reduce the manpower required in the debugging process of the program source code is a problem to be solved at present.

Contents of the invention

In view of this, the object of the present invention is to provide a method and system for visualizing program execution behavior, which reduces the manpower required in the debugging process of program source codes. The specific plan is as follows:

A method for visualizing program execution behavior, comprising:

Use the program debugger to monitor the execution process of the program source code;

If it is monitored that an execution event corresponding to a preset monitoring target occurs during the execution of the program source code, the execution process of the program source code is suspended, and a mark corresponding to the execution event is marked on the program source code line of code; wherein, the preset monitoring target is a monitoring target set in advance on the program debugger;

If the execution event is a fault event, then use the program debugger to obtain the stack frame and stack trace information corresponding to the execution event, and analyze the stack trace information to obtain the corresponding fault cause, and then The stack frame, the stack trace information, and the cause of the failure are displayed on the screen of the local terminal.

Preferably, the program debugger is a GDB debugger.

Preferably, the preset monitoring target is a stack overflow event, a program interruption event or a memory access error event.

Preferably, the program interruption event is an interruption event caused by a line breakpoint, a function breakpoint, a conditional breakpoint or an event breakpoint.

Preferably, after the process of parsing the stack trace information to obtain the corresponding fault cause, it also includes:

determining a fault severity level corresponding to the execution event according to the fault cause;

If the fault severity level is greater than a preset level, the stack frame, the stack trace information and the fault cause are sent to a pre-designated target device terminal.

Preferably, the process of sending the stack frame, the stack trace information and the failure cause to a pre-specified target device terminal includes:

Taking a screenshot of the display area displaying the stack frame, the stack trace information and the cause of the failure on the local terminal screen to obtain corresponding screenshot information;

Send the screenshot information to the target device terminal.

Preferably, the method also includes:

Acquiring information fed back by the target device terminal after receiving the stack frame, the stack trace information, and the cause of the failure, and displaying the fed back information in real time on the screen of the local terminal.

The invention also discloses a program execution behavior visualization system, including:

The execution process monitoring module is used to monitor the execution process of the program source code by using the program debugger;

The execution process suspending module is used to suspend the execution process of the program source code when it is monitored that an execution event corresponding to a preset monitoring target occurs during the execution of the program source code; wherein, the preset monitoring target is A monitoring target pre-set on the program debugger;

a code marking module, configured to mark the code line corresponding to the execution event on the program source code;

An information acquisition module, configured to use the program debugger to obtain stack frames and stack trace information corresponding to the execution event when the execution event is a fault event;

An information parsing module, configured to parse the stack trace information to obtain corresponding fault causes;

The information display module is used to display the stack frame, the stack trace information and the fault cause on the local terminal screen.

Preferably, the system also includes:

A fault severity level determination module, configured to determine the fault severity level corresponding to the execution event according to the fault cause after the information analysis module obtains the fault cause;

An information sending module, configured to send the stack frame, the stack trace information, and the cause of the fault to a pre-designated target device terminal when the fault severity level is greater than a preset level.

Preferably, the information sending module includes:

A screenshot unit, configured to take a screenshot of the display area displaying the stack frame, the stack trace information, and the cause of the failure on the local terminal screen, to obtain corresponding screenshot information;

An information sending unit, configured to send the screenshot information to the target device terminal.

In the present invention, the program execution behavior visualization method includes: using a program debugger to monitor the execution process of the program source code; if it is monitored that an execution event corresponding to a preset monitoring target occurs during the execution of the program source code, then suspend The execution process of the program source code, and mark the code line corresponding to the execution event on the program source code; where the preset monitoring target is the monitoring target set in advance on the program debugger; if the execution event is a fault event, Use the program debugger to obtain the stack frame and stack trace information corresponding to the execution event, and analyze the stack trace information to obtain the corresponding fault cause, and then display the stack frame, stack trace information, and fault cause on the local terminal screen . It can be seen that in the present invention, when a specific execution event occurs during the execution of the program source code, the code line corresponding to the execution event will be identified, and when the above-mentioned specific execution event is a fault event, the code line will be identified. Analyze the stack trace information to obtain the corresponding fault cause, and finally display the stack frame, stack trace information, and fault cause corresponding to the above fault events on the local terminal screen, so that software developers can intuitively Know the cause of failure-like events without requiring software developers to manually analyze the source code to learn the cause of the failure. It can be seen that the present invention reduces the manpower required in the debugging process of the program source code.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present invention, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

FIG. 1 is a flow chart of a method for visualizing program execution behavior disclosed in an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of a program execution behavior visualization system disclosed in an embodiment of the present invention.

detailed description

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

The embodiment of the present invention discloses a method for visualizing program execution behavior, as shown in FIG. 1 , the method includes:

Step S11: Using a program debugger to monitor the execution process of the program source code.

It can be understood that the program debugger in this embodiment may be an existing program debugger in the prior art. For example, the program debugger in this embodiment may use the GDB debugger released by the GUN open source organization. Of course, the program debugger in this embodiment may also be a newly developed program debugger.

In addition, in this embodiment, the execution process of the program source code refers to the running process of the program source code when the program source code is debugged.

Step S12: If it is monitored that an execution event corresponding to a preset monitoring target occurs during the execution of the program source code, then suspend the execution process of the program source code, and mark the code line corresponding to the execution event on the program source code; , the preset monitoring target is the monitoring target set in advance on the program debugger.

It can be understood that the above-mentioned preset monitoring target may be a fault event, and of course, it may also be a non-fault event that needs attention.

Step S13: If the above-mentioned execution event is a fault event, use the program debugger to obtain the stack frame and stack trace information corresponding to the execution event, and analyze the stack trace information to obtain the corresponding fault cause, and then display the error on the local terminal screen Display stack frames, stack trace information, and fault causes.

In this embodiment, when the execution event corresponding to the above preset monitoring target is a fault event, the program debugger will be used to obtain the corresponding stack frame and stack trace information, and then the stack trace information will be parsed to obtain the corresponding cause of issue.

It can be seen that in the embodiment of the present invention, when a specific execution event occurs during the execution of the program source code, the code line corresponding to the execution event will be identified, and when the above-mentioned specific execution event is a fault event , the stack trace information will be analyzed to obtain the corresponding fault cause, and finally the stack frame, stack trace information and fault cause corresponding to the above fault events will be displayed on the local terminal screen, so that software developers can Intuitively learn the cause of failure events without requiring software developers to manually analyze the source code to learn the cause of the failure. It can be seen that the embodiment of the present invention reduces the manpower required in the debugging process of the program source code.

The embodiment of the present invention discloses a specific method for visualizing program execution behavior. Compared with the previous embodiment, this embodiment further explains and optimizes the technical solution. specific:

The preset monitoring target in the previous embodiment may specifically be a stack overflow event, a program interruption event or a memory access error event.

Wherein, the above-mentioned program interruption event is an interruption event caused by a line breakpoint, a function breakpoint, a conditional breakpoint or an event breakpoint. It can be understood that the above-mentioned line breakpoint refers to a breakpoint that suspends the execution of the program when the program source code executes to a specified line, and the above-mentioned function breakpoint refers to a breakpoint that stops when the program source code executes to the first line of code corresponding to the specified function. The breakpoint that suspends the execution of the program. The above-mentioned conditional breakpoint refers to the breakpoint that suspends the execution of the program if a specific condition is true during the execution of the program source code. The above-mentioned time breakpoint refers to that if a specific event occurs during the execution of the program source code. A breakpoint that suspends execution of code.

In step S13 of the previous embodiment, if the execution event corresponding to the aforementioned preset monitoring target is a fault event, the stack trace information is analyzed to obtain the corresponding fault cause. Among them, after analyzing the stack trace information to obtain the corresponding fault cause, it also includes:

According to the cause of the failure, determine the failure severity level corresponding to the above execution event, and if the failure severity level is greater than the preset level, send the stack frame, stack trace information and failure cause to the pre-designated target device terminal.

That is to say, when the fault level corresponding to the above-mentioned execution event is high, the corresponding stack frame, stack trace information and fault cause will be sent to the pre-designated target device terminal, which is beneficial to pool the wisdom of other software developers to jointly Solve the above fault events. It can be understood that the above-mentioned target device terminal may be a personal computer, or may be an intelligent mobile terminal or the like.

More specifically, the above-mentioned process of sending the stack frame, stack trace information and fault cause to the pre-specified target device terminal may include:

Take a screenshot of the display area displaying the stack frame, stack trace information and fault cause on the local terminal screen to obtain the corresponding screenshot information, and then send the screenshot information to the target device terminal.

That is to say, in this embodiment, the above stack frame, stack trace information, and fault cause may be sent to the target device terminal by way of screenshot.

Further, the method in this embodiment may also include: acquiring the information fed back by the target device terminal after receiving the stack frame, stack trace information and fault cause, and displaying the fed back information on the local terminal screen in real time.

Correspondingly, the embodiment of the present invention also discloses a program execution behavior visualization system, as shown in Figure 2, the system includes:

The execution process monitoring module 21 is used to monitor the execution process of the program source code by using a program debugger;

Execution process suspends module 22, is used for when the execution event corresponding to preset monitor target occurs during monitoring program source code, then suspends the execution process of program source code; Wherein, preset monitor target is in advance Monitoring objectives set on the above;

The code marking module 23 is used to mark the code line corresponding to the execution event on the program source code;

The information acquisition module 24 is used to obtain the stack frame and stack trace information corresponding to the execution event by using a program debugger when the above-mentioned execution event is a fault event;

The information analysis module 25 is used to analyze the stack trace information to obtain the corresponding fault cause;

The information display module 26 is configured to display stack frames, stack trace information and failure reasons on the local terminal screen.

For more detailed working processes of the above-mentioned modules, reference may be made to the corresponding content disclosed in the foregoing embodiments, which will not be repeated here.

It can be seen that in the embodiment of the present invention, when a specific execution event occurs during the execution of the program source code, the code line corresponding to the execution event will be identified, and when the above-mentioned specific execution event is a fault event , the stack trace information will be analyzed to obtain the corresponding fault cause, and finally the stack frame, stack trace information and fault cause corresponding to the above fault events will be displayed on the local terminal screen, so that software developers can Intuitively learn the cause of failure events without requiring software developers to manually analyze the source code to learn the cause of the failure. It can be seen that the embodiment of the present invention reduces the manpower required in the debugging process of the program source code.

Further, the system in this embodiment may also include a fault severity determination module and an information sending module; wherein,

The fault severity determination module is used to determine the fault severity level corresponding to the execution event according to the fault cause after the information analysis module obtains the fault cause;

The information sending module is used to send the stack frame, stack trace information and fault reason to a pre-designated target device terminal when the fault severity level is greater than the preset level.

Wherein, the above-mentioned information sending module may include a screenshot unit and an information sending unit; wherein,

A screen capture unit, configured to capture a screen of a display area displaying stack frames, stack trace information and failure causes on the local terminal screen, to obtain corresponding screen capture information;

The information sending unit is used for sending the screenshot information to the target device terminal.

Finally, it should also be noted that in this document, 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 not only includes those elements, but also other elements not expressly listed, or elements inherent in the process, method, article, or apparatus. 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.

The method and system for visualizing program execution behavior provided by the present invention are described above in detail. In this paper, specific examples are used to illustrate the principle and implementation of the present invention. The description of the above embodiments is only used to help understand the present invention. method and its core idea; at the same time, for those of ordinary skill in the art, according to the idea of the present invention, there will be changes in the specific implementation and scope of application. In summary, the content of this specification should not be understood as Limitations on the Invention.

Claims (10)

1. A method for visualizing program execution behavior, comprising: Use the program debugger to monitor the execution process of the program source code; If it is monitored that an execution event corresponding to a preset monitoring target occurs during the execution of the program source code, the execution process of the program source code is suspended, and a mark corresponding to the execution event is marked on the program source code line of code; wherein, the preset monitoring target is a monitoring target set in advance on the program debugger; If the execution event is a fault event, then use the program debugger to obtain the stack frame and stack trace information corresponding to the execution event, and analyze the stack trace information to obtain the corresponding fault cause, and then The stack frame, the stack trace information, and the cause of the failure are displayed on the screen of the local terminal. 2. The program execution behavior visualization method according to claim 1, wherein the program debugger is a GDB debugger. 3. The method for visualizing program execution behavior according to claim 2, wherein the preset monitoring target is a stack overflow event, a program interruption event or a memory access error event. 4. The method for visualizing program execution behavior according to claim 3, wherein the program interruption event is an interruption event caused by a line breakpoint, a function breakpoint, a conditional breakpoint or an event breakpoint. 5. The program execution behavior visualization method according to any one of claims 1 to 4, characterized in that, after the process of analyzing the stack trace information and obtaining the corresponding fault cause, it also includes: determining a fault severity level corresponding to the execution event according to the fault cause; If the fault severity level is greater than a preset level, the stack frame, the stack trace information and the fault cause are sent to a pre-designated target device terminal. 6. The program execution behavior visualization method according to claim 5, wherein the process of sending the stack frame, the stack trace information and the cause of the failure to a pre-designated target device terminal comprises: Taking a screenshot of the display area displaying the stack frame, the stack trace information and the cause of the failure on the local terminal screen to obtain corresponding screenshot information; Send the screenshot information to the target device terminal. 7. The program execution behavior visualization method according to claim 5, further comprising: Acquiring information fed back by the target device terminal after receiving the stack frame, the stack trace information, and the cause of the failure, and displaying the fed back information in real time on the screen of the local terminal. 8. A program execution behavior visualization system, comprising: The execution process monitoring module is used to monitor the execution process of the program source code by using the program debugger; The execution process suspending module is used to suspend the execution process of the program source code when it is monitored that an execution event corresponding to a preset monitoring target occurs during the execution of the program source code; wherein, the preset monitoring target is A monitoring target pre-set on the program debugger; a code marking module, configured to mark the code line corresponding to the execution event on the program source code; An information acquisition module, configured to use the program debugger to obtain stack frames and stack trace information corresponding to the execution event when the execution event is a fault event; An information parsing module, configured to parse the stack trace information to obtain corresponding fault causes; The information display module is used to display the stack frame, the stack trace information and the fault cause on the local terminal screen. 9. The program execution behavior visualization system according to claim 8, further comprising: A fault severity level determination module, configured to determine the fault severity level corresponding to the execution event according to the fault cause after the information analysis module obtains the fault cause; An information sending module, configured to send the stack frame, the stack trace information, and the cause of the fault to a pre-designated target device terminal when the fault severity level is greater than a preset level. 10. The program execution behavior visualization system according to claim 9, wherein the information sending module comprises: A screenshot unit, configured to take a screenshot of the display area displaying the stack frame, the stack trace information, and the cause of the failure on the local terminal screen, to obtain corresponding screenshot information; An information sending unit, configured to send the screenshot information to the target device terminal.