JPH034336A - Program debug processor - Google Patents

Abstract

PURPOSE:To prevent a working efficiency from lowering due to the input leakage of a debug command and an input miss by executing the input of the debug command described with a debug command language in the debug processing of a user program. CONSTITUTION:When an activation for executing the debug of the user program by using a debug command described with the debug command language by the user is executed, the user inputs the debug command from terminal equip ment 8. Whether a debut command name inputted from the equipment 8 is equal to the name of the debug command group stored in a debug command language storage file 7 or not is decided, and when they are not equal, the inputted debug command is executed. When the inputted debug command name is equal to the name of the debug command group stored in the file 7, the debug command group is read in from the file 7, a debug command analyzing part 5 analyzes the logic of the debug command language, it is converted to an executable debug command group, and a debug 2 performs the execution.

Description

DETAILED DESCRIPTION OF THE INVENTION [Industrial Application Field] The present invention is utilized for program debugging processing of an information processing system. The present invention relates to program debugging processing for debugging work that is routinely performed multiple times or debugging work that requires the input of a large number of debugging commands.

〔overview〕

The present invention stores debug commands written in a debug command language in a program debug processing device for an information processing system, reads the stored debug commands when the debug commands are input, analyzes the logic, and executes the debug commands. By converting and executing a set of possible debugging commands, it prevents a drop in efficiency due to operational errors and improves work efficiency.

[Conventional technology]

In a conventional program debugging process, a debug command input procedure is such that a user inputs a debug command with a syntax defined by a debugger from a terminal device in response to a debug command input opportunity.

[Problem that the invention seeks to solve]

In the above-mentioned conventional debugging command input procedure in program debugging, even if the same debugging command is input multiple times for multiple debugging tasks, the debugging command must be manually input each time the input trigger occurs. , omitted debug command input,
There is a possibility that input errors may occur during operations, such as input errors, and it may not be possible to perform the same debugging task each time.

In addition, with conventional technology, there is no way to define the logic of the debug command input procedure other than by the user himself/herself, so the debugging work depends on the behavior of the user program, where the content of the debug command to be executed differs depending on the data value. In this case, the user had to judge the content of the debug command to be input each time an opportunity to input a debug command occurred.

SUMMARY OF THE INVENTION The present invention is intended to solve these problems, and aims to provide an apparatus that can execute program debug processing by making it possible to define the logic of debug command input using a debug command language.

[Means for solving problems]

The present invention includes a main control unit, a terminal device, and a terminal device input that is connected to the main control unit and outputs execution results of debug commands to the terminal device and reads debug commands input from the terminal device. In a program debugging processing device that includes an output unit and a debugger that executes debugging commands input from the terminal device, a debugging command language that defines the logic of debugging command input work, and writing in the debugging command language. a debug command language input/output unit that provides a debug command language storage file that stores a debug command group for which logic of an input procedure is defined, and reads a debug command group written in the debug command language from the debug command language storage file; The present invention is characterized by comprising a debug command language analysis section that analyzes the logic of the loaded debug command language and converts it into a group of executable debug commands.

[Effect]

From the debug command language storage file that stores the debug command language that defines the logic of debug command input work and the debug command group that defines the logic of the input procedure by writing in the debug command language. The human output section reads a group of debug commands written in the debug command language,
The debug command language analysis unit analyzes the logic of the loaded debug command language, converts it into an executable debug command group, and executes the input debug commands.

This prevents deterioration in the efficiency of debugging work due to operational errors such as omissions in inputting debugging commands or input errors, and reduces the processing time for debugging command inputting work that is dependent on the user.

〔Example〕

Next, embodiments of the present invention will be described based on the drawings.

Fig. 1 is a block diagram showing the configuration of the embodiment of the present invention, Fig. 2 is a flowchart showing the flow of operation of the embodiment of the invention, and Fig. 3 is the logic of the debug command input procedure using the debug command language of the embodiment of the invention. It is a figure showing an example.

In the embodiment of the present invention, a main control unit 3 is connected to a terminal device 8 and this main control unit 3, and outputs the execution results of debug commands to the terminal device 8 and reads debug commands input from the terminal device 8. The present invention includes a terminal device input/output unit 4 that performs input/output operations, and a debugger 2 that executes debug commands input from the terminal device 8. Further, as a feature of the present invention, a debug command language that defines the logic of debug command input work, and A debug command language storage file 7 is provided that stores a group of debug commands that define the logic of an input procedure by being written in a debug command language.
A debug command language input/output unit 6 reads a debug command group written in a debug command language from a debug command language, and a debug command language analysis unit 5 analyzes the logic of the read debug command language and converts it into an executable debug command group. Be prepared.

The debug command language storage file 7 stores a group of debug commands written in the debug command language under any name specified by the user.

When a user inputs a debug command from the terminal device 8 when debugging a user program, the terminal device input/output section 4 reads the input debug command and passes control to the main control section 3.

The main control unit 3 compares the debug command name input to the terminal device 8 and the name of the debug command group stored in the debug command language storage file 7, and if they are not equal, the control is transferred to the debugger 2 and the debug command is is executed. 7 If the debug command name input from the terminal device 8 is equal to the name of a debug command group stored in the debug command original language storage file 7, control is passed to the debug command language input/output unit 6 and the debug command name input from the terminal device 8 is Loads a group of debug commands using the debug command name as a key.

The debug command language analysis unit 5 analyzes the logic of the read debug command language and converts it into a group of executable debug commands, and control is passed to the debugger 2 to execute the debug commands.

Next, with reference to FIG. 2, a description will be given of the flow of operations of the program debug processing device 1, which allows the logic of debug command input to be defined using the debug command language, at the time of debug command input and execution.

When the user starts debugging a user program using a group of debug commands written in a debug command language, the user inputs a debug command from the terminal device 8 (Al).

A2 to determine whether the debug command name input from the terminal device 8 is equal to the name of the debug command group stored in the debug command language storage file 7.
), if they are not equal, the debug command input from the terminal device 8 is executed (A5).

In addition, if the debug command name input from the terminal device 8 is equal to the name of a debug command group stored in the debug command language storage file 7, the debug command language storage file is created using the debug command name input from the terminal as a key. Load the debug command group from 7 (A3). The debug command analysis unit 5 analyzes the logic of the debug command language and converts it into a group of executable debug commands (A4), and the debugger 2 executes the debug commands (A5). After executing the debug command, it is determined whether or not a debug end command has been input. If it has not been input, the process returns to debug command input (A1), and if it has been input, the process ends.

Next, a method for describing the logic of a debug command input procedure using the debug command language will be described with reference to FIG.

It is possible to incorporate logic including branch instructions, loop instructions, etc. into the logic of the debug command input procedure written in the debug command language, so you can change the contents of the input debug command depending on the value of a certain variable, or change the contents of the input debug command depending on the value of a certain variable. It becomes possible to control logic by inputting debug commands multiple times.

A debug command group defined by the logic of the debug command input procedure shown in FIG. 3 is created with the name C0M-1, and a variable named @C0UNT is declared as a control variable. After the debug command group l is executed, the value of the variable DATAI used in the user program is obtained. If the value is 0, debug command group 2 is executed, if the value is 1, debug command group 3 is executed, and if the value is other than 0.1, debug command group 4 is executed. After execution of debug command group 5, a loop is generated using the variable @C0UNT declared by the debug command language as a control variable, and debug command group 6.7 is executed the number of times in the loop. However, after the debug command group 6 is executed, the value of the variable DATA2 used in the user program is obtained, and if the value is "XxX", control is transferred to the statement indicated by the label named LAB.

〔Effect of the invention〕

As explained above, according to the present invention, by making it possible to input debug commands written in a debug command language during debugging of a user program,
By preventing the deterioration of debugging efficiency due to operational errors such as omissions or input errors in debugging commands, improving the efficiency of debugging, and by making it possible to define the logic of resobug command input using the debugging command language. This has the effect of reducing the processing time for debug command input work, which was dependent on the user, and reducing the number of man-hours required for debugging work.

[Brief explanation of drawings]

FIG. 1 is a block diagram showing the configuration of an embodiment of the present invention. FIG. 2 is a flowchart showing the operation flow of the embodiment of the present invention. FIG. 3 is a diagram showing an example of the logic of a debug command input procedure using the debug command language according to the embodiment of the present invention. ■...Program debug processing device, 2...Debugger, 3...Main control unit, 4...Terminal device input/output unit, 5
. . . Debug command language analysis section, 6. Debugging command language input/output section, 7. Debugging command language storage file, 8. Terminal device.

Claims (1)

[Claims] 1. A main control unit, which is connected to a terminal device and the main control unit, and outputs execution results of debug commands to the terminal device and reads debug commands input from the terminal device. A debug command language that defines the logic of a debug command input operation in a program debug processing device that includes a terminal device input/output unit to perform debug commands and a debugger that executes debug commands input from the terminal device, and a debug command language that defines the logic of debug command input operations. A debug command language storage file is provided to store a group of debug commands that define the logic of the input procedure, and a debug command language input/output function is used to read the debug command group written in the debug command language from this debug command language storage file. What is claimed is: 1. A program debug processing device comprising: a debug command language analysis section that analyzes the logic of a loaded debug command language and converts it into a group of executable debug commands.