JPH04336631A - Error message output system - Google Patents

Abstract

PURPOSE:To recognize an area of a program where an error is detected and the information on the program execution history by recognizing the details of execution of the program to store them in a memory and storing the factor of the error and the program executed position when the error is detected. CONSTITUTION:When an error factor is detected, this factor and a relative number are set in an area (dollar symbol) E. Then a main routine is reset in a return state after each information is set in the area E, and the detection of an event is decided. The detection of the event is confirmed when the error factor is detected in a subroutine and the information is set in the area E. Thus the information on the area E storing the error information and the information on an area (dollar symbol) R storing the execution history are outputted as an error message. Thus an intra-subroutine relative number showing the error detected area is outputted together with the error factor as the information stored in the area E. Meanwhile an identification data A-B is outputted from the area R.

Description

[Detailed description of the invention]

0001

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for outputting error messages when an information processing apparatus executes a program. BACKGROUND ART Some information processing devices, such as computers and electronic exchanges that execute programs and perform control, execute a series of processes and, when an error factor occurs, output the error and terminate the process. With this method, when programs that use common subroutines are executed, error information (also called events) may be passed around, making it impossible to identify the location of the error, and improvements are desired.

0002

2. Description of the Related Art FIG. 4 shows a processing flow diagram of a conventional example. FIG. 4 is an example in which subroutine B, subroutine C, etc. are provided for main routine program A. After a certain process in program A of the main routine (40 in Figure 4), subroutine B is called (41 in Figure 4).
), when the process of subroutine B (45) is executed, it is determined whether an error factor has occurred (46).

[0003] The cause of this error is that in the process of subroutine B (45), for example, when reading the file memory, an error occurs and reading cannot be performed, or an error occurs that prevents the process from continuing. In this case, information indicating the occurrence of an error (register indicating the status) is set, so by identifying this error occurrence information, the occurrence status of the error cause can be determined.

[0004] If an error factor has occurred, an event is set (47). This is an operation in which a code indicating that an emergency processing state (a state in which processing cannot be continued any longer) has occurred is set in a specific register. Once this event setting is performed, the program then returns to the end of this subroutine and returns to the original program A. Further, in determining whether an error factor has occurred, if there is no error factor, the next process of subroutine B (48) is executed.

[0005] After that, it branches to subroutine C (49
), in subroutine C, when the process (52) is executed, it is determined whether an error factor has occurred. Based on this judgment, if an error cause has occurred, the event is set in the same way as in subroutine B above, and the process returns to subroutine B; however, if no error cause has occurred, processing (same as 55
) and moves to subroutine D (not shown).

[0006] When the processing of subroutine D ends normally, the process returns to subroutine C, where it is determined whether or not an event has been detected. (same 5)
7). If an event is detected here, the end of subroutine C is reached and the event detected in subroutine B (same 5
0), an event due to the same error occurrence factor is detected here as well, the end of subroutine B is reached, and the program returns to program A of the main routine.

Program A also determines whether an event has been detected (42), and similarly, if an event has been detected, an error message is output (44). In this error message output, an error message (error content) based on event settings executed in any of the subroutines is output.

[0008]

[Problem to be Solved by the Invention] As mentioned above, when a series of processing is executed, if an error factor occurs that prevents further processing from continuing, a mechanism is adopted that outputs an error message and terminates the processing. When a number of common subroutines are used in combination in a hierarchical program, error information (events) is often passed around, so there is a problem in which the location where an error is actually detected cannot be recognized. Ta.

That is, in the example shown in FIG. 4, even if an error factor occurs in subroutine C, the error message output executed by program A includes subroutines B, C,
I don't know which one of D... caused it. SUMMARY OF THE INVENTION An object of the present invention is to provide an error message output method that can recognize not only the cause of an error in a program that uses a combination of subroutines, but also the program location where an error has been detected and the program execution history information.

0010

[Means for Solving the Problems] FIG. 1 is a diagram showing the basic configuration of the present invention. In FIG. 1, 10 is a processing section, 11 is a program execution section, 12 is a routine identifier setting means, 13 is an error confirmation means, 14 is a processing identifier setting means, 15 is an error state identification means upon return, and 16 is a routine identifier updating means. , 17 is an error information output means, 18 is a memory, and 181 are individual subroutines, and each subroutine is provided with a subroutine identifier 182 and a processing position identifier 183 indicating a processing position within the subroutine.
Reference numeral 184 represents an execution history storage area in which identifiers of subroutines to be executed are sequentially stored, and reference numeral 185 represents an error information storage area in which the error cause and the identifier of the processing position at the time of error occurrence are stored.

[0011] The present invention recognizes the process of program execution and stores it in memory, and when an error is detected, the cause of the error and the position where the program was executed are stored. and the program's execution history information.

0012

[Operation] In FIG. 1, when the program execution unit 11 of the processing unit 10 executes a program, it first retrieves the main routine program from the memory 18, and thereafter, when called during the process, the corresponding subroutine 181
is extracted and processed. When a program is executed, the subroutine identifier 182 is first detected by the routine identifier setting means 12 and set in the execution history storage area 184 in the memory 18. When the routine is processed, the error checking means 13 checks whether an error has occurred.

When it is confirmed that an error has occurred, the processing identifier setting means 14 takes out the cause of the error and the processing position identifier 183 (relative number within the subroutine, etc.) in the subroutine at that time, and stores it in the memory 18. It is set in the error information storage area 185. Once the error information is set, the processing of this routine (subroutine) is terminated and the original routine is returned. At this time, the return error state identifying means 15 is activated to identify whether or not an error state has occurred in the terminated routine (previously executed routine) that makes it impossible to continue processing any further.

As a result, if an error state (an error state detected by the error checking means) is not detected, the routine identifier updating means 16 is activated to update the execution history storage area 1.
Update the processed routine identifier set to 84 (
delete). In this case, the subsequent processing is executed sequentially. However, when the error state identification means 15 identifies an error state at the time of recovery, the error information output means 17 is activated. As a result, the execution history of the subroutine in the execution history storage area 184 in the memory 18, the error cause in the error information storage area 185, and the processing position identifier (relative number) 183 in the subroutine are output, so the cause and location of the error are output. I understand.

[0015]

Embodiment FIG. 2 is a processing flow diagram of an embodiment, and FIG. 3 is a configuration example of an information processing apparatus in which the present invention is implemented. The processing flow shown in FIG. 2 is executed in an information processing apparatus like that shown in FIG. That is, in FIG. 3, 30 is the main memory (MM
), 31 is the central control unit (CC), 32 is the channel control unit (CHC), and 33 is the file memory control unit (FM
C), 34 is a file memory (FM), 35 is an input/output device controller (IOC), 36 is an input/output device (IO), 3
7 is a line control device (data communication, etc.), and 38 is a line compatible device. Note that 37 and 38 are provided when data communication is performed via a line.

FIG. 2 shows a processing flow of an embodiment applied to the configuration example shown in FIG. When executing a program, each program (main routine A, subroutine B, subroutine C, etc.) is loaded in advance into the main memory 30 from the file memory (34 in FIG. 3). Furthermore, a common area is allocated in the main memory 30 for storing the execution history, and a label "$R" is assigned to this area. Furthermore, a common area for storing area information is allocated and a label "$E" is assigned to this area.

When the main routine is first started (program A is executed), an execution history storage area "$R" allocated in the main memory (see 30 in FIG. 3) is created.
Since “A” is displayed as an identifier in this program, set “A” in area $R (20 in Figure 2).
. Next, NULL (all “0”) is placed in the error information storage area “$E” allocated in the main memory.
(21). Thereafter, the first process of routine A is executed (22), and then subroutine B is called (23).

In executing subroutine B, a program identifier is first set (step 230) in the same way as for program A. This subroutine has “
B" is added, so set "-B" in area $R. Therefore, area $R includes "
A-B" is set.

Next, the first process of this routine is executed (231), and it is determined whether an error factor has occurred (232). As a result, if the occurrence of an error cause is detected, the error cause and a relative number (in the example in Figure 2, "0001" (233) are set in the area $E above.In this case, the error cause is , the setting information of the status display register is used as in the past.

If the occurrence of the error factor described above is detected, after setting each piece of information in area $E, the process returns to the return point, returns to program A (main routine), and in step 24 the event is set. A detection judgment is made (same 25). If an error factor occurs in the subroutine and information is set in area $E, it is determined that an event has been detected, and the process moves to step 28, where the area $E for storing error information and the area $R for storing execution history are stored. Processing that outputs information as an error message is executed.

[0021] Through this output process, the subroutine relative number (0001 in this example) representing the error cause and error detection location is output as information stored in the error information storage area $E, and the subroutine relative number (0001 in this example) is output as information stored in the error information storage area $E. "A-B" is output from area $R. Looking at this, it can be seen that an error occurred at the location with relative number 0001 in subroutine B.

In the determination of the occurrence of an error factor in the next subroutine B, if no error factor is detected, the next process is executed (234), and then subroutine C is called (235). Although the flow in subroutine C is not shown, similarly, "-C" is placed in area $R.
is set (A-B-C), and the processing of subroutine C is similarly executed. If an error occurs during the process, the event detection judgment after returning to subroutine B (
At step 236), it is determined that an event has been detected, and the process moves to the end of subroutine B and returns to program A.

If no error occurs in the processing in subroutine C, when returning to subroutine B, the judgment of event detection (236) indicates that no event has been detected, and the "-C" in the execution history storage area $R is " is set blank (this makes it "A-B"), and the subsequent process of subroutine B is executed (from 237 onwards).

[0024] If no error occurs in the processing of each program of subroutines B, C, etc., when returning to main routine A, event detection judgment (same 24
), there is no detection. After this, initialize area $R (set A) (25), and initialize area $E (
All "0") (26), and the subsequent processing of routine A is executed (27 and subsequent steps).

The size of the above execution history storage area $R is adjusted according to the hierarchical stage of the program, and the size of the error information storage area $E is adjusted according to the number of error causes and the number of error detection locations. be adjusted.

[0026]

According to the present invention, not only the cause of error occurrence but also the process of error detection can be recognized, making it easy to determine whether the error is due to a program error or an external factor.

[Brief explanation of the drawing]

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

FIG. 2 is a processing flow diagram of the embodiment.

FIG. 3 is a configuration example of an information processing device in which the present invention is implemented.

FIG. 4 is a process flow diagram of a conventional example.

[Explanation of symbols]

10 Processing unit 11 Program execution unit 12
Routine identifier setting means 13 Error checking means 14 Processing identifier setting means 15
Error state identification means 16 at the time of recovery
Routine identifier updating means 17 Error information output means 18 Memory 181 Subroutine 182 Subroutine identifier 183
processing position identifier

Claims (2)

[Claims] Claim 1: In a program execution history management method for an information processing device that processes hierarchical programs, a routine identifier is assigned to a subroutine of each program;
An execution history storage area is provided in the memory, and the program execution unit sequentially sets the routine identifier in the execution history storage area at the start of processing of a subroutine, and detects an error condition when returning from the other called routine to the current routine. and means for updating the routine identifier in the execution history storage area to the current routine identifier if the execution history storage area is not executed, and outputting the content of the execution history storage error when an error occurs. [Claim 2] In claim 1, a processing identifier is assigned corresponding to the processing within the subroutine of each program, an error information storage area is provided in the memory, and the program execution unit of the processing device is configured to perform processing after the processing within each routine. When an error is detected by error confirmation, the processing identifier and error cause are set in the error information storage area, and when an error occurs, the contents of the execution history storage area and the error information storage area are output. Output method.