JPH0269837A - Program debug support device - Google Patents

Abstract

PURPOSE:To efficiently debug a program by operating a program execution supervisory means by means of giving an execution supervisory condition and then, operating a program execution tracing means by means of giving an execution tracing condition. CONSTITUTION:The program execution supervisory means 2 executes an object program and stores input output data of respective execution steps within a range shown by the execution supervisory condition inputted from an input means 7 and execution data including the name of a step and the row number of the corresponding source program in a program execution supervisory data file 50. The program execution tracing means 3 outputs respective execution data on the forward direction or the opposite direction of execution from an execution tracing start position shown by the execution tracing condition inputted from an input means 7, and the content of the step of the source program corresponding to execution data from an output means. Thus, the program can easily be debugged.

Description

[Detailed Description of the Invention] [Industrial Application Field] The present invention relates to a program debugging support device, and particularly to a program debugging support device that monitors the execution of a program to be debugged over a predetermined range and collects execution data related to program execution steps. By storing the execution data in a file and outputting the result of tracing the program execution in the execution order or in the reverse direction from a separately specified tracing start position based on the stored execution data, the program can be easily debugged. The present invention relates to a program debugging support device.

[Conventional technology]

Program debugging, which involves checking and correcting bugs in a newly created or newly modified source program, is generally done by executing an object program obtained by translating the source program and creating the program. If a result differs from what the user expected, the cause is investigated and the relevant part of the source program is corrected. Conventionally, as a device for supporting debugging of such a program, there is a device that outputs a paragraph name of a corresponding source program to a storage medium or a printing device during the execution process of an object program.

[Problem to be solved by the invention]

According to the conventional program debugging support device described above,
Although the execution order of the paragraphs of the source program can be known, the detailed execution status of the execution steps within each paragraph, such as the output results for the input of the execution steps, cannot be known. For this reason, if the execution result of a program is not what you expected, conventionally, in order to discover the execution step that is the cause, you manually recalculate all the execution steps while looking at the source program list. I was working on tracking the flow.

SUMMARY OF THE INVENTION An object of the present invention is to provide a program debugging support device that eliminates the need for such troublesome work and allows programs to be easily debugged.

[Means to solve the problem]

In order to achieve the above object, the program debugging support device of the present invention includes an object program file that stores an object program of a program to be debugged, and a source program file that stores a source program of the program to be debugged. ,
an input means for inputting execution monitoring conditions and execution tracing conditions, an output means for outputting execution tracing results, and each execution step within the range indicated by the execution monitoring conditions input from the input means by executing the object program. program execution monitoring means for storing execution data including input/output data, corresponding paragraph names and line numbers of the source program in a program execution monitoring data file; Each piece of execution data on the forward side or the backward side of execution from the execution tracing start position indicated by the execution tracing condition input from the means and the source corresponding to the execution data. and program execution tracking means for outputting the contents of the paragraphs of the program from the output means.

[Effect]

In the program debugging support device of the present invention, the object program file stores the object program of the program to be debugged, the source program file stores the source program of the program to be debugged, and the program execution monitoring means , executes the object program and monitors program execution to collect input/output data of each execution step within the range indicated by the execution monitoring conditions input from the input means, and execution data including the paragraph name and line number of the corresponding source program. The program execution tracking means stores data in a data file, and the program execution tracking means selects the execution data stored in the execution monitoring data file from the execution tracing result position 1 indicated by the execution tracing condition inputted from the input means to the forward direction of execution or Each piece of execution data on the backward side and the content of the paragraph of the source program corresponding to the execution data are outputted from the output means.

〔Example〕

Next, embodiments of the present invention will be described in detail with reference to the drawings.

FIG. 1 is a block diagram of an embodiment of a program debugging support device of the present invention. The program debugging support device of this embodiment includes a processing device 1 including a program execution monitoring device 2 and a program execution tracking device 3, and a storage medium in which an object program file 40 storing an object program of a program to be debugged is stored. 4, a storage medium 5 that stores a program execution monitoring data file 50 that stores execution data obtained by monitoring program execution, and a source program file 60 that stores a source program of a program to be debugged. The system includes a storage medium 6, an input device 7 for inputting execution monitoring conditions and execution tracking conditions, and a display device 8 for displaying execution tracking results.

The program execution monitoring device 2 executes the object program in the object program file 40, and includes input/output data of each execution step within the range indicated by the execution monitoring conditions input from the input device 7, and the paragraph name of the corresponding source program. This is a device that stores execution data including the information and line numbers in the program execution monitoring data file 50. Furthermore, the program execution tracking device 3 selects the input device 7 from among the execution data stored in the execution monitoring data file 50.
This is a device that displays on the display device 8 each execution data within the range indicated by the execution trace conditions inputted from the execution data and the contents of the paragraphs of the source program corresponding to the execution data.

FIG. 2 is a diagram showing an example of the contents of the program execution monitoring data file 50. This program execution monitoring data file 50 is the object program file 40.
program name of the object program stored in
Consisting of a record 500 that records information such as the version number, and a plurality of execution data groups 501-1 to 501-n that are a collection of records that record execution data obtained as a result of monitoring the execution of the object program. be done.

Each execution data group corresponds to one paragraph of the program to be debugged.

FIG. 3 shows execution data groups 501-1 to 501-n in FIG.
It is a figure which shows the example of the content of arbitrary one execution data group 501-i among them. The execution data group 501-i includes execution data 501-i-1 to 501, each of which is one record.
-1-m. Each execution data 501-i-1~
501-1m corresponds to one execution step of the object program of the debug target program, and paragraph 1 of the source program corresponding to the execution step
Line number, data input/output ID (for example, input with 0, output with l), data name (variable name), data length, data attribute (
Contains the value of input or output data.

FIG. 4 is a flowchart of processing by the program execution monitoring device 2, and FIG. 5 is a flowchart of processing by the program execution tracking device 3. The operation of this embodiment will be described below with reference to each figure.

When debugging the corresponding source program stored in the source program file 60 by executing the object program stored in the object program file 40, the user first uses the input device 7 to debug the corresponding source program stored in the source program file 60.
, the name of the program to be debugged, the execution monitoring start condition that indicates what conditions are met to start execution monitoring, and the conditions that indicate what conditions are met to end execution monitoring. The program execution monitoring device 2 is started by inputting an execution monitoring command including execution monitoring termination conditions and the like.

As shown in FIG. 4, the activated program execution monitoring device 2 first takes in the input execution monitoring command (step 41), and stores the execution monitoring start condition and execution monitoring end condition in its internal memory. (steps 42 and 43), and then reads the corresponding object program from the object program file 40 according to the name of the program to be debugged indicated by the execution monitoring command and starts it (step 44).
.

Then, by executing steps 45 to 49 as follows, input/output data of each execution step included in the range of execution monitoring conditions specified by the execution monitoring command,
Execution data including paragraph names, line numbers, etc. of the corresponding source program are sequentially stored in the program execution monitoring data file 50 as one record.

First, the program execution monitoring device 2 performs the following operations every time the started object program executes one execution step.
Execution data related to the execution step is fetched (step 45). The execution data to be imported here is the value, attribute, data length, data name, input/output ID of the data input or output in the execution step, the paragraph name and line number of the source program corresponding to the execution step. . Next, by checking whether the execution monitoring start condition stored in the internal storage area matches the value of the corresponding item in the imported execution data, the location specified by the execution monitoring start condition is checked. It is determined whether the execution has been performed (step 46). If there is no failure, that is, if it is not the execution monitoring start point, the process returns to step 45 and the above-described operations are repeated.

Moreover, if - it is a failure, that is, if it is the execution monitoring start point, the execution data imported this time is recorded as the next record in the program execution monitoring data file 50 (step 47).
). Then, by checking whether the value of the corresponding item of the execution data imported this time matches the execution monitoring termination condition stored in the internal storage area, the execution of the part specified by the execution monitoring termination condition is executed. It is determined whether the execution has been executed or not (step 49). If they do not match, that is, if the execution monitoring is not finished, the process proceeds to step 148, where the object program executes the next execution step, and the execution data related to that execution step is stored. Import, step 47
The captured execution data is recorded in the program execution monitoring data file 50 as the next record. Also,
When it is determined in step 49 that the execution monitoring has ended, the process shown in FIG. 4 is ended. At this time, an end record indicating the end is recorded in the program execution monitoring data file 50.

By performing the above processing, each part included in the range from the part matching the execution monitoring start condition specified by the execution monitoring command to the part matching the execution monitoring end condition is added to the program execution monitoring data file 50. Execution data related to execution steps are recorded in the order of execution.

Now, after the execution of the program to be debugged has finished, the user can enter the name of the program to be traced, the conditions under which execution tracing should be started, that is, the execution tracing start position corresponding to the tracing start point. When an execution tracing command including a condition and a tracing direction designation specifying whether the program is executed in the order of execution or in the reverse direction is inputted from the input device 7, the program execution tracing device 3 is activated.
The process shown in FIG. 5 is started.

First, the program execution tracking device 3 takes in an execution tracking command input from the input device 7 (step 51),
The program execution monitoring data file 50 whose first record has the same name as the tracked program name included in the execution tracking command is searched and its first record, that is, record 500 is read (step 52).Next, in step 51, Set the tracking start position condition and tracking direction in the captured execution tracking command in the internal storage area (Step 53), program execution monitoring data file 5
Set record count 2 of 0 to "2°" (step 54). Then, read the record indicated by record count! of the program execution monitoring data file 50, and set the tracking start position set in the internal storage area in step 53. By checking whether the condition matches the corresponding item of the execution data included in the record, it is determined whether it is the tracking start position (step 56).

If they do not match, that is, if it is not the tracing start position, the record count l is incremented by 1, the process returns to step 55, the next record, that is, the execution data is read from the program execution monitoring data file 50, and it is determined in step 56 whether or not it is the tracing start position. do.

When the tracking start position is determined in step 56, a source program with the same name is found from the source program file 60 based on the tracked program name and the paragraph name included in the imported execution data, and the Reads the contents of the paragraph with the above paragraph name, that is, all source lines included in that paragraph (step 58
), this is displayed on, for example, the left side of the screen of the display device 8 (stellar screen 59). Note that information such as the version number is also recorded in the source program itself, so step 52
A comparison is made with the version number recorded in the record 500 read in, and if the source program is of a different version, it is treated as an error. Next, the currently captured execution data is displayed, for example, on the right side of the screen of the display device 8 (step 60). That is, when the tracking start position is reached, the execution data related to the tracking start position is displayed on the display device 8.
, and all source lines of the paragraph including the source line corresponding to the tracing start position are displayed on the display device 8.

Next, determine the tracking direction set in the internal storage area (step 61), and if the direction is forward, record count l is +IL (step 62), and if it is backward, record count l is incremented by -l (step 63). . Note that in this embodiment, if no tracking direction is specified, the process is terminated.

Next, according to the updated record count l, the next record is read from the program execution monitoring data file 50 (step 64), and the tracking direction is determined again (step 65). If the direction is forward, the record read this time is the program execution monitoring data file 50. It is determined whether or not it is an end record indicating the end of the data file 50 (step 66). If it is not an end record, the process proceeds to step 68, and if it is an end record, the process is terminated. Also, if the tracking direction is the opposite direction,
It is determined whether the record read this time is the first record of the program execution monitoring data file 50, that is, record 500. If it is not record 500, the process proceeds to step 6, and if it is record 500, the process is terminated.

In step 68, where control is transferred when the tracking direction is forward or backward and the record read this time is not the final record or record 500 but is a record containing execution data, Step 68)
If they are equal, the content of the corresponding paragraph of the source program has already been displayed on the display device 8, so the process advances to step 60 and the current execution data is displayed on the display device 8. If they are different, the process advances to step 58 and the content of the corresponding paragraph of the source program is displayed on the display device 8. The paragraph to be executed is read, the paragraph is displayed on the display device 8 in the next step 59, and the current execution data is displayed on the display device 8 in step 60.

By performing the above processing, the execution data from the tracing start position specified by the execution tracing command to the tracing direction specified by the execution tracing command and the contents of the paragraph of the corresponding source program are displayed on the display device 8. That will happen.

In the above embodiment, the program execution tracking device 3 extracts and displays the execution data and related paragraphs of the source program in the range from the execution tracking start position to the beginning or end of the program execution monitoring data file 50. A condition regarding the execution tracing end position may be included in the execution tracing command, and the tracing process may be terminated when the condition is satisfied.

〔Effect of the invention〕

As explained above, the program debugging support device of the present invention provides execution monitoring conditions to cause the program execution monitoring means to operate, and then provides execution tracing conditions to operate the program execution tracing means, so that the program debugging support device according to the present invention can be configured as indicated by the execution tracing conditions. the contents of the paragraphs of the source program contained within the range;
The input/output data for each execution step 1 Execution data including the paragraph name and line number is output from the output means, so the debugger can check which execution step in which paragraph of the source program by looking at the output contents. It becomes possible to easily recognize the program execution status, such as what input/output data was obtained and in what order steps were executed, and it becomes possible to debug the program efficiently.

[Brief explanation of the drawing]

FIG. 1 is a block diagram of an embodiment of the present invention, FIG. 2 is a diagram showing an example of the contents of a program execution monitoring data file, FIG. 3 is a diagram showing an example of the contents of an execution data group, and FIG. 4 is a diagram showing an example of the contents of an execution data group. FIG. 5 is a flowchart of an example of processing by the program execution monitoring device; FIG. 5 is a flowchart of an example of processing by the program execution tracking device. In the figure, l...Processing device 2...Program execution monitoring device 3...Program execution tracking device 4.5.6...Storage medium 7...Input device 8...Display device 40...・Object program file 50...
Program execution monitoring data file 60...source program file

Claims (1)

[Scope of Claims] An object program file that stores an object program of a program to be debugged, a source program file that stores a source program of the program to be debugged, and an input for inputting execution monitoring conditions and execution tracing conditions. means, an output means for outputting an execution trace result, executing the object program and input/output data of each execution step within a range indicated by the execution monitoring conditions input from the input means, and of the corresponding source program. program execution monitoring means for storing execution data including paragraph names and line numbers in a program execution monitoring data file; and a program execution monitoring means for storing execution data including paragraph names and line numbers in a program execution monitoring data file; Each piece of execution data on the side specified by the execution tracing condition from the execution tracing start position on the forward or backward side of execution and the contents of the paragraphs of the source program corresponding to the execution data are output from the output means. 1. A program debugging support device comprising: program execution tracing means for outputting program execution.