JPS6277657A - Collection system for execution history information of user program - Google Patents

Abstract

PURPOSE:To generate a flexible interruption program by including an interruption flag in an instruction. CONSTITUTION:A loading module for a user program stored in an auxiliary memory device 7 is loaded in a main memory device 8, the interruption flag 33 included in the instruction is set selectively in the generation of this loading module according to an execution history information collection instruction. Then if the interruption flag 33 in the instruction and an interruption permit register 6 are both set when the user program is executed, an interruption is initiated to save the contents of a specific register in the specific area of the main memory device 8. The saved contents of this register are collected and stored as execution history information and then the control is returned to a user program.

Description

DETAILED DESCRIPTION OF THE INVENTION Object of the Invention Industrial Application Field The present invention relates to an execution history information collection method used for debugging a user program executed in a computer system, and in particular, to a system for collecting execution history information on an instruction-by-instruction basis. This paper relates to a method for collecting execution history information that can be collected with great detail.

BACKGROUND OF THE INVENTION For user programs executed on conventional electronic computer systems, it is necessary to collect execution history information for purposes such as debugging.

Conventionally, the method for collecting such execution history information is
A method is known in which a source program is modified so that instructions for collecting execution history information are inserted at key points in the source program.

Another known method is to rewrite an instruction in an area where control is expected to be passed during program execution to an instruction for collecting history information, collect the history information, and then return to the original instruction.

Furthermore, as another method, a method is known in which a monitor program that captures and simulates instructions of a user program is linked together during link processing.

Problems to be Solved by the Invention Among the conventional methods mentioned above, in the method of changing the source program, it is necessary to perform recompilation processing to remove the instructions for collecting history information from the source program after debugging, which is time-consuming. There is a problem.

In addition, with the method of rewriting the original instructions to instructions for collecting history information, there is a problem that if control is not transferred to an area where control is predicted to be transferred due to a control disorder during program execution, important history information cannot be collected. There is.

Furthermore, in the method of linking a monitor program for simulation, re-linking processing is required to exclude it from linking targets after debugging is completed, which is a problem in that it is time-consuming.

Configuration of the Invention Means for Solving the Problems The execution history information collection method of the present invention which solves the problems of the prior art described above has an execution history information collection method that solves the above-mentioned problems of the prior art. At this time, the interrupt flag included in the instruction is selectively sent according to the execution history information collection instruction, and when the user program is executed, if the interrupt flag in the instruction and the interrupt enable register are both set, the interrupt is disabled. The content of the saved register is collected and saved as execution history information, and then control is returned to the user program.

Hereinafter, the operation of the present invention will be explained in detail together with examples.

Embodiment Referring to FIG. 1, an execution history information collection method according to an embodiment of the present invention includes a loading stage 1 of a load module of a user program, an execution stage 2 of a user program, and an execution history information collection method. Interrupt stage 3. A collection/printing stage 4 and a return stage 5, an interrupt permission register 6, an auxiliary storage device 7 in which a user program load module is stored, a main memory bag W8 into which the user program load module can be fully loaded, and a printout. It is composed of a device 9. -First of all, the user
A load module for the execution history information collection/printing program to be executed in the collection/printing stage 4 is stored in the auxiliary storage device 7.

Next, the user causes the loader to execute load step 1 illustrated in the flowchart of FIG. 2 in order to load the user program in the load module 7 into the main storage device 8.

When load phase 1 is started, first step 1
1, it is determined whether collection of execution history information is specified. If collection of execution history information is specified during a test run for debugging, etc., proceed to step 12.
At this point, the execution history information collection/printing program load module stored in the auxiliary storage device 7 is loaded into a predetermined area of the main storage device 8 . On the other hand, if collection of execution history information is not specified after debugging is completed, step 12 is skipped.

In the next step 13, the user program load module stored in the auxiliary storage device 7 is loaded into the main storage bag W8. In step 14, it is determined again whether collection of execution history information has been specified, and if this has been specified, then in step 15, the first instruction of the load module of the user program in the main storage device 7 is read out.

The instructions in the load module are composed of an operand address section 31, an instruction code 32, an interrupt flag 33, an index register specification section 34, and a pace register specification section 35, as illustrated in FIG. 3 for a one-operand instruction. There is.

In the next step 16, the interrupt flag 33 in the first instruction read from the main memory 8 is set on. In step 17, it is determined whether or not the last instruction in the user program has been read and the interrupt flag has been set. If it is not finished,
Returning to steps 15 and 16, the reading of the next instruction and the setting of the interrupt flag for that instruction are repeated. When it is determined in step 17 that the v1 inclusion flag for the last instruction in the user program has ended, the processing of load stage 1 ends.

Next, control is transferred to the usage program execution means 2 loaded into the main storage device 8, and the instructions in the usage program are sequentially read from the main storage device 8 and executed. Prior to execution of each instruction, the interrupt flag 33 in that instruction
Then, ON/OFF of the interrupt permission register 6 is checked.

This interrupt permission register 6 is installed exclusively for the processing of collecting execution history information, and is initially set to ON prior to the start of execution of the user program.

During execution after debugging, if either the interrupt flag 33 or the interrupt enable register 6 in the instruction is off, the next instruction is executed without going through the interrupt stage 3. On the other hand, if the interrupt flag 33 and the interrupt enable register 6 in the instruction are both on during debugging, etc., the interrupt stage 3, the collection/print stage 4, and the return stage 5 as shown in the flowchart of FIG. are executed in sequence.

When the first interrupt stage 3 is started, in step 21 the interrupt flag 33 in the instruction and the interrupt enable register 6 are
After being reset, in the next step 22, the contents of a predetermined register including a program counter in the central processing unit are saved to a predetermined area of the main storage device 8.

After this, control is passed to the collection/printing stage 4, which is executed according to the execution history information collection/printing program in the main memory 8. That is, in step 23, the contents of the predetermined register that have been saved are read out from the main storage device 8,
After being edited into a format specified by the user, it is output to the printout device 9 as execution history information.

Control then passes to a restore step 5, where in step 24 the contents of the registers saved in the main memory 8 are restored to the corresponding registers in the central processing unit. Subsequently, in step 25, the interrupt permission register 6 is set, and then in the final step 26, control is passed to the instruction that generated the interrupt in the user program and executed.

Above, we have illustrated a configuration in which interrupt flags are set for all instructions in a user program, but by limiting this to a specific group of instructions such as branch-related instructions, the collection range of execution history information can be made to an appropriate size. You can also narrow it down.

Further, instead of editing and outputting the execution history information to the printing device, it may be configured to temporarily store it as is in the main storage device and edit and output it after the execution of the user program is completed.

Alternatively, the assembler or compiler may be used instead of the loader to set the interrupt flag in the instruction.

Effects of the Invention As explained in detail above, the method of the present invention allows the collection of execution history information to be specified for each machine language instruction. However, it is possible to easily find the point where control has been disrupted based on the saved results of execution history information, link map information, and object module list.

Furthermore, after debugging is completed, by not specifying collection of execution history information at the loading stage, the debugged user program can be executed as is without recompiling or relinking the source program.

Note that if you have the assembler or compiler set the interrupt flag in the instruction word instead of the loader, you can simply initialize the interrupt enable register to OFF without having to recompile the debugged user program. It can be used as is.

In particular, by including an interrupt flag in the instruction, the user can easily set/reset this flag.
Furthermore, processing after an interrupt can be specified by software, providing flexibility. Another advantage is that interrupt programs can be created.

[Brief explanation of drawings]

FIG. 1 is an overall configuration diagram of an execution history information collection method according to an embodiment of the present invention, FIG. 2 is a flowchart showing the procedure of load stage 1 in FIG. 1, and FIG. 3 is an instruction format in the above embodiment. FIG. 4 is a conceptual diagram illustrating the case of a one-operand instruction. 3 is a flowchart showing the procedure of collection/printing stage 4 and return stage. 1. User program loading stage, 2. User program execution means, 3. Interruption stage, 4. Execution history information collection/printing stage, 5. Returning to user program stage, 6 ...Interrupt permission register, 7.. Auxiliary storage device, 8.. Main storage device, 9.. Print output device.

Claims (1)

[Claims] When loading a load module of a user program into the main storage device or when creating this load module, an interrupt flag included in an instruction is selectively set according to an execution history information collection instruction. When the user program loaded onto the main memory is executed, if both the interrupt flag and the interrupt enable register in the instruction are set, an interrupt is generated and a predetermined data is stored in a predetermined area on the main memory. A method for collecting execution history information of a user program, characterized in that the contents of the register are saved, the contents of the register saved by this interrupt are collected and saved as execution history information, and then control is returned to the user program.