JP7102883B2 - Application program, function program module - Google Patents

Description

The present invention relates to an application program that runs on a computer and a functional program module that is started by the application program and provides functions necessary for the application program to run.

An application program is required to perform the desired processing using a computer. In the past, the development of this application program was carried out independently by each company, but with the recent increase in functionality and complexity, it has been shared by multiple companies. For example, an application program to be developed is divided into a plurality of small program units (referred to as "functional program modules" in the present specification) mainly from the viewpoint of functions, and the plurality of functional program modules are divided into a plurality of companies. Will share the development. Then, one application program is developed by combining the functions provided by the plurality of completed functional program modules.

In the application program developed in this way, the target processing is realized by starting a plurality of functional program modules one after another in a predetermined order to realize the functions. In addition, because of the operation in this way, if even one functional program module containing a program error (so-called bug) exists among the plurality of functional program modules, the processing of the application program ends normally. It disappears.

Therefore, a monitoring program module called a watchdog timer is used to monitor the execution time of the operation by the functional program module, and if the execution time becomes abnormally long, it is determined that a problem has occurred. Then, the application program is forcibly initialized by software. In addition, in order to make it easy to identify the cause of the bug, the function program module that was operating at the time the problem occurred (that is, the function program module that seems to have a bug) and the operation content of the function program module are described. A technique for storing has been proposed (Patent Document 1).

Japanese Unexamined Patent Publication No. 2006-011991

However, when the watchdog timer causes a forced initialization, it may not be possible to find the cause of the problem no matter how much you check the function program module and operation contents that were operating at that time, and as a result, the application. There was a problem that the development of the device might get stuck.

The present invention has been made to solve the above-mentioned problems in the prior art, and a watchdog timer forcibly initializes an application that executes a target process by combining a plurality of functional program modules. The purpose is to provide a technique that can easily identify the cause.

In order to solve the above-mentioned problems, in the application program and the functional program module of the present invention, the application indicates that the functional program module has started and the termination information indicating that the functional program module has finished its operation. The stored contents are not erased even if the program is initialized. It is stored in the backup memory in chronological order. If an argument has been received at startup, the argument is also stored in the backup memory. Furthermore, when the startup information, arguments, and termination information are stored in the backup memory, if the startup information, arguments, and termination information for other functional program modules are stored in the backup memory, the other functional program modules After the start information, arguments, and end information , the start information, arguments, and end information are stored. In addition, when the amount of data of start information, arguments, and end information stored in the backup memory exceeds a predetermined upper limit, new start information, arguments, and end are started in order from the old start information, arguments, and end information. Overwrite the information.
In this way, even if the execution time of the functional program module reaches a predetermined upper limit and is initialized by the monitoring program module, the backup memory can be checked to see if the functional program module has been started normally. You can know. Then, if it is not started normally, it can be determined that the cause is not the functional program module that was operating when the initialization occurred, so the cause of the initialization can be easily identified. It becomes possible.

It is a block diagram which showed the rough internal structure of the application program 1 of this Example. It is explanatory drawing which conceptually showed how the main program module 10m executes a target process by activating a plurality of functional program modules 10 in a predetermined order. It is explanatory drawing which shows a mode that the monitoring program module 10w monitors the execution time of the function program module 10 and initializes the main program module 10m. It is a block diagram which shows the rough internal structure of the functional program module 10 of this embodiment. It is explanatory drawing which showed the internal structure of the backup memory 21 which the function program module 10 of this Example writes data. It is a flowchart of the function providing processing executed by the function program module 10 of this embodiment. It is explanatory drawing which conceptually showed how the functional program module 10 of this Example writes data to the operation history storage area 21a of a backup memory 21. In the application program 1 of the present embodiment, it is an explanatory diagram showing the reason why the cause can be easily identified even when the monitoring program module 10w forcibly initializes the application program 1.

Hereinafter, examples of the present invention will be described in order to clarify the contents of the present invention described above.
A. Device configuration :
A-1. Operation outline of application program 1:
FIG. 1 shows a rough internal structure of the application program 1 of this embodiment. As shown in the figure, the application program 1 includes a main program module 10m, a plurality of functional program modules 10a to 10d, and a monitoring program module 10w.
The functional program modules 10a to 10d are small programs that run on a computer, and each realizes a predetermined basic function. The main program module 10m executes a process intended by the application program 1 (hereinafter, may be referred to as a target process) by starting a plurality of functional program modules 10a to 10d in a predetermined order. Further, the main program module 10m and the functional program modules 10a to 10d operate by reading necessary data from the memory 20 or writing data to the memory 20.
In the following, when it is not necessary to distinguish the individual functional program modules 10a to 10d, they may be simply referred to as the functional program module 10. Further, although the application program 1 of this embodiment includes four function program modules 10, a larger number of function program modules 10 may be provided.

The monitoring program module 10w is a so-called watchdog timer, which starts timing when it is started by the main program module 10m, and forcibly initializes the main program module 10m when a predetermined upper limit time elapses. When the main program module 10m and the function program module 10 are operating normally, the main program module 10m initializes the time counting time of the monitoring program module 10w before the time measuring time of the monitoring program module 10w reaches the upper limit time. .. Therefore, the operating main program module 10m is not initialized by the monitoring program module 10w.

FIG. 2 shows how the main program module 10m executes a target process by activating a plurality of functional program modules 10a to 10d in a predetermined order. In the illustrated example, the main program module 10m first activates the functional program module 10a. Further, when the first functional program module 10 (here, the functional program module 10a) is activated, the monitoring program module 10w is also activated. The solid arrow shown in FIG. 2 conceptually indicates that the main program module 10m is activating the functional program module 10 and the monitoring program module 10w. Further, the monitoring program module 10w starts timing when it is started.

When the functional program module 10a is started by the main program module 10m, the functional program module 10a provides the main program module 10m with basic functions unique to the functional program module 10a by executing a predetermined process. The arrow indicated by the broken line in FIG. 2 indicates that the functional program module 10 provides the basic function to the main program module 10 m. Further, when an argument such as a variable value or a numerical value for specifying the processing content is required for the functional program module 10 to execute the processing, it is acquired from the main program module 10m at the time of startup.

When the function program module 10a executes a predetermined process and finishes the operation of providing the function, the main program module 10m starts the function program module 10b this time according to its own program, and the time counting time of the monitoring program module 10w. To initialize. The arrow of the alternate long and short dash line shown in the figure indicates that the main program module 10m initializes the time counting time of the monitoring program module 10w.
The upper limit of the time measured by the monitoring program module 10w is the time required for the function program module 10a to provide the function and the time required by the main program module 10m to initialize the time measured by the monitoring program module 10w in response to the result. The time is set sufficiently longer than the total time required for the program. Therefore, the main program module 10m can initialize the time counting time of the monitoring program module 10w before the time measuring time of the monitoring program module 10w reaches the upper limit time.

When the functional program module 10b is also started, the main program module 10m is provided with basic functions unique to the functional program module 10b by executing a predetermined process. Then, the main program module 10m starts the functional program module 10c this time, and initializes the time counting time of the monitoring program module 10w.
Here, the time required for the functional program module 10b to provide the function and the time required for the functional program module 10a to provide the function are not necessarily the same. Similarly, the time required for the main program module 10m provided with the function from the function program module 10b to start the function program module 10c, and the main program module 10m provided with the function from the function program module 10a are the function program module 10b. It is not always the same as the time it takes to start.

However, even so, the time required for the functional program module 10b to provide the function and the time required for the main program module 10m to start the functional program module 10c in response to the result (therefore, the time counting time of the monitoring program module 10w is determined. The total time (time required for initialization) is sufficiently shorter than the upper limit time measured by the monitoring program module 10w. Therefore, the main program module 10m can initialize the time counting time of the monitoring program module 10w before the time measuring time of the monitoring program module 10w reaches the upper limit time.

Hereinafter, similarly, the main program module 10m starts the functional program module 10 in this order in the order of the functional program module 10a, the functional program module 10d, and the functional program module 10c according to its own program, and sets the time counting time of the monitoring program module 10w. initialize. The main program module 10m executes the target process by activating the plurality of functional program modules 10 in a predetermined order in this way. Further, if the main program module 10m and the function program module 10 are operating normally, the time counting time of the monitoring program module 10w is initialized before the upper limit time is reached, so that the monitoring program module 10w initializes the time measuring time. The main program module 10m is never initialized.
However, if the main program module 10m or the functional program module 10 does not operate normally for some reason, the time counting time of the monitoring program module 10w cannot be initialized, and the main program module 10m is initialized. ..

FIG. 3 conceptually shows how the monitoring program module 10w initializes the main program module 10m. In the example shown in FIG. 3, as in the case of FIG. 2, the main program module 10m first starts the functional program module 10a and the monitoring program module 10w, and then initializes the time counting time of the monitoring program module 10w. The plurality of functional program modules 10 are started in a predetermined order.
However, in the example shown in FIG. 3, an abnormality has occurred in the functional program module 10d and the operation has not ended. As a result, the time counting time reaches the upper limit time without being able to initialize the time counting time of the monitoring program module 10w by the main program module 10m, is initialized by the monitoring program module 10w, and the operation of the functional program module 10d is forcibly stopped. Will be done.
In this way, when an abnormality occurs in the operation of the main program module 10m or the function program module 10, the main program module 10m is initialized by the monitoring program module 10w. Therefore, it is possible to avoid a situation in which the main program module 10 m or the functional program module 10 goes out of control.

Further, in the monitoring program module 10w, prior to initializing the main program module 10m, the function program module 10 that was operating at that time and the operation contents of the function program module 10 are stored in the backup memory 21 (FIG. 1). See). Unlike the memory 20, the backup memory 21 does not erase the stored contents even if the main program module 10m is initialized. Therefore, when initialization by the monitoring program module 10w occurs, the function program module 10 that caused the initialization can be identified by reading the contents stored in the backup memory 21, or the operation contents. You can locate the bug from.

However, even if the contents stored in the backup memory 21 are read after the initialization by the monitoring program module 10w occurs and the functional program module 10 operating at that time is examined in detail, a bug can be found. Sometimes I couldn't. When such a situation occurs, the reason why the initialization occurred cannot be specified, so that the development of the application program 1 is delayed.
Therefore, the functional program module 10 of this embodiment has the following internal structure.

A-2. Internal structure of functional program module 10:
FIG. 4 shows the internal structure of the functional program module 10 incorporated in the application program 1 of this embodiment. As shown in the figure, the functional program module 10 of this embodiment includes an activation request detection unit 11, a function providing unit 12, an activation information output unit 13, and an end information output unit 14.
In addition, in order to make it possible to easily identify the cause of the initialization of the main program module 10m by the monitoring program module 10w, these "parts" pay attention to the functions provided in the functional program module 10 and the functional program module 10 It is an abstract concept that classifies the program code of. Therefore, one program code may be classified into a plurality of "parts", and there may be a program code that is not classified into any of the "parts".

When the activation request detection unit 11 detects that the main program module 10m has requested activation, the activation request detection unit 11 activates the function providing unit 12.
The function providing unit 12 provides a predetermined function to the main program module 10m by executing a predetermined operation on the computer when activated. Further, when the function providing unit 12 operates, when a variable value is required or an operating condition needs to be specified, an argument indicating the variable value or the value for specifying the condition is detected as an activation request. The unit 11 acquires from the main program module 10 m and supplies it to the function providing unit 12.

When the function providing unit 12 starts, it outputs start information indicating that it has started to the start information output unit 13. If an argument is supplied from the activation request detection unit 11 at the time of activation, the argument is also output to the activation information output unit 13.
The start-up information output unit 13 outputs start-up information (and an argument if it exists) received from the function providing unit 12 at the time of start-up to the backup memory 21.

Further, when the function providing unit 12 is activated, the function providing unit 12 repeats an operation of reading data from the memory 20, executing a predetermined process on the read data, and storing the obtained data in the memory 20. A predetermined basic function is provided to the main program module 10 m. Then, when a predetermined operation for providing the function is completed, a message to that effect is output to the end information output unit 14.
When the end information output unit 14 receives from the function providing unit 12 that the operation has been completed, the end information output unit 14 outputs the end information indicating that the operation has been completed to the backup memory 21.

FIG. 5 conceptually shows the data structure of the backup memory 21 in which the functional program module 10 of this embodiment writes start information, end information, and the like. As shown in the figure, the backup memory 21 of this embodiment includes an operation history storage area 21a and an initialization status storage area 21b.
Of these, the operation history storage area 21a is an area for writing the above-mentioned start-up information, end information, and the like when the function program module 10 starts up or ends. Further, the initialization status storage area 21b includes information for identifying the functional program module 10 that was operating when the monitoring program module 10w described above initializes the main program module 10m using FIG. 1. This is the area for writing the operating status. As described above, the data written in the operation history storage area 21a and the initialization status storage area 21b are not deleted even if the main program module 10m is initialized.
Further, as shown in the drawing, the operation history storage area 21a is divided into a plurality of small areas, and each of them is given a unique address number. The operation history storage area 21a of this embodiment is divided into eight small areas with address numbers ad1 to ad8.

Since the application program 1 of this embodiment incorporates the above-mentioned functional program module 10, even if the main program module 10m is initialized by the monitoring program module 10w, the functional program module 10 having a bug can be easily implemented. It becomes possible to specify to.

B. Operation of function program module 10:
FIG. 6 shows a flowchart of the function providing process executed by the function program module 10. When the function program module 10 is started by the main program module 10m, the function program module 10 provides a predetermined function to the main program module 10m by executing this function providing process.

As shown in FIG. 6, the functional program module 10 first determines whether or not it has been started by the main program module 10m (S100). As a result, if it is not activated (S100: no), the same determination is repeated to enter a standby state until it is activated.
Then, when it is started by the main program module 10m, it is determined as "yes" in S100, and subsequently, the start information indicating that it has been started is stored in the operation history storage area 21a of the backup memory 21 (S101). ..

Here, as described above with reference to FIG. 5, the operation history storage area 21a is divided into a plurality of (8 in this case) small areas, and the address numbers ad1 to ad8 are assigned to each small area. ing. When writing data to the operation history storage area 21a, the functional program module 10 of this embodiment writes data to the small areas in order according to the order of the address numbers ad1 to ad8.
For example, if the data has not yet been written in the operation history storage area 21a, the data is written in the address number ad1 of the operation history storage area 21a. Further, if the data is written in the address number ad1 but the data is not yet written in the address number ad2, the data is written in the address number ad2.
Further, when the data is written in all the address numbers ad1 to ad8 of the operation history storage area 21a, the data is written in the address number in which the oldest data is written. For example, when data is written to address number ad8, the next data to be written is address number ad1, the next is address number ad2, the next is address number ad3, and so on. ..

Further, as described above with reference to FIG. 2, a plurality of functional program modules 10 are started in order, and each functional program module 10 writes data to the operation history storage area 21a of the backup memory 21. Therefore, if the previously activated functional program module 10 has written to, for example, the address number ad3 of the operation history storage area 21a, the activation information will be written to the address number ad4 in S101.

After writing the activation information to the operation history storage area 21a as described above (S101), it is determined whether or not the argument supplied from the main program module 10m exists (S102). As described above, the argument is a variable value required for the function program module 10 to provide a predetermined function, a numerical value such as a value that specifies the content of the function, an address value that stores the variable value or the numerical value, and an address. A numerical value such as a pointer value indicating a value. Some functional program modules 10 require arguments to be specified, some are not required but arguments can be specified, and some cannot specify arguments. When the main program module 10m starts the functional program module 10. , Provide arguments as needed.
Therefore, in S102, it is determined whether or not the argument supplied from the main program module 10m exists.

As a result, when the argument is not supplied (S102: no), the process for providing the basic function peculiar to the function program module 10 is started (S104).
On the other hand, when the argument is supplied (S102: yes), the argument is stored in the operation history storage area 21a of the backup memory 21 (S103) in the same manner as the above-described startup information. Since the number of arguments to be supplied is not necessarily one, when n arguments are supplied, those arguments are stored in the n address numbers of the operation history storage area 21a.
In this way, when the argument is written to the operation history storage area 21a of the backup memory 21 (S103), the process for providing the basic function peculiar to the function program module 10 is started (S104).

During the process for providing the unique function, a predetermined process is executed while reading data from the memory 20 (see FIG. 4) and writing data.
Subsequently, it is determined whether or not the process for providing the unique function is completed (S105), and if the process is not completed (S105: no), the process is continued as it is.
On the other hand, when the processing is completed (S105: yes), the fact that the provision of the function is completed is output to the main program module 10m (S106).

Subsequently, the end information indicating that the process for providing the function is completed is stored in the operation history storage area 21a of the backup memory 21 (S107). When storing the end information, the end information is stored in the address number where the oldest data is stored in the operation history storage area 21a, as in the case of storing the start information and arguments described above. For example, when the argument is stored in S103, the end information is stored in the address number next to the address number in which the argument is stored (in the case of the address number ad8, the address number ad1). If the argument is not stored in S103, the end information is stored following the address number in which the start information is stored in S101.
When the end information is written in the operation history storage area 21a of the backup memory 21 in this way, the function providing process of FIG. 6 ends.

As described above, the functional program module 10 of the present embodiment sends start information at startup, arguments when arguments are supplied, and end information at the end in the operation history storage area 21a of the backup memory 21. I am writing in series. Therefore, even if the monitoring program module 10w initializes the main program module 10m during the execution of the application program 1, the cause of the initialization can be easily identified by examining the backup memory 21.
In particular, in the application program 1 of this embodiment, the functional program module 10 writes start information, end information, and the like in the operation history storage area 21a of the backup memory 21 in chronological order. Therefore, as will be described in detail later, by examining the operation history storage area 21a, it is possible to know the status when each function program module 10 is started, so that the cause of the initialization by the monitoring program module 10w has occurred. Can be identified even more easily.

FIG. 7 illustrates how data is written to the operation history storage area 21a as the main program module 10m sequentially activates the function program module 10. Here, the main program module 10m will be described assuming that the functional program modules 10 are started in the order shown in FIG.
As described above with reference to FIG. 2, the main program module 10m first activates the functional program module 10a, and accordingly, the functional program module 10a is activated at the address number ad1 of the operation history storage area 21a. Information Ast is written. Further, the functional program module 10a uses one argument, and along with this, the argument Av of the functional program module 10a is written in the address number ad2 of the operation history storage area 21a. Further, when the function program module 10a ends its operation, the end information Aen of the function program module 10a is written in the address number ad3.

Further, the main program module 10m starts the functional program module 10b following the functional program module 10a (see FIG. 2). Along with this, the activation information Bst of the functional program module 10b is written in the address number ad4 of the operation history storage area 21a. Further, since the functional program module 10b uses two arguments, two arguments Bv1 and Bv2 are written in the address number ad5 and the address number ad6 of the operation history storage area 21a, and further, the operation history. The end information Ben of the functional program module 10b is written in the address number ad7 of the storage area 21a.

Subsequently, the main program module 10m activates the functional program module 10c. Along with this, the activation information Cst of the functional program module 10c is written in the address number ad8 of the operation history storage area 21a. Further, since the functional program module 10c does not use an argument, the end information Cen of the functional program module 10c is written in the address number ad1 of the operation history storage area 21a.
Similarly, every time the functional program module 10 is activated, the activation information of the functional program module 10 is written in the operation history storage area 21a, and if an argument exists, the argument is also written. Then, when the functional program module 10 ends, the end information of the functional program module 10 is written in the operation history storage area 21a.

Here, as described above with reference to FIG. 3, a case where the main program module 10m is initialized by the monitoring program module 10w during the operation of the functional program module 10d will be considered.
As described above, the contents stored in the backup memory 21 are not erased even if they are initialized. Therefore, the status storage area 21b at the time of initialization of the backup memory 21 is initialized in the same manner as the conventional application program 1. The operating status of the functional program module 10 that was operating at that time is recorded. Further, in the operation history storage area 21a, information written by the functional program module 10 before being initialized is recorded.

FIG. 8A shows the data stored in the operation history storage area 21a at the time of initialization. The shaded areas in the figure are the data written by the functional program module 10d that was operating when it was initialized (in this case, the activation information Dst and the argument Dv). As described above, the functional program module 10 writes data in the order of address numbers. Therefore, when the data shown in FIG. 8 (a) is rearranged in the order in which the data is written, the order is as shown in FIG. 8 (b).

As shown in FIG. 8B, the functional program module 10d that was operating at the time of initialization receives the argument Dv stored in the address number ad5 when it is started. Further, although the functional program module 10a is operating before the functional program module 10d is started, the end information Aen of the functional program module 10a is not stored in the operation history storage area 21a. That is, the functional program module 10a has not been normally terminated for some reason such as an interrupt, and the functional program module 10d is started in such a situation, so that the functional program module 10d cannot operate normally. Therefore, it is probable that initialization by the monitoring program module 10w has occurred.

Further, for the functional program module 10c that was operating before the functional program module 10a that caused the initialization in the functional program module 10d, the end information Cen of the functional program module 10c is stored. Therefore, it is considered that the functional program module 10c is normally terminated for the time being. From this, although the functional program module 10a was started in a normal state, it did not end normally for some reason, and the functional program module 10d was started in that state. Therefore, the operation of the functional program module 10d It is highly probable that initialization by the monitoring program module 10w occurred inside. Therefore, it is considered that the initialization occurred during the operation of the functional program module 10d, but it is the functional program module 10a that needs to be investigated for the existence of a bug in the program.

Alternatively, the functional program module 10d that was operating when the initialization occurred received the argument Dv at the time of startup, but this argument Dv may not be a normal value.
In such a case, the functional program module 10d does not have a program bug, but the main program module 10m that supplies the abnormal argument Dv to the functional program module 10d, or the functional program module 10a that caused the problem. It is considered that we should investigate whether there is a bug in.

In this way, the operation history of the functional program module 10 is stored in the operation history storage area 21a in chronological order. Therefore, when the initialization by the monitoring program module 10w occurs, it is possible to know the situation when the functional program module 10 is started. For example, it is possible to know whether or not the functional program module 10 that was operating before the functional program module 10 has been normally terminated, or whether or not a normal argument has been supplied at the time of startup.
If the function program module 10 that was operating at the time of initialization is not started in a normal state, it is not the function program module 10 at the time of initialization, but before the function program module 10. It is probable that there is a bug in the functional program module 10 that was running.

Further, if the operation history of the plurality of functional program modules 10 is stored as in the operation history storage area 21a of this embodiment, the function that was operating before the functional program module 10 in which the initialization occurred. It is also possible to know under what circumstances the program module 10 is started. As a result, if the functional program module 10 is not started in a normal state, it is considered necessary to investigate the existence of a bug in the functional program module 10 that was operating before that.

As described above, in the application program 1 of the present embodiment, the situation when the functional program module 10 is started is stored in the backup memory 21 which is not erased even if the main program module 10m is initialized. Therefore, even when the main program module 10m is initialized by the monitoring program module 10w, it is possible to easily identify the cause of the initialization.

Although the examples of the present invention have been described above, the present invention is not limited to the above-mentioned examples, and can be carried out in various modes without departing from the gist thereof.

1 ... Application program, 10a-10d ... Functional program module,
10m ... main program module, 10w ... monitoring program module,
11 ... Start request detection unit, 12 ... Function provision unit, 13 ... Start information output unit,
14 ... end information output unit, 20 ... memory, 21 ... backup memory,
21a ... Operation history storage area, 21b ... Initialization status storage area.

Claims (3)

An application program (1) that executes a predetermined target process on a computer.
A plurality of functional program modules (10), which are programs that realize individual functions used in the target processing, and
A main program module (10 m), which is a program that realizes the target processing by starting the plurality of functional program modules in a predetermined order, and
The execution time of the functional program module is monitored, and if the execution time does not exceed a predetermined upper limit time, specific information that can identify the running functional program module is stored in a predetermined backup memory (21). However, when the execution time exceeds the upper limit time, the specific information of the function program module being executed is stored in the backup memory. Along with this, a monitoring program module (10w), which is a program for initializing the main program module, is provided.
The functional program module is
The start-up information indicating that the function has been started and the end information indicating that the operation for realizing the function has been completed are stored in the backup memory in a time-series manner and in a state in which the function program module can be identified . If an argument has been received at startup, that argument is also stored in the backup memory.
When the start information or the argument or the end information is stored in the backup memory, if the start information or the argument or the end information of another functional program module is stored in the backup memory, the backup memory stores the start information or the argument or the end information. Following the start information or the argument or the end information of the other functional program module, the start information or the argument or the end information is stored , and further.
When the amount of data of the start information, the argument and the end information stored in the backup memory exceeds a predetermined upper limit amount, the new start is started in order from the old start information or the argument or the end information . An application program comprising overwriting information or said argument or said end information . The application program according to claim 1.
The monitoring program module stores the specific information in the initialization status storage area set in the backup memory.
The functional program module stores the start information, the argument, or the end information in an operation history storage area set in an area different from the initialization status storage area on the backup memory.
An application program characterized by that. A functional program module (10) that is started by an application program (1) that executes a predetermined target process on a computer and realizes a function used in the target process.
The startup information indicating that the application program has been started is output to the backup memory (21) whose stored contents are not erased even if the application program is initialized, and if an argument is received at the time of the startup, the argument is also included. , The startup information output unit (12) that outputs to the backup memory,
With the end information output unit (14) that outputs the end information indicating that the operation for realizing the function is completed to the backup memory.
With
When the start information output unit outputs the start information or the argument to the backup memory, the start information or the argument or the end information of another functional program module is output to the backup memory. Is to output the start information or the argument following the start information or the argument or the end information of the other functional program module.
When the end information output unit outputs the end information to the backup memory, if the start information or the argument of the other functional program module or the end information is output to the backup memory, the end information output unit may output the end information. The end information is output following the start information or the argument or the end information of the other functional program module.
When the amount of data of the start information or the argument or the end information stored in the backup memory exceeds a predetermined upper limit amount, the start information output unit and the end information output unit are old. Overwrites the new start information or the argument or the end information in order from the argument or the end information.
A functional program module characterized by that.

Images