JPH06149615A - Event recording system - Google Patents

Abstract

PURPOSE:To simply and efficiently record task switching history and event generation history capable of accurately reproducing the operation of a multitask program. CONSTITUTION:Tasks A to C in a user program 2 are operated by a task control part 32 in accordance with the task scheduling of an operating, system and task scheduling obtained by simulating task switching algorithm, and at the time of generating task switching, task switching information including task switching generation time and its contents is sent and recorded to/in an event recording device control part 33. At the time of generating a system call or an external interruption, whether a factor generating the status is caused by the generation of an event determined by the control part 33 in accordance with an instruction generated from a terminal equipment 5 or not is inspected by an event detection inspected part 31, and when the inspected result is yes, event information including event generation time and its contents is acquired, sent and recorded to/in the control part 33.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an event recording method suitable for debugging work for reproducing and investigating the operation of a multitask program.

[0002]

2. Description of the Related Art Generally, in order to perform multi-task debugging, the order of occurrence of events in each task and their contents are investigated and saved, and the recorded event history is used to reproduce the operation of the program. It is necessary to investigate the behavior of the program. Conventionally, as a method to realize a monitor that records event history by software in order to reproduce the operation of the program,

(1) A system in which a dedicated task (event recording task) for monitoring each task is prepared, and events generated by system calls and interrupts generated by each task are collected and an event history is recorded (2) OS simulator There is known a method of recording an event history by providing an event search function to the.

[0004]

However, in the above method (1) of preparing a task for monitoring / recording an event (event recording task), the event recording task itself is also controlled as one of the tasks. It was difficult to recognize the task switching as an event and record when it was performed.

That is, in the method in which the execution order of tasks is left to the scheduling of the operating system and the monitor examines the event and the task switching by monitoring the system call and the interrupt, it is possible to detect when the task switching is performed. In order to do so, each time an event or interrupt in which task switching can occur occurs, control must be transferred to the event recording task to investigate the status of all tasks, and it must be predicted whether or not the task will switch. , Was not efficient.

In addition, in order to record the occurrence time and contents of the event and task switching, the above method (2) using an OS simulator having a function of recording the event and task switching operating on the operating system is It required a lot of resources, was slow in execution speed, and was difficult to realize.

That is, in order to accurately reproduce the operation of a program by using the event history, the task switching timing by the operating system and the history of the task name to be executed are also required, but the conventional task It was difficult to record the switching using a software monitor running on the operating system.

The present invention has been made in consideration of the above circumstances, and an object thereof is to easily and efficiently record a task switching history and an event occurrence history that enable accurate reproduction of multi-program operation. It is to provide an event recording method that can record to.

[0009]

In order to achieve the above object, the present invention operates each task of an event recording target program according to an algorithm that simulates a task scheduling and task switching algorithm of an operating system, When a switch occurs, the task control means that acquires the task switch information including the task switch occurrence time and the switch content, and the occurrence of the event are detected by monitoring external interrupts or system calls made by the task. , An event detection investigating means for investigating the occurred event and acquiring event information including the event occurrence time and the content of the event, and controlling the task control means and the event detection investigating means, and at the same time the event information and the task Based on the switching information
It is characterized by comprising an event recording device control means for creating and recording an event generated in the target program and a history of task switching.

[0010]

In the above structure, the task control means in the monitor (event recording device) realized by using a specific task (event recording task) operating on the operating system is used for task scheduling and task switching of the operating system. The task scheduling algorithm that simulates the algorithm, and the information necessary for the task scheduling are retained, the time to operate the task is determined according to the scheduling algorithm, and the task to operate is determined by the operating system in order to operate the task according to the determination. Let it run and wait for other tasks. The task recording algorithm held by the task control means and information necessary for task scheduling are given from the event recording device control means.

As described above, the scheduling of each task of the program that is the target of event recording (investigation) and the determination of the timing of task switching are performed not by the operating system, but by the task control means in the monitor operating on the system. Performed by. Therefore, the task switching information including the task occurrence time and its switching content can be easily acquired by the task control means being monitored. This task switching information is notified to the event recording device control means. Further, by letting the operating system perform processing such as task swapping for operating the task, the load on the monitor (task control means therein) can be reduced.

On the other hand, the event detecting / inspecting means detects the occurrence of an event by recognizing the task being executed and observing an external interrupt or a system call issued by the task being executed. The event to be detected by the event detection / inspection means is determined by the event recording device control means in accordance with a request from the user.

When detecting the occurrence of an event, the event detecting / inspecting means investigates the occurring event, acquires the event occurrence time and the information about the task that caused the event from the task or the operating system, and as event information. Notify the event recording device control means.

The event recording device control means, based on the event information notified from the event detection investigation means and the task switching information notified from the task control means, the event generated in the target program and the task performed by the task control means. Create a switching history and record / save it in an external recording device.

[0015]

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

In FIG. 1, 1 is an operating system (multitasking operating system), 2
Is a user program (user program) operating on the operating system 1. The user program 2 is a program that is a target of event recording, and is composed of, for example, three tasks, task A, task B, and task C. Task A of this program 2,
Examples of contents of B and C are shown in FIGS. 2 (a), 2 (b) and 2 (c).

The operations of the above three tasks A, B and C are essentially non-deterministic. In other words, the behavior changes depending on which task of tasks A, B, and C starts execution, when task switching is performed, and the like. For example, it is assumed that the user activates these three tasks A, B, and C "simultaneously". At this time, as a result of the scheduling of the operating system, different behavior is performed depending on whether task B sends a motion message first or task C sends a message.

3 is a task A which constitutes the program 2,
An event recording device 4 for investigating and recording the operations of B and C, 4 is an external recording device for storing the information of the event investigated by the event recording device 3 and the history of task switching, and 5 is a terminal device. The terminal device 5 inputs the information required for event recording according to the input operation of the user, and transmits it to the event recording device 3 (in the event recording device control unit 33 described later).

The event recording device 3 is realized by using a dedicated event recording task that operates on the operating system 1, and is composed of an event detection / inspection unit 31, a task control unit 32, and an event recording device control unit 33. It

The event detection / inspection section 31 uses a system call issued by the event recording target task (A, B, C),
A function that detects an interrupt from the outside or a change in the status of a task, and investigates whether the cause of the status is the occurrence of an event, and obtains information about the task that generated the event from the task or operating system 1 With the function to get from. In this example, the exchange of messages by tasks A, B, and C is regarded as an event. This event definition is performed from the terminal device 5 according to a user operation, for example, and the event recording device control unit 33 notifies the event detection investigation unit 31.

The event detection / inspection unit 31 also has a function of notifying the event recording device control unit 33 of event information including the event occurrence time and its content. This event information includes an event occurrence time, the content of the event, the task name of the task that generated the event (event generation task name), and the address that generated the event (event generation address).

The task control unit 32 generates / creates an event target task according to a task scheduling algorithm.
A function that requests control / termination to the operating system 1, a function that investigates when a task issues a system call, and a task switching information that includes the task switching occurrence time and its content when a task switching occurs And has a function of notifying the event recording device control unit 33.

As the task scheduling algorithm in this example, a simulation of a time-division scheduling algorithm of an operating system (OS) is applied, whereby each task is executed from task A for a fixed time, for example. It Here, the task control unit 32 first generates the tasks A, B, and C, immediately stops them, records the task IDs (task names), operates the tasks one by one, and switches the tasks each time.
As a result of task scheduling, the task switching occurrence time, the execution end task name (task name of the task that was being executed until then) and the execution end address, and the next execution task name (the task name of the next task to be executed) The next execution start address is sent to the event recording device controller 33 as task switching information.

In the present embodiment, the clock used for recording the occurrence time of the event and the task switching is the program 1
It is a logical timepiece that advances by "1" when step execution is performed, and returns to "0" when the maximum value is exceeded.

Next, the event recording device control unit 33 determines the event to be detected in the event detection investigation unit 31 (message exchange in this example) according to the input from the terminal device 5, and the task control unit 32. With a function to give a program (in this example, program 2) to be investigated.

The event recording device control unit 33 also, based on the event information sent from the event detection investigation unit 31 and the task switching information sent from the task control unit 32,
It has a function of creating and storing in the memory (not shown) an event that occurred in the program 2 that is the target of event recording and a task switching history performed by the task control unit 32, and then save it in the external recording device 4. The format of this history consists of four types of information: event / task switch occurrence time, event / task switch occurrence task name, event / task switch occurrence address, and event / task switch content. Is stored. Next, the operation of the configuration of FIG. 1 will be described.

First, in the configuration of FIG. 1, from the operating system 1, the tasks A, B, and C constituting the program 2 operate under the management of the event recording task (which realizes the event recording device 3). Seems to be a subtask to do. Further, the event recording task appears to the operating system 1 as a normal task.

Now, in this embodiment, tasks A, B,
In order to investigate the operation of C, the task scheduling by the task control unit 32 in the event recording device 3 is performed by applying the simulation of the time-division scheduling algorithm of the OS as described above, and When the message exchange by the task C is treated as an event, the event recording device 3 behaves as follows.

First, the task control section 32 of the event recording device 3 executes the 0th line (A-0) of the task A. In this case, the task control unit 32 first interprets that the task switching has been performed for the task A, and notifies the event recording device control unit 33 of this task switching. That is, the task control unit 32
Notifies the event recording device control unit 33 of task switching information including a task switching occurrence time, a next execution task name, and a next execution start address. Since it is the first time here, there is no execution end task name and execution end address in the task switch information, and the task switch time (event
The task switching occurrence time) is "0", the next execution task name is "A", and the next execution start address is "0".

In response to the notification from the task control unit 32, the event recording device control unit 33 sets “0” as the event / task switching occurrence time and the event / task switching content (task control unit as shown in FIG. The "task switching to A-0" generated based on the next execution task name "A" and the next execution start address "0" notified from 32 is stored in the memory. Thereafter, every time the task is switched, the task switching information is notified from the task control unit 32 to the event recording device control unit 33.

When the fourth line (A-4) of the task A is executed, the system call [refer to the mailbox m] is issued from the task A, as is clear from FIG. 2 (a). It Then, the event detection / inspection unit 31 receives this system call, investigates the task A, and determines that it is an event. As a result, the event detection investigation unit 31
Indicates to the event recording device control unit 33 that an event [referencing the mailbox m] has occurred, the event occurrence time (event / task switching occurrence time), and the task name of the task that generated the event. Event information for notifying A ”and the event occurrence address“ 4 ”(4th line) is recorded in the event recording device control unit 33.
Send to. Here, the event occurs at the fifth step after the event A is scheduled and the recording of the event is started, so the occurrence time is 5.

According to the notification from the event detection investigation unit 31, the event recording device control unit 33, as shown in FIG.
"5" as the event / task switching occurrence time, "A" (task A) as the event / task switching occurrence task (event occurrence task), and "4" as the event / task switching occurrence address (event occurrence address) “[Refer to mailbox m]” is stored in the memory as the content of event / task switching.

Next, it is assumed that task switching occurs when the fifth line (A-5) of task A is executed and task B is switched to. Since this task switching has occurred at the sixth step after switching to task A, the task switching occurrence time is "6". In this case, the task control unit 3
2 is task switching occurrence time “6”, execution end task name “A” and execution end address “5” (for task A), next execution task name “B” and next execution start address “for task B” The event recording device control unit 33 is notified of task switching information consisting of 0 ″.

According to the notification from the task control unit 32, the event recording device control unit 33, as shown in FIG. 3, has "6" as the event / task switching occurrence time and "A" (as the event / task switching occurrence task. "A" (task A) is used as the event / task switching occurrence address.
End execution address) of the event / task switching (generated based on the next execution task name “B” and the next execution start address “0” notified from the task control unit 32) “B-0 Task switching ”in the memory.

When the third line (B-3) of task B is executed, as is clear from FIG. 2B, [task A
Send message to] event occurs. The event occurrence time at this time is "9". In this case, "9" is stored in the memory as the event / task switching occurrence time.
"B" (task B) as the event / task switching occurrence task, "3" (third line) as the event / task switching occurrence address, and "[Send message to task A]" as the event / task switching content. Are sequentially stored (see FIG. 3).

Next, the execution of task B proceeds, and after the execution of the fifth line (B-5) of task B, the second line (B
-It is assumed that the task C is switched to when task 2) is executed. In this case, from the task control unit 32 to the event recording device control unit 33, the task switching occurrence time “13”, the execution end task name “B”, the execution end address (of the task B) “2”, and the next execution task name “ C "and (for task C)
The next execution start address “0” is notified. In this case, the event / task switching occurrence time is "1" in the memory.
3 "is" B "as the event / task switching occurrence task
(Task B) stores "2" (task B execution end address) as the event / task switch occurrence address and "task switch to C-0" as the event / task switch content (see FIG. 3). ).

Next, the execution of task C proceeds, and task C 3
It is assumed that the [send message to task A] event occurs when the line (C-3) is executed (Fig. 2).
(See (c)). In this case, in the memory, "16" is set as the event / task switching occurrence time, "C" (task C) is set as the event / task switching occurrence task, and "3" (3rd line as the event / task switching occurrence address). )But,
"[Send message to task A]" is sequentially stored as the content of the event / task switching (see FIG. 3).

After that, it is assumed that the task switching occurs in the second line (C-2) of the task C that is re-executed, and the task C is switched to the task A. In this case, the task switching time is "2".
0 ", the execution end task name is" C ", the execution end address (for task C) is" 2 ", and the next execution task name is" A ". The next execution start address (for task A) is the previous If there is no mail in the fifth line (A-5) when task A is executed, the result will be "3" (A-13) (Fig. 2).
(See (a)). Therefore, in memory
"20" as the task switching occurrence time, "C" (task C) as the event / task switching occurrence task, and "2" (second line) as the event / task switching occurrence address
However, "task switch to A-13" is stored as the content of the event / task switch (see FIG. 3).

The event recording device control unit 33 stores the history of event occurrence and task switching (event / task switching history) stored in the memory as shown in FIG. 3 as described above.
Is stored in the external recording device 4. The event / task switching history stored in the external recording device 4 is shown in a table form in FIG.
Shown in.

Next, the processing performed in the event recording device 3 to obtain the above event / task switching history will be described.
Description will be given separately for the preparation stage and one cycle of task scheduling.

First, in the preparation stage, the event recording device control unit 33 requests the task control unit 32 to generate tasks A, B, and C and stop them (end) in accordance with an instruction input from the terminal device 5. When the task control unit 32 completes the task generation and stop work requested, the event recording device control unit 33 notifies the event detection / inspection unit 31 that the event to be acquired is message exchange.

Next, the event recording device control unit 33 passes to the task control unit 32 an algorithm for executing each task in order from the task A for a fixed time as a scheduling algorithm.

The process up to this point is the preparation stage, and thereafter, the cycle of the processing of the event recording device 3 mainly performed by the task control unit 32 continues. This processing cycle will be described with reference to the flowchart shown in FIG.

In this cycle, the task control section 32 first determines the task to be executed next according to the scheduling algorithm (step S1). Then, the task control unit 32 notifies the event recording device control unit 33 of the scheduling result, that is, the task switching occurrence time, the execution end task name, the execution end address, the next execution task name, and the next execution start address (step S2). ).

Next, the task control unit 32 executes the task selected according to the task scheduling algorithm according to the task switching algorithm (step S
3).

When a system call or an interrupt occurs while the task is being executed under the control of the task control section 32, the control is transferred to the event detection investigation section 31.
Then, the event detection investigation unit 31 requests the task control unit 32 to stop the task being executed, and investigates whether the cause of this state is an event occurrence (message exchange in this example). If it is caused by an event occurrence, the content of the event is acquired from the event occurrence task and is notified to the event recording device control unit 33 together with the event occurrence time, the event occurrence task name and the event occurrence address (step S
4). Here, the event occurrence task name and the event occurrence address are acquired from the task control unit 32.

When task switching occurs while a task is being executed under the control of the task control unit 32, the task control unit 32 checks whether there is a command (instruction) from the event recording device control unit 33. From (step S5), the process proceeds to the next cycle.

By repeating the above, the event / task switching history as shown in FIG. 3 is stored in the memory, and the event / task switching history table shown in FIG. 4 is generated in the external recording device 4 from the contents of this memory. It

In the above embodiment, the case where the message exchange is regarded as an event has been described. However, the present invention is not limited to this, and a case where a variable has a certain value according to an instruction input from the terminal device 5, It is also possible to catch the event of calling a system call as an event. In the latter case, the content of the event needs to be obtained from the operating system 1, not from the task.

[0050]

As described above in detail, according to the present invention,
Each task of the event recording target program is operated by the task control means according to the task scheduling of the operating system and the task scheduling simulating the task switching algorithm. When the task switching occurs, the task control means causes the task switching occurrence time and the switching. The task switching information including the content is configured to be acquired, and the target detection program operated by the control of the task control means is monitored by the event detection investigation means to detect the occurrence of the event, and the event occurrence time and the content of the event are displayed. Since it is configured to acquire the event information including the task switching information and the history of the event switching and the task switching based on the event information, the occurrence of the task switching can be easily detected and recorded. Which task is currently Because it can easily know whether you are work, investigation of the events that have occurred in the target program
Recording can be done efficiently. In addition, by using the event record (event / task switching history) obtained in this way, it is possible to accurately reproduce the operation of the program, which can significantly reduce the debugging time of the user program.

[Brief description of drawings]

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

FIG. 2 is a diagram showing an example of the contents of tasks A, B, and C that constitute a program targeted for event recording in the embodiment.

FIG. 3 is a diagram showing an example of storing a history of event / task switching on a memory in the same embodiment.

FIG. 4 is a diagram showing an event / task switching history table recorded in an external recording device 4 from the memory contents of FIG. 4;

FIG. 5 is a flowchart mainly illustrating a processing cycle of the event recording device 3 performed by the task control unit 32.

[Explanation of symbols]

1 ... Operating system, 2 ... User program, 3 ... Event recording device, 4 ... External recording device, 5 ... Terminal device, 31 ... Event detection investigation part, 32 ... Task control part, 33 ... Event recording device control part.

Claims (1)

[Claims] 1. An event recording method for recording an event occurring in a user program consisting of a plurality of tasks operating on a multitasking operating system, simulating a task scheduling function and a task switching algorithm of the operating system. The task control means for operating each of the tasks according to the scheduling, and acquiring the task switching information including the task switching occurrence time and the switching content when the task switching occurs, and the program of the event recording target. An event detection investigating unit that monitors an execution state to detect the occurrence of an event, and obtains event information including an event occurrence time and the content of the event; and the task control unit and the event detection investigating unit, and the task. control Event recording device control means for creating a history of events and task switching occurring in the program based on the task switching information acquired by the means and the event information acquired by the event detection and investigation means. The event recording method is characterized in that the history of events and tasks created by the event recording device control means is recorded in the recording device.