JPH0567016A - Program abnormal operation monitor system - Google Patents

Abstract

PURPOSE:To detect the abnormality of a program by information issued at the time of transmitting and receiving a message constituted of plural synchronously operating tasks. CONSTITUTION:In a message monitoring part 30, an interface part 34 with a host CPU, memory 32 in which a program is stored, and sub CPU 31 which controls the transmission and reception of the message by the program, are connected through a local bus 33.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program abnormal operation monitoring system, and in particular, in a real-time system having a CPU, a program to be installed is controlled by a plurality of tasks that operate synchronously by sending and receiving messages under the control of a real-time OS. In this case, the present invention relates to a program abnormal operation monitoring method for monitoring a message transmission / reception notification issued at the time of message transmission / reception.

[0002]

2. Description of the Related Art FIG. 4 is a diagram showing an example of a conventional program abnormal operation monitoring system. The conventional example is composed of a real-time program consisting of a plurality of tasks, and 21 to 24 represent tasks, and arrows connecting the tasks represent the flow of a message serving as an inter-task interface. Reference numeral 21 is a task that is activated at regular intervals and sends a message to the processing tasks 22 and 23. The processing tasks 22 and 23 activated by the message are common lower tasks 24 depending on the situation.
To control. Message transmission / reception is performed by issuing a system call indicated by a broken line from each task to the real-time OS.

[0003]

In the conventional program abnormal operation monitoring method described above, in a system using a real-time program, only some tasks are stopped due to a deadlock due to a program defect or resource conflict. There were times when it ended up. Since this kind of failure is caused by software, it is difficult to detect it in terms of hardware.

[0004]

In the program abnormal operation monitoring method of the present invention, an interface unit with the host CPU, a memory for storing the program, and a sub CPU for controlling transmission / reception of messages by the program are provided on a local bus. The abnormality is detected by the notification issued when the message is transmitted and received, which is composed of a plurality of tasks that are connected with each other and operate in synchronization.

[0005]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described with reference to the drawings. FIG. 1 is a block diagram of an embodiment of the present invention, FIG. 2 is a flow chart for explaining the operation of the present embodiment, and FIG. 3 is a diagram showing the contents of a message of the present embodiment.

In the message monitoring unit 30 shown in FIG. 1, 31 is a sub-CP for managing the message monitoring unit 30.
U, which monitors the message transmission / reception notification according to the program on the memory 32. 33 is a local bus, 3
Reference numeral 4 is an interface with the host CPU.

FIG. 3 shows the contents of the message transmission / reception notification, and the task ID is an ID for identifying the task that transmitted the message. The message ID is a number assigned to the message issued by the relevant task.
And specify the message. The number of bytes sent (received) is the message length. The message monitoring unit 30 issues a fault alarm when the message lengths at the time of transmission and the time of reception are different or the occurrence of a message that is not received even after the stipulated time has elapsed is detected based on these information.

Next, the operation of this embodiment will be described with reference to FIG.
This will be described with reference to (b). Step S1 of FIG. 2 (a)
1 to S13 are message transmission processes. After the task on the transmitting side issues a message transmission request system call (S11), the real-time OS executes the same transmission processing as the conventional one (S12), but thereafter, the message monitoring unit 3
Notify 0 that the message has been sent (S
13).

Steps S14 to S16 of FIG. 2B are a message receiving process. After issuing a message reception request system call from the task on the receiving side (S14),
The real-time OS executes the same receiving process as the conventional one (S15), but thereafter, with respect to the message monitoring unit 30,
Notify that a message has been received.

[0010]

As described above, in the abnormal program operation monitoring method of the present invention, a message monitoring unit is provided, and a message transmission / reception notification issued at the time of message transmission / reception is monitored to detect a program abnormality. can do.

[Brief description of drawings]

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

FIG. 2 is a flowchart for explaining the operation of the present embodiment.

FIG. 3 is a diagram showing the contents of a message of this embodiment.

FIG. 4 is a diagram for explaining a conventional program abnormal operation monitoring method.

[Explanation of symbols]

 30 message monitoring section 31 sub CPU 32 memory 33 local bus 34 interface section with host CPU

Claims (1)

[Claims] 1. An interface unit with a host CPU,
The memory in which the program is stored and the sub CPU that controls the transmission and reception of the message by the program are connected by the local bus, and the abnormality is notified by the notification issued when the message is transmitted and received, which consists of a plurality of tasks that operate in synchronization. A program abnormal operation monitoring method characterized by detecting.