JPH06250876A - Interactive debugging supporting system - Google Patents

Abstract

PURPOSE:To easily collect information at the time of debugging by visually displaying a source list with variable values in the case of displaying a source list at the time of program debugging. CONSTITUTION:A variable value table preparing part 10 for sampling a real variable at the time of executing variables in a program, a variable editing/ outputting part 11 for visually displaying correspondence between a source program 8 consisting of symbolic codes and a source program substituted by variable values and a variable value table 4 for storing the real variable of each line at the time of executing the program are connected to a debugging supporting part 6. A program to be tested is executed by the supporting part 6, real variable values are acquired and stored in the table 4 and a source list with variable values is visually displayed.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an interactive debug support system.

[0002]

2. Description of the Related Art Conventionally, a debug support system for debugging a program executes symbolic information, such as a program name, a variable name, a label, which is described in a source program when the program is executed and a loop or an exception condition or an error in the result occurs. ， Problem information of the program can be output by using the line number. In addition, the debug support system can visually display the corresponding source program line when tracing the execution of the program for each break point or exception occurrence point or for each sentence.

However, the visible display of the source list of the program and the visible display of the variable value at the time of execution of the variables defined in the program are treated as different functions and cannot be displayed simultaneously. Therefore, when tracking the change of the variable value, it took time and effort to acquire the failure information.

[0004]

In the above-mentioned conventional method, the variable value and its change are interrupted by executing the program at a specified line, and the value of the specified variable at that time is visually displayed or specified. The value of the variable can be inspected by always displaying it, but the change of the variable cannot be inspected because it is compared with the list of the source program for each line executed.

[0005]

SUMMARY OF THE INVENTION An object of the present invention is to register the values of variables used in each line of a program in a variable value table during execution of the program and output the source list of the program. Value from the variable value table, edit and compare the source list of the program with the source list in which the acquired variable value replaces the variable used in that source list, and display it in the same list. . Thereby, the trouble information can be acquired quickly and easily at the time of debugging, and the work can be performed efficiently.

Therefore, according to the present invention, a storage unit for storing a program to be tested, a debug support unit for executing the program and collecting debug information, and a debug command for the debug support unit are input to make the debug information visible. In an interactive debugging support system having a terminal device for displaying, a source program file storing a source program of the program, a debugging database storing debugging information including pointers of variables of the program, and a program execution time The variable value table creation unit that collects the value of the variable and stores the variable value table in the variable value table, the source program, and the source program in which the variable of the source program is replaced with the variable of the source program are visible. And a variable value edit output unit to be displayed. .

[0007]

Embodiments of the present invention will now be described with reference to the drawings.

Referring to FIG. 1 showing a configuration of an embodiment of the present invention, the interactive debug support system 1 stores a program section area 2 for storing a program section of a test target program to be executed and a data section thereof. A storage unit 5 having a data value area 3 and a variable value table 4 for storing the variable values at the time of execution of each line of the program, and executing the program, stopping at the specified line, collecting debug information, and responding to the specified line A debug support unit 6 for visually displaying source lines, a terminal device 7 for visually displaying a source list by inputting a debug instruction to the debug support unit 6, a source program file 8 of a program to be tested, and a source program compilation time. Sources the debug database 9 that contains the pointers of the obtained variables and the variable values of each line of the program being executed. Program files 8, the variable value table creating unit 10 taken from Debbakku database 9 and the data unit 3, replacing the value of a variable in the source program and its variables, and edit variable values editing unit 11 for visual display
And

Further, FIG. 2 showing the functional configuration of the variable value table creating section 10, FIG. 3 showing the functional configuration of the variable value editing section 11, and the variable values can be replaced by the source program and its variables represented by symbolic codes. The operation of this embodiment will be described with reference to FIG. 4 exemplifying a screen that is edited and visually displayed in comparison with the source program that is being used.

Referring to FIG. 2 showing the configuration of the variable value table creating section 10, the operation thereof will be described in detail. When the terminal device 7 instructs the debugging start of the program 2 to be tested, the debugging support section 6 The variable value table creation unit 10 is activated. The variable value creation control unit 22 of the variable value table creation unit 10 issues a command to the test target program to set the break points on all program lines.
To send. The debug support unit 6 executes the program, interrupts the execution of each line, and sends the interrupt address of the line to the variable value table creation control unit 22. Then, the variable value table creation control unit 22 converts the line number of the debug information of the program stored in the debug database 9 into the line number corresponding to the interruption address. The line number to be converted is the source list analysis unit 2
1, the source list analysis unit 21 acquires the contents of the line corresponding to the line number from the source program file 8, divides the line into words, and sends the words to the variable value table creation control unit 22. The variable value table creation control unit 22 sends the words to the variable value acquisition unit 23 one by one. The variable value acquisition unit 23 determines whether or not the word is a variable based on the debug information in the debug database 9. When the word is a variable, the variable value acquisition unit 23 calculates the address in which the value of the variable is stored based on the debug information, and acquires the value of the variable from the data area 3. The acquired variable value is sent to the variable value table creation control unit 22, and the variable value and line number are edited and registered in the variable value table.

Next, the operation of the variable value edit output unit 11 will be described with reference to FIG.
, The variable values stored in the variable value table 4 are acquired, the source list 8 of the program is edited, and the values of all the variables used in the program are edited in a list that can be compared and displayed visually. Perform valued source list edit process.

First, when the visual display of the source list with variables is instructed to the variable value edit output control unit 25 from the terminal device 7 through the debug support unit 6, the variable value edit output control unit 2
Reference numeral 5 sends line numbers sequentially designated from the beginning of the source program to the source list search unit 26 based on the line numbers of the source list included in the visual display instruction. The source list search unit 26 acquires the contents of the line corresponding to the line number from the source program file 8, and further acquires the value of the variable corresponding to the passed line number from the numerical value table 4. The content of the acquired line and the value of the variable are sent to the variable value edit output control unit 25. The variable value edit output control unit 25 sends the contents of the line to be sent and the value of the variable to the variable value replacement output unit 24. The variable value replacement output unit 24 edits the content of the line and the value of the variable and visually displays them on the terminal device 7.

Further, referring to FIG. 4 exemplifying the visual display screen of the source list with variable values output by the variable value substitution output unit 24, the line number 27 is the source line. The line numbered 28 with a right arrow is a source line in which a variable name is converted into a variable value. Taking line 001000 as an example, A (I) = 0 is the source line represented by the symbolic code. 5 (100) = 0 is the source line in which the variable name is converted into the variable value. "5" in the source line where the variable name is converted to the variable value is array variable A
It is a value of (100). Then, this value is a value before "0" is substituted. 100 represents the value of the variable I.

[0014]

As described above, according to the present invention, when the value of the variable used in each line of the program is saved in the variable value table during execution of the program and the source list of the program is output, the variable Debug information at the time of debugging by acquiring the value of the variable used in each line from the value table, editing the source list of the program and the values of all variables defined in the program in the same list, and displaying them visually Can be easily collected.

[Brief description of drawings]

FIG. 1 is a diagram showing a configuration of an embodiment of the present invention.

FIG. 2 is a diagram showing a configuration of a variable value table creation unit in FIG.

FIG. 3 is a diagram showing a configuration of a variable value edit output unit in FIG.

FIG. 4 is an example of a visible display screen of a source list with variable values.

[Explanation of symbols]

 1 Interactive Debug Support System 2 Program Part Area 3 Data Part Area 4 Variable Value Table 5 Storage Part 6 Debug Support Part 7 Terminal Device 8 Source Program File 9 Debug Database 10 Variable Value Table Creation Part 11 Variable Value Edit Output Part

Claims (1)

[Claims] 1. A storage device that stores a program to be tested, a debug support unit that executes the program and collects debug information, and a terminal device that inputs a debug command to the debug support unit and visually displays the debug information. In an interactive debugging support system having, a source program file storing a source program of the program, a debugging database storing debugging information including a pointer of a variable of the program, and a variable of the variable at the time of executing the program. A variable value table creation unit that collects values and stores them in a variable value table, the source program, and a variable value edit that visually displays the source program and the source program in which the values of the variables are replaced by the variables of the source program An interactive debugging support system that includes an output unit and Temu.