JPS63217436A - Abort dump collecting system for program - Google Patents

Abstract

PURPOSE:To eliminate the dump of an undesired task occupied segment by securing such a constitution where a slave task information to an abnormal end processing part whether it collects the task occupied segments of its own task as the dump information after the start of its execution. CONSTITUTION:When it is considred that the contents of the task occupied segments of slave tasks 23 and 24 forming a program 21 are needed for analysis of the abnormal end causes of both tasks 23 and 24, this fact is informed to an abnormal end processing part after both tasks 23 and 24 started their execution. When said contents are not needed, this fact is also information to the abnormal end processing part after the tasks 23 and 24 started their executions. Thus it is decided whether the task occupied segment should be collected or not when the both tasks 23 and 24 end in an abnormal state. At the same time, the information on the control of the tasks 23 and 24 are collected among those contents of the segment shared among tasks when both tasks 23 and 24 end abnormally. This it is possible to select the collection or non-collection of task occupied segment for each of both tasks 23 and 24. Then the output of the segment shared by tasks just by collecting the desired information only.

Description

[Detailed Description of the Invention] [Field of Industrial Application] The present invention relates to a program aport dump collection method,
In particular, it relates to an aport dump collection method when a child task in a multiple task terminates abnormally.

[Conventional technology]

Conventionally, the aport dump collection method for a program with a multi-task configuration consisting of a parent task and one or more child tasks is to collect the inter-task shared segment and the task exclusive segment if the abnormally terminated task is the parent task. There is a known method in which a task exclusive segment is collected, and if the abnormally terminated task is a child task, the task exclusive segment is collected. This is because in most cases, conventionally, to analyze the cause of a parent task's abnormal termination, it is sufficient to have the contents of its private segment and shared segment, and to analyze the cause of a child task's abnormal termination, it is sufficient to have the contents of its private segment. Because it was considered sufficient.

[Problem that the invention seeks to solve]

In the conventional port dump collection method described above, when a child task terminates abnormally, the task exclusive segment owned by the child task is unconditionally collected and output. This is because, as mentioned above, it was thought that the contents of the private segment would normally be sufficient to analyze the cause of abnormal termination of a child task. However, since the shared segment contains information regarding the control of the child task, it is easier to analyze the cause of the abnormal termination of the child task if the contents of the shared segment are also collected.

However, in the conventional method, only the task exclusive segment was collected, which had the disadvantage that the cause could not be efficiently analyzed. Also,
For some child tasks, it is possible to analyze the cause of abnormal termination by knowing the contents of the shared segment without knowing the contents of the proprietary segment (for example, most of the information is in the shared segment, and a copy of it is in the proprietary segment). Even in such cases, the conventional method collects task-only segments uniformly, so if a child task terminates abnormally when it has a large segment with a large capacity as a private segment, a large amount of data will be collected. The disadvantage is that dump information is output.

The present invention has been made in view of these circumstances,
The purpose is to provide an aport dump collection method for a program that allows selection of whether or not to collect task-specific segments for each child task, and also collects and outputs only necessary information regarding inter-task shared segments. It is in.

[Means for solving problems]

In order to achieve the above object, the present invention provides an aport dump collection method when a child task abnormally terminates in a program with a multi-task configuration. The abnormal termination processing unit is configured to notify the abnormal termination processing unit whether or not to collect the task exclusive segment as dump information, and when the child task terminates abnormally, the abnormal termination processing unit performs task exclusive use of the child task by the notification. The task-specific segment is collected only when segment collection is instructed, and information related to the control of the child task is collected from among the inter-task shared segments of the child task.

[Effect]

If the contents of the task-specific segment are considered necessary to analyze the cause of abnormal termination of a child task, the contents of the task-specific segment are configured to notify the abnormal termination processing module after the child task starts execution, and conversely, if the contents of the task-specific segment are deemed to be unnecessary. In this case, by configuring the child task to notify the abnormal termination processing unit of this fact after the child task starts execution, it is determined whether or not the task exclusive segment is to be collected when the child task abnormally terminates.

Further, when a child task terminates abnormally, information related to control of the child task is collected from among the contents of the inter-task shared segment.

〔Example〕

Next, embodiments of the present invention will be described with reference to the drawings.

Figure 2 shows a program (PR○G) 21 with a multi-task configuration.
is a diagram showing a configuration example of a program 21, a parent task (MAIN) 22 and a child task (SUBX) 23.
and a child task (SUBY) 24.

FIG. 3 is a diagram showing the address space of the program 21 having the multi-task configuration, in which the parent task 22 has a task exclusive segment 34 unique to the task and an inter-task shared segment 37 which is a shared segment between tasks. The child task 23 has a task exclusive segment 35 and an inter-task shared segment 37, and the child task 24 has a task exclusive segment 36 and an inter-task shared segment 37.

FIG. 1 is a block diagram of an embodiment of the present invention, and the configuration and operation of this embodiment will be explained below with reference to each figure.

Before starting the execution of the program 21, for example, specify in advance with a parameter whether or not the task exclusive segment 35-36 is to be collected as dump information when the child task 23-24 constituting the program 21 terminates abnormally. I'll keep it. For convenience of explanation, the following description assumes that a parameter that instructs the collection of the task exclusive segment 35 is input for the child task 23, and a parameter that does not instruct the collection of the task exclusive segment 36 is input for the child task 24.

When the execution of the program 21 having a multi-task configuration is started, as shown in FIG. Child task 23
is activated (32), and execution of the child task 23 is started (S3).

The child task 23 first determines whether or not to collect a dump of the segment 35 unique to the self-task when the self-task terminates abnormally, using the task-specific segment collection instruction processing provided in the self-task 23. In the present example, the child task 23 instructs the collection of the task exclusive segment 35 to the processing unit 11 (S4), and
retains this information.

Similarly, when the child task 24 is activated by a command to activate the child task 24 in the parent task 22 and the child task 24 starts execution, the child task 24 performs the collection instruction process (S4 ) instructs the abnormal termination processing unit 11 not to collect the task exclusive segment 36 in this example, and the abnormal termination processing unit 11 retains this information.

Now, if an error occurs during the execution of child task 23 (35
), the processing of the abnormal termination processing unit 11 is started, and it is determined whether or not to collect a dump of the segment 35 unique to the child task 23 by the task exclusive segment collection determination process (S6), and in the present example, collection is possible. is instructed, a dump of the task exclusive segment 35 is collected (37). Also, by the inter-task shared segment necessary information collection process S8, the contents of the inter-task shared segment 37 are collected from the child task 23. Only information related to control is collected as necessary information. When the collection of the dump by the necessary information collection process of the inter-task shared segment 37 is completed, the processing of the abnormal termination processing unit 11 is completed, and the execution of the child task 23 is ended (S9).

After that, when the execution of the parent task 22 is finished (S to)
The information collected by the abnormal termination processing unit 11, that is, the contents of the task exclusive segment 35 of the child task 23 and the necessary information in the inter-task shared segment 37, are output to a dump information storage device or the like by the aport dump output means ( Sl
l).

On the other hand, if an abnormality occurs in a child task 24 that has not been instructed to collect a task-only segment, a dump of the segment 35 unique to the child task 24 is not collected in the task-only segment collection determination process of the abnormal termination processing unit 11. is determined (36), and by the inter-task shared segment necessary information collection process S8, the inter-task shared segment 37
Among the contents, only the information related to the control of the child task 24 is collected as necessary information, and only the necessary information in the inter-task shared segment 37 collected by the abnormal termination processing unit 11 after the execution of the parent task 22 is collected as the aport dump. It is output as information, and the contents of the task exclusive segment 36 are not output.

〔Effect of the invention〕

As explained above, the present invention makes it possible to decide for each child task whether or not to collect a task-only segment at the time of its abnormal termination, so that the contents of the task-only segment are not necessary for analyzing the cause of abnormal termination. By not instructing child tasks to be collected in advance, there is an effect that unnecessary dumping of task exclusive segments can be eliminated.

Furthermore, since information related to the control of the child task is collected from the contents of the inter-task shared segment when a child task terminates abnormally, the cause of the abnormal termination of the child task can be efficiently analyzed.

[Brief explanation of the drawing]

FIG. 1 is a block diagram of an embodiment of the present invention, FIG. 2 is a diagram showing an example of the structure of a program with a multi-task structure, and FIG. 3 is a diagram showing an address space of a program with a multi-task structure. In the figure, 81 to 311 are processing steps, 11...
Abnormal termination processing unit, 21... Program with multi-task configuration, 22... Parent task, 23.24... Child task,
34.35°36...Task exclusive segment, 37.
...A shared segment between tasks.

Claims (1)

[Claims] In an aport dump collection method when a child task abnormally terminates in a program with a multi-task configuration, the child task dumps the task exclusive segment of the self-task when the self-task terminates abnormally after starting its execution. The abnormal termination processing unit is configured to notify whether or not to collect the information as information to an abnormal termination processing unit, and the abnormal termination processing unit is configured to instruct collection of the task exclusive segment of the child task by the notification when the child task terminates abnormally. A method for collecting an aport dump of a program, characterized in that the task exclusive segment is collected only when the task is executed, and information related to the control of the child task is collected from the inter-task shared segment of the child task.