JPS58201152A - Automatic information acquition system - Google Patents

Abstract

PURPOSE:To investigate the cause of a fault easily, by storing all pieces of information necessary for an electronic computer to reexecute a program at specific intervals of time, and tracing the program by the stored pieces of information when the program ends abnormally. CONSTITUTION:The time interval at which information necessary for program reexecution is stored in a storage part 9 and compared with the output of a timer 8 to generates an interruption signal 12 at acquisition time, and a program information acuisition part 14 is activated to store all pieces of information necessary for the program reexecution in a file 15. This operation is repeated to the end of the program. If a fault of the program is detected by a detector 11, an interruption 12 is caused to start a trace program 16 with a program recovery function. A return from an abnormal end occurrence point to the closest information acquisition start point is made automatically and the pieces of information in the file 15 are recovered; and then the program is reexecuted and the operation of the program is traced to output necessary pieces of information automatically. Thus, the cause of the abnormal end is investigated easily.

Description

DETAILED DESCRIPTION OF THE INVENTION Object of the Invention According to the present invention, during program execution, information is automatically stored in a file after a certain period of time, and the information is automatically stored in a file at the location closest to the point where a program bug occurs.

The information taken at each point is automatically confirmed, and the result data is from the closest point to before the program error occurred.

is automatically traced and relates to automatic acquisition of information suitable for depacking.

Conventional technology In the past, if an abnormality occurred during program processing, the program had to be executed again from the beginning, which required turnaround time and job request man-hours, which required an extra hour. ■The operating system has a function called checkpoint restart, but this requires the setting of a checkpoint macro, which creates extra programming work for Pro Gamer.

■When an abnormality occurs, it is not possible to see the trajectory of the execution state before the abnormality occurred. Therefore, it took a lot of man-hours to investigate the cause.

Purpose of invention The object of the present invention is as described above.

This method eliminates the problems of the conventional method and is shown below.

■After the program passes the cheek point in Figure 1, all the information necessary for re-execution is automatically obtained.

be stored in the program information file.

■If the program in Figure 1 terminates abnormally, ■.

The purpose of this is to add the information necessary to trace the program's operations to the information stored in , and make it re-executable.

The debugging process is part of the program development process.

Since it takes about half of the entire process,
Measures must be taken to shorten the program development period.

Therefore, we have focused on the debugging process to see if it is possible to automatically obtain depacking information for bug occurrences and shorten the program processing re-execution time.

EMBODIMENTS OF THE INVENTION Below 1 A general schematic diagram of the present invention will be explained with reference to FIG. 1, and an information acquisition method will be explained with reference to FIGS. 2 and 3.

FIG. 1 is an overall schematic diagram of the present invention, showing an automatic information acquisition method when an abnormality occurs in a program. When the program reaches point b at time t1, an interrupt is generated by the timer 8 in FIG. 2, and all information necessary for re-execution from point h is stored in the program information storage file 15.

The same process is performed when the point C is reached. The program is
Suppose that an abnormality occurs when Cx is reached.

Based on the information in the program information storage file, the program is returned to the state at point C and can be re-executed. During re-execution, the program traces the program's behavior and outputs information that helps determine the cause of the abnormal termination. A method for automatically tracing the execution of a program will be described below using the general configuration diagram of FIG. 2 and FIG. 3.

Information for restarting the program when it terminates abnormally is acquired by the program information acquisition unit 14 shown in FIG. What are its operating procedures?

■Information required to re-execute the program (hereinafter referred to as "pro").

Durham information and record-f) Obtain time interval externally.

is set in the program information acquisition time storage section 9 before program execution.

(2) After the start of the program, the comparison section 10 compares the time in the timer 8 and the program information acquisition time storage section, and if it is the acquisition time, sends a signal to the interrupt generation section 12.

0 interrupt generation section is program information acquisition section.

to start.

■Program information acquisition department re-programs.

All information necessary to open the program is stored in the program information file 15 in a conventional manner.

■Repeat steps from ■ to ■ until the program ends.
1. If the program terminates abnormally, the abnormal termination detection section 11 detects it and sends a signal to the interrupt generation section, which starts the trace program section 16 with program recovery function.

The recovery procedure is as follows: (1) From the trace program file; (2) Store the trace program in memory after the loading address information.

■■ recovers the following ■O.

■ Trace data for re-execution (p5rry, registers, etc.) from the program information file Re-execution data within the program itself.

− Stored in the data area.

■Storing the segment being executed to 0 in the program being executed.

Trace program 16 with program recovery function after recovery
The details are shown in Figure 3.

Next, the procedure for acquiring trace information is as follows.

I will explain.

■Collect the program execution address from the PSW.

■Collect instructions from the running program.

■Execute ■ using the trace program.

■Output Depack trace information.

■Return to the next instruction in the program.

■Repeat steps from ■ to ■ above until just before the abnormality occurs to obtain trace information.

According to the above method example.

■By automatically returning to the nearest point from the point where the abnormal termination occurred and executing the process, there is no need to execute the program from the beginning.

Rerun time is reduced. Re-run during ■ above.

The trace information of the executed program is automatically output to a line printer, etc.

This has the effect of reducing the number of man-hours required to investigate the cause of bug occurrence.

Effects of the Invention Since the structure is as described above, the following effects can be obtained with the present invention.

■Like a conventional checkpoint restart.

There is no need to incorporate special commands into the user program, and there is no need to request man-hours for re-execution, so there is no work burden on the programs.

■When an abnormal termination occurs due to a bug occurring, the process returns to the point closest to the point of occurrence and re-executes, reducing the number of man-hours required to investigate and investigate the cause of an abnormal termination.

This shortens the program development period including debugging time.

■Collect the minimum necessary information by changing the depacking function of the trace program itself.

I can do it.

[Brief explanation of drawings]

FIG. 1 is an overall schematic diagram of an embodiment of the present invention. FIG. 2 is an exemplary block diagram for explaining the overall configuration, and FIG. 3 is a block diagram for explaining an execution method of recovery for re-execution and automatic tracing from a program information file. 1...Program execution order. 2...Cheetsuku Point. 3...Abnormal termination point. 4...Program information file. 5...Data group. 6...Trace information list. 8...Timer. 900. Program information acquisition time storage unit. 10... Comparison section. 11...Abnormal termination detection section. 12...Interrupt generation section. 13...User program. 14...Program information acquisition section. 16...Race program with program recovery function. 17...Trace program file. 23...All phlog files. r1 24...Re-execution data area. 25...Memory, 26...Trace program section. 2B...Trace program body. 7 z Illustration 3 Illustration S

Claims (1)

[Scope of Claims] 1. In the case where an abnormal termination of a program occurs during the execution of a program in an electronic computer. ■Generate a clock using a timer to generate all the information necessary to re-execute the program. It is automatically saved to a file after a certain period of time. With means. 1 (" ■If the program terminates abnormally, a means to recover the information stored in ■, read each instruction by a trace program, output traces, and return to a state where it can be re-executed. ■Re-execute from the state of ■ above. 1. An automatic information acquisition system characterized by comprising means for automatically outputting information necessary to a programmer at the time of depacking by tracing the operation of the program when the program is depacked.