JPH08249215A - Method for managing program operation information - Google Patents

Abstract

PURPOSE: To provide a method for managing program operation information capable of providing information relating to the activation environment of the program required so as to investigate the cause of the program which generates a fault, to a user at the time of operating and at the time of ending. CONSTITUTION: By providing a program information management table 61 on a shared memory 6 and incorporating a module for writing the information relating to the activation environment of the program 5 to the program information management table 61 inside a program control part 1, at the time of activating, operating and ending the program, the information specified by a dedicated function incorporated inside the program or the program control part 1 is preserved in the program information management table 61 and the preserved information is provided to the user.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a program operation information management method for managing information on a program startup environment at the time of program startup, operation and termination.

[0002]

2. Description of the Related Art FIG. 17 shows a conventional program operation described in "Design of UNIX Kernel" by Maurice J. Bach (Kyoritsu Shuppan Co., Ltd., Oct. 5, 1990, pp. 20-29). It is a block diagram which shows the management method of information, 1 is a program control part which starts and controls a program, 11 stores the information regarding the program which the program control part 1 is currently controlling, and the transition of the state of a program And a program table whose contents are changed, 2 is an input unit for receiving an input from a user, 3 is a display unit for presenting information to the user, 4 is a program table for the program control unit 1
The program control unit 1 issues a request to present the contents of
When the contents of the program table 11 are output in response to the request, the program information display program 5 for outputting the contents to the display unit 3 is a program currently in operation.

Next, the operation will be described. The program control unit 1 stores information (program number, size of the program 5, execution time, etc.) regarding the program 5 at the time of starting the program 5 in the program table 11, and in the process of controlling the program 5, the state of the program 5 When a change occurs in the, the contents of the program table 11 are changed. When there is a request from the user to acquire information regarding the state of the program 5 via the input unit 2, the program control unit 1 activates the program information display program 4. The program information display program 4 knows what information the user wants via the input unit 2 and issues an information provision request to the program control unit 1 based on the information. Upon receiving the request, the program control unit 1 gives the information stored in the program table 11 to the program information display program 4. The program information display program 4 devises the display so that it is easy for the user to see, and outputs information to the display unit 3.

[0004]

Since the conventional method of managing program operation information is configured as described above, the program control unit 1 saves in the program table 11 among the information on the program 5 currently in operation. The information that has been obtained can be obtained by issuing a request to the program control unit 1, but the cause of the failure of the running program 5 is sought from among the information that the program control unit 1 does not store in the program table 11. Any information needed by the user for this purpose, such as the absolute path of the failing program 5, the version, the compile options when the program was created,
There is a problem that it is not possible to centrally manage the program 5 starter, the start time, the file opened by the program 5, the absolute path of the core file, etc., and it takes time to retrieve and acquire such information. there were.

If the program 5 fails and is abnormally terminated, the information about the program 5 disappears from the program table 11. Therefore, the information about the failed program 5 is sent from the program control unit 1 after the failure. In addition, the information about the program 5 cannot be centrally managed when the program 5 is operating after the program operation ends, and thus the information about the terminated program 5 is lost. There was a point.

The present invention has been made in order to solve the above problems, and the user can arbitrarily specify the information regarding the program startup environment necessary for investigating the cause of the faulty program. It is an object of the present invention to obtain a method of managing program operation information that can be provided to the user.

It is another object of the present invention to provide a program operation information management method capable of speedily searching information by centrally managing information related to a program activation environment.

A further object of the present invention is to obtain a program operation information management method capable of acquiring information on the boot environment of a program that has abnormally ended due to a failure even after the program operation has ended.

[0009]

According to a first aspect of the present invention, there is provided a method for managing program operation information, which stores information on a program startup environment in an information management area on a shared memory at the time of startup, and during operation and termination of the program. The information provided later is provided upon request.

In the method for managing program operation information according to the second aspect of the present invention, by calling a dedicated function provided in the program, arbitrary information about the program provided by the user is provided as information about the boot environment in the information management area. It is to be stored in.

According to a third aspect of the present invention, there is provided a method for managing program operation information, wherein when a compiler generates an executable program from a source program, compile information such as a compile option is embedded in the executable program to provide information about a boot environment. The compilation information is stored in the information management area.

According to a fourth aspect of the present invention, there is provided a program operation information management method, wherein information that cannot be stored in an executable program is stored in an information management area as information about a boot environment.

According to a fifth aspect of the present invention, there is provided a program operation information management method, wherein information about access is stored in an information management area as information about a boot environment.

According to a sixth aspect of the present invention, there is provided a program operation information management method, in which the storage of information related to a program activation environment is stopped in response to a user selection or a program selection.

[0015]

According to the first aspect of the present invention, there is provided a program operation information management method, wherein information about a boot environment is stored in an information management area on a shared memory when a program is started, and the stored information is stored in a reference program during or after the program is running. By presenting the information so that it can be referred to, it becomes possible to quickly search for information on the boot environment at the time of starting the program and to obtain the information on the program even after the program ends.

According to a second aspect of the present invention, there is provided a program operation information management method, wherein a program special function for storing arbitrary information about a program in an information management area is called from the program to determine the cause of the program failure. It is possible for the user to arbitrarily specify the information that the user has determined necessary.

According to a third aspect of the present invention, a program operation information management method embeds compile information such as compile options into an executable program when the compiler generates an executable program from a source program.
By storing the information embedded at the time of starting the program in the information management area, it is possible to quickly obtain the information at the time of program generation from the program in which the failure has occurred.

According to a fourth aspect of the present invention, there is provided a program operation information management method, including a program start date / time, a program starter, information on a started executable program, and information on a core file generated when the program is abnormally terminated. By storing the information that cannot be stored in the executable program in the information management area, it becomes possible to quickly obtain such information.

According to a fifth aspect of the present invention, there is provided a method for managing program operation information, wherein information on files opened by the program during operation of the program, information on other programs running the program, and access by the program. By storing the information regarding the access such as the information about the existing device driver in the information management area, it is possible to quickly obtain the information.

According to a sixth aspect of the present invention, there is provided a method for managing program operation information, wherein information about a boot environment is stopped from being saved in accordance with a selection made by a user or a program. It is possible to reduce the overhead during the operation of a program that needs to reduce the overhead due to saving.

[0021]

【Example】

Example 1. An embodiment of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing a method of managing program operation information according to an embodiment of the present invention.
1 is a program control unit for activating and controlling a program, 1
Reference numeral 1 denotes a program table that stores information about the activation environment of the program currently controlled by the program control unit 1 and whose contents are changed as the state of the program changes, 12
Is a management table entry section for writing information on the program activation environment in a program information management table described later, 2 is an input section for receiving an input from a user, 3 is a display section for outputting information provided to the user, and 6 is a program control section 1. Not only the shared memory, which is a memory area on the software that can be referred to and written in if the general program is given access right, 61 is provided on the shared memory 6.
Information on the boot environment can be saved in a predetermined format when the program is started, and a program information management table (information management area) writable and readable by not only the program control unit 1 but also any other program having an access right, 4 Is a program information display program for reading information stored in the program information management table 61 in accordance with a user's request and devising a display so that it is easy for the user to see, and 5 is a program in operation. As described above, FIG. 1 shows a structural relationship between software and hardware for realizing the program operation information management method according to this embodiment. Information on the boot environment of the program 5 is shared by the shared memory when the program is started. 6 shows a mechanism in which the stored information is stored in the program information management table 61 and the stored information can be referred to during and after the program operation.

FIG. 2 is a diagram showing the format of the program information management table 61 on the shared memory 6. In the figure, 611 is a unit for storing information, an information entry consisting of five areas, and 6111 is an information entry. A program number storage area that is located first in 611 and stores a program number, 6112 is an entry length storage area that is located second in information entry 611 and stores the length of information entry 611, and 6113 is an information entry Third of 611
An information type storage area, which is located at the fourth position and stores the length of information related to the startup environment of the program 5, 6114 is an information type which is located at the fourth position of the information entry 611 and stores the type of information related to the startup environment of the program 5. Storage area, 611
An information content storage area 5 is located at the fifth position of the information entry 611 and stores information related to the boot environment of the program 5. A plurality of information entries 611 are arranged in the program information management table 61 with a variable length.

The information about the activation environment of the program 5 stored in the information content storage area 6115 is, for example, arbitrary information about the program 5 provided by the user, compilation information such as compile options, and the program 5.
Information that cannot be saved in the executable program, such as the startup date and time, the startup person, the absolute path of the started executable program, the absolute path of the core file that is generated when the program 5 terminates abnormally, while the program 5 is running Program 5
Is the information related to the access such as the absolute path of the file opened by the program, the absolute path and name of the other program running the program, and the absolute path and name of the device driver accessed by the program. Information type storage area 611 as the type of information
Stored in 4.

Next, the operation will be described. FIG. 3 is a flowchart showing the flow of processing of the program operation information management method, and the operation will be described below with reference to this flowchart.

The program control section 1 proceeds to step ST11.
First, before starting the program 5, the program 5 is numbered, and the secured number is stored in the program table 11 as the program number. Further, in step ST12, the program control unit 1 starts the program 5 that is started before the program 5 is started.
To obtain information about the boot environment as described above.

Next, the program control unit 1 executes step S
At and after T13, the information acquired above is stored in the program information management table 61 before the first program is started. In step ST13, the program control unit 1 writes the program number in the program number storage area 6111 of the same information entry 611 as shown in FIG. In step ST14, the program control unit 1 calculates the information entry length and writes the calculated value in the entry length storage area 6112 of the same information entry 611. In step ST15, the program control unit 1 calculates the information length and uses the calculated value as the same information entry 6
11 in the information length storage area 6113. In step ST16, the program control unit 1 writes the type of information in the information type storage area 6114 of the same information entry 611. In step ST17, the program control unit 1 writes the information content in the information content storage area 6115 of the same information entry 611. In step ST18, the program control unit 1 confirms whether or not there is further information to be written, and if there is information, returns to step ST13, and if not, proceeds to step ST19. Finally, in step ST19, the program control unit 1 writes a value indicating that there is no information thereafter in the program number storage area 6111 of the next information entry 611. The program control unit 1 repeats the above-described operations from steps ST13 to ST19 to store a plurality of information in the program information management table 61 on the shared memory 6.

Next, the operation of presenting information on the activation environment of the program 5 to the user in response to a request from the user or the like will be described. FIG. 4 is a flow chart showing the flow of processing in which the program information display program 4 acquires information regarding the program number n from the program information management table 61. In step ST21, when the program information display program 4 is started, the program number n specified by the user is read via the input unit 2 at the time of starting. In step ST22, the program information display program 4 opens the program information management table 61 on the shared memory 6.

Next, the program information display program 4
Retrieves information about the program number n from step ST23 onward. In step ST23, the pointer is moved to the read position (the initial value of the pointer is 0, which indicates the beginning of the program information management table 61). In step ST24, the program number m is first read from the program number storage area 6111 of the top information entry 611. Then, in step ST25, the read program number m is the information entry 6
It is determined whether or not the value indicates the end of 11.

If the program number m read in step ST25 is not a value indicating the end of the information entry 611, the process proceeds to step ST26. In step ST26, it is determined whether or not the read program number m is the same as the program number n designated by the user, and if it is the same, information is read out in step ST27.
Go to. On the other hand, if they are not the same, the process proceeds to step ST28 to calculate the value of the next pointer. In step ST27, the contents of the information type storage area 6114 and the information content storage area 6115 of the information entry 611 corresponding to the program number n are read out and stored in the area inside the program information display program 4. On the other hand, in step ST28, the entry length storage area 6
The value of the pointer to the next information entry is calculated by adding the value of the entry length acquired from 112 to the value of the current pointer, and the process returns to step ST23. As a result, the processes of steps ST23 to ST28 are repeated until the information entry 611 corresponding to the program number n is found.

If the program number m read in step ST25 is a value indicating the end of the information entry 611, the process proceeds to step ST29. In step ST29, the information acquired so far is appropriately processed and displayed. The program information saving step is shown in FIG.
4 corresponds to steps ST11 to ST19, and the program information presentation step corresponds to steps ST21 to ST29 in FIG.

As described above, according to this embodiment,
When the program 5 is started, the information about the boot environment is centrally stored in the program information management table 61 on the shared memory 6, so that the information can be searched quickly.
The time for investigating the cause of a failure can be shortened. Also,
Since the information about the boot environment remains stored in the program information management table 61 even after the program 5 ends, it is possible to obtain the information about the boot environment of the failed program 5 after the program 5 ends. By retrieving such information at any time later, the cause of the failure can be investigated when necessary.

Example 2. FIG. 5 is a block diagram showing a method of managing program operation information according to another embodiment of the present invention. In the figure, the same reference numerals as those in FIG. 1 are the same or corresponding components, and the description thereof will be omitted. . Thirteen
Is provided in the program control unit 1 and acquires the start address of the in-program information storage area provided in the program 5 from the address notification unit also provided in the program 5, 51 Is an in-program information storage area for storing information about the program 5 that the user arbitrarily wrote when creating the program 5, 52 is an address notifying section for informing the in-program address acquisition section 13 of the start address of the in-program information storage area 51. Is. As described above, FIG. 5 shows a structural relationship between software and hardware for realizing the program operation information management method according to this embodiment. The program is provided with a dedicated address notification unit 52 and the like. This is a mechanism for storing arbitrary information about the program 5 in the program information management table 61 by starting it in the program 5.

Next, the operation will be described. FIG. 6 is a flowchart showing the flow of processing of the program operation information management method according to this embodiment, and the operation will be described below with reference to this flowchart.

In step ST31, the program 5
The address notifying unit 52 is activated by calling a dedicated function in the. In step ST32, the address notification unit 52 gives the head address of the in-program information storage area 51 in the program 5 to the in-program address acquisition unit 13 in the program control unit 1. Next, in step ST33, the in-program address acquisition unit 13 gives the acquired address to the management table entry unit 12. In step ST34, the management table entry unit 12 acquires the program information arbitrarily written by the user from the in-program information storage area 51 in sequence based on the given address, and in step ST35, the flowchart of FIG. According to the processing of steps ST13 to ST19, the program information is written in the program information management table 61 on the shared memory 6. The details of this processing are the same as those in the first embodiment, and therefore the description thereof is omitted.

The program information written in the program information management table 61 on the shared memory 6 is acquired by the program information display program 4 and displayed on the display unit 3 in accordance with the process shown in the flowchart of FIG. it can. The details of this processing are the same as those in the first embodiment, and therefore the description thereof is omitted.

Example 3. FIG. 7 is a block diagram showing a method of managing program operation information according to another embodiment of the present invention. In the figure, the same reference numerals as those in FIG. 1 are the same or corresponding components, and the description thereof will be omitted. . 72
5 is an executable program in which compilation information such as compile options at the time of compilation is embedded; 7251 is compile information such as compile options; 14 is compile information 725 from the executable program 725 when the program control unit 1 starts the executable program 725.
This is a compilation information acquisition unit for extracting 1. As described above, FIG. 7 shows a structural relationship between software and hardware for realizing the program operation information management method according to this embodiment, and when the executable program 725 generated by the compiler is started up, , Compilation information 72 embedded in the executable program 725
5 shows a mechanism for storing 51 in the program information management table 61 on the shared memory 6.

Next, a mechanism for embedding the compile information 7251 such as a compile option in the executable program 725 when the compiler generates the executable program 725 from the source program will be described. FIG.
Is a block diagram showing the structure of the mechanism, and in the figure, 2 is an input unit, which is equivalent to that designated by the same reference numeral in FIG. Reference numeral 7 is a compiler that controls the process of sequentially activating programs such as the embedded preprocessors described below to create an executable program 725 from a source program, and 711 is a work file 722 that stores the compile options given to the compiler 7 from the input unit 2. The embedded preprocessor 712 to be embedded in the file is started by the compiler 7 and performs header file processing, macro expansion, etc., to change the work file 722 to the intermediate file 723.
Is a standard preprocessor for creating
And a code generator 714 for generating an object program 724 which is a machine language instruction sequence from the intermediate file 723 is activated by the compiler 7,
This is a linker for creating an executable program 725 by linking a standard library (not shown) with the object program 724.

Next, the operation will be described. Here, first, compile information 7251 such as compile options.
The operation of embedding the program in the executable program 725 will be described. FIG. 9 is a flowchart showing the flow of the processing.

In step ST41, the compiler 7
Is started, and the compiler 7 is given a compile option for specifying the path name of the source program 721 and the compile behavior. In step ST42, the compiler 7 embeds the same path name and compile option as those given to itself, and embeds the preprocessor 711.
The embedded preprocessor 711 is activated.
In step ST43, the embedded preprocessor 7
11 writes an information start pattern, a compile option, and an information end pattern in the work file 722. Further, the contents of the source program 721 are added to this. In step ST44, the compiler 7 activates the standard preprocessor 712. From this point onward, the processing is the same as normal compiler processing. That is, in step ST45, the standard preprocessor 712 performs header file processing, macro expansion, etc. to create the intermediate file 723. In step ST46, the compiler 7 activates the code generator 713. In step ST47, the code generator 713 causes the intermediate file 72
Object program 72 which is a machine language instruction sequence from 3
4 is generated. In step ST48, the compiler 7 activates the linker 714. In step ST49, the linker 714 links the object program 724 with necessary modules from a standard library or the like to create an executable program 725. By such processing, the compile information 7251 such as compile options
Embedded in the executable program 725. The compilation information embedding step is step ST41 in FIG.
To ST49.

Next, the operation of writing the compile information 7251 in the program information management table 61 will be described. FIG.
Reference numeral 0 is a flow chart showing the flow of the processing, and the operation will be described below with reference to this flow chart.

In step ST51, when the program control unit 1 is requested to start the executable program 725, in step ST52 the compile information acquisition unit 14 of the program control unit 1 executes the executable program 725.
Open. Then, in step ST53,
The compilation information acquisition unit 14 uses the executable program 725.
While searching for the information start pattern. If the information start pattern is not found, the process proceeds to step ST58,
The executable program 725 is loaded into the memory and normal activation and control are started. On the other hand, when the information start pattern is found, the process proceeds to step ST54, and the written compile information 7251 is read. Next, step S
At T55, the information end pattern is searched. If the information end pattern is not found, the process proceeds to step ST58, the executable program 725 is loaded into the memory, and normal activation and control are started. On the other hand, when the information end pattern is found, the process proceeds to step ST56, the compilation information acquisition unit 14 activates the management table entry unit 12, and gives the compilation information 7251 acquired by the above operation to the management table entry unit 12. Next, in step ST57, the management table entry unit 12 writes the compile information 7251 into the program information management table 61 in accordance with the processing of steps ST13 to ST19 in the flowchart of FIG. 3 of the first embodiment. The details of this processing are the same as those in the first embodiment, and therefore the description thereof is omitted.

The information written in the program information management table 61 on the shared memory 6 can be acquired by the program information display program 4 according to the processing of the flowchart of FIG. 4 of the first embodiment. The details of this processing are the same as those in the first embodiment, and therefore the description thereof is omitted.

As described above, according to this embodiment,
Since the compile information 7251 at the time of generating the executable program 725 of the program 5 that has ended due to a failure can be obtained even after the program 5 is finished, for example, a defect due to optimization at the time of compile can be detected.

Example 4. FIG. 11 is a block diagram showing a program operation information management method according to another embodiment of the present invention. In the figure, the same reference numerals as those in FIGS. Is omitted. Reference numeral 15 indicates the start date and time of the program 5, the starter, the relative path of the started executable program 725, and the program 5 abnormally ended for each of the operating programs 5 which the program control unit 1 has started and is currently controlling. Information such as the relative path of the core file generated at this time is written in the program table 11 as necessary and maintained. The program table maintenance unit 16 acquires the absolute path from the relative path of the executable program 725 and the core file. It is an absolute path acquisition unit that does. Thus, FIG.
Reference numeral 1 shows the structural relationship of software and hardware for realizing the program operation information management method according to this embodiment. The start date and time of the program 5, the starter, and the absolute path of the started executable program 725. ,
It shows a mechanism for saving information that cannot be saved in the executable program 725, such as the absolute path of the core file generated when the program 5 terminates abnormally, in the program information management table 61 at the time of starting and operating the program. is there.

Next, the operation will be described. FIG. 12 is a flow chart showing the flow of processing of the program operation information management method according to this embodiment. The operation will be described below with reference to this flow chart.

In step ST61, when the program control unit 1 receives a request to start the executable program 725 from the input unit 2, in step ST62 the program table maintenance unit 15 is started, and the start date and time of the program 5, the starter, The relative path etc. of the executable program 725 is entered in the program table 11. Then, in step ST63, the program control unit 1 activates the management table entry unit 12. In step ST64, the management table entry unit 12 performs the above-mentioned operation and the program table maintenance unit 1
The information entered by 5 is obtained from the program table 11. Next, in step ST65, the program control unit 1 activates the absolute path acquisition unit 16 to convert the relative path of the information acquired from the program table 11 into an absolute path. And
In step ST66, the management table entry unit 12 writes the information converted into the absolute path in the program information management table 61 according to the processing of steps ST13 to ST19 in the flowchart of FIG. 3 of the first embodiment. The details of this processing are the same as those in the first embodiment, and therefore the description thereof is omitted.

Next, in step ST67, the program table maintenance section 15 determines in step ST if the information about the program 5 being controlled requires maintenance.
Returning to step 62, the program table maintenance unit 15 is started again, the starting date and time of the program 5, the starter, the relative path of the executable program 725, etc. are entered in the program table 11, and the processes of steps ST63 to ST66 are repeated. On the other hand, if there is no need for maintenance, step ST
Proceed to 68 and stand by until maintenance is required.

The information written in the program information management table 61 on the shared memory 6 can be acquired by the program information display program 4 according to the processing of the flowchart of FIG. 4 of the first embodiment. The details of this processing are the same as those in the first embodiment, and therefore the description thereof is omitted.

As described above, according to this embodiment,
Information that cannot be stored in the executable program 725, such as the start date and time of the program 5, the starter, the absolute path of the started executable program 725, the absolute path of the core file generated when the program 5 abnormally terminates, etc. Since the information can be stored in the program information management table 61 when the program 5 is started up and operated, when the cause of the failure of the program 5 is at the time of starting the program, it is possible to prevent the loss of information related to the failure.

Example 5. FIG. 13 is a block diagram showing a method of managing program operation information according to another embodiment of the present invention. In the figure, the same reference numerals as those in FIG. 1 are the same or corresponding components, and their explanations are omitted. . 1
A file access unit 7 is provided in the program control unit 1 and opens the file by checking whether the specified file exists when the program 5 requests the file access or whether or not there is an access right. 531
Is provided in the program 5, and a file open unit 532 is provided in the program 5 for designating the relative path of the file and requesting the program control unit 1 to open the file. A file closing unit 8 requested to the program control unit 1 is an arbitrary file stored in an auxiliary storage device (not shown). As described above, FIG. 13 shows a structural relationship between software and hardware for realizing the program operation information management method according to this embodiment, and the files opened by the program 5 while the program 5 is operating. 8 absolute path, name and absolute path of another program running program 5, program 5
6 shows a mechanism capable of storing the name and absolute path of the device driver accessed by the program information management table 61.

Next, the operation will be described. FIG. 14 is a flow chart showing the flow of processing of the program operation information management method according to this embodiment.

When the file open unit 531 in the program 5 is activated in step ST711, the file open unit 531 specifies the relative path of the file 8 to be opened and the open mode such as reading and writing in step ST721. The file access unit 17 of the program control unit 1 is requested to open the file 8. In step ST73, the program control unit 1 activates the absolute path acquisition unit 16 and converts the relative path of the file 8 into an absolute path. In step ST74, the file access unit 17 searches the file 8 in the auxiliary storage device to check whether it can be opened. If it can be opened, the process proceeds to step ST751, and if it cannot be opened, the process proceeds to step ST752. In step ST751, the file access flag is set to "success". On the other hand, in step ST752, the file access flag is set to "failure". Then, it progresses to step ST76.

On the other hand, when the file 8 which has already been opened is closed, when the file closing unit 532 in the program 5 is started in step ST712,
In step ST722, the file close unit 53
2 requests the file access unit 17 of the program control unit 1 to close the opened file 8. And
In step ST753, the file access unit 17
Sets the file access flag to "closed". Then, it progresses to step ST76.

Next, in step ST76, the management table entry unit 12 writes the file access flag and the absolute path of the file 8 in the program information management table 61 in accordance with the processing of steps ST13 to ST19 in the flowchart of FIG. . Also, if necessary, the absolute paths and names of other running programs and the absolute paths and names of device drivers are also written. The details of this processing are the same as those in the first embodiment, and therefore the description thereof is omitted.

Then, in step ST77, it is determined whether the operation is an open request or a close request for the file 8. If the operation is open, the process proceeds to step ST781, and if it is closed, the process proceeds to step ST782. In step ST781, the file access unit 17 returns to the file open unit 531 in the program 5 whether or not the open was successful as a file identifier. On the other hand, in step ST782, the file access unit 17 returns to the file closing unit 532 in the program 5 whether or not the file is closed as a return value.

The information written in the program information management table 61 on the shared memory 6 can be acquired by the program information display program 4 according to the processing of the flowchart of FIG. 4 of the first embodiment. The details of this processing are the same as those in the first embodiment, and therefore the description thereof is omitted.

As described above, according to this embodiment,
The absolute path and name of the file 8 opened by the program 5 while the program 5 is operating, the absolute path and name of another program running the program 5, and the absolute path and name of the device driver accessed by the program 5 Since it can be stored in the program information management table 61, when the cause of the failure of the program 5 is the access of the file 8 or the like, the loss of the information can be prevented.

Example 6. FIG. 15 is a block diagram showing a method of managing program operation information according to another embodiment of the present invention. In the figure, the same reference numerals as those in FIG. 1 are the same or corresponding components and their explanations are omitted. . 6
2 is a program information management table 61 by the management table entry unit 12
Storing in the shared memory 6 for instructing whether to write (ON) or not (OFF) writing information on the activation environment of the program 5 (various kinds of information described in the second to fifth embodiments) to the Information writing control flag 58, ON / O of information writing control flag 62
A flag ON / OFF program for performing FF, 54 is a flag ON / OFF unit that can be activated in the program 5 and turns ON / OFF the information writing control flag 62. The program operation information management method according to this embodiment sets the information write control flag 62 on the shared memory 6 to 0.
By turning N / OFF, the above-described second to fifth embodiments
The information about the activation environment of the program 5, which is described in the method for managing program operation information by the above, can be saved or not saved. Therefore, FIG. 15 shows only the configuration of software and hardware relating to this embodiment, and the mechanism for storing the information described in the program operation information management method according to the above-mentioned Embodiments 2 to 5 is omitted. are doing.

Next, the operation will be described. FIG. 16 is a flow chart showing the processing flow of the program operation information management method according to this embodiment.

In step ST81, when the program control unit 1 activates the management table entry unit 12, step ST
At 82, the management table entry unit 12 reads the contents of the information writing control flag 62. In step ST83, if the content of the information writing control flag 62 is ON, the process proceeds to step ST84 and the information writing control flag 62
If the content of is OFF, the process ends. Step ST
In 84, the information about the activation environment of the program 5 is written in the program information management table 61 according to the processing of steps ST13 to ST19 of the flowchart of FIG. 3 of the first embodiment. The details of this processing are the same as those in the first embodiment, and therefore the description thereof is omitted.

The information write control flag 62 is turned on.
/ OFF is performed by the flag ON / OFF program 58 or the flag ON / OFF unit 54 activated in the program 5. The flag ON / OFF program 58 is turned on / off by the information writing control flag 62 specified by the user via the input unit 2. Also, flag O
The information write control flag 62 is turned ON / OFF at an arbitrary point during program operation by activating the N / OFF section 54 at an arbitrary point in the program 5.

The information about the boot environment of the program 5 written in the program information management table 61 on the shared memory 6 can be acquired by the program information display program 4 according to the processing of the flowchart of FIG. The details of this processing are the same as those in the first embodiment, and therefore the description thereof is omitted.

As described above, by turning on / off the information writing control flag 62 on the shared memory 6, arbitrary information about the program 5, compilation information such as compile options, information that cannot be saved in the executable program, And, when the program 5 does not need to save the information about the file 8 or other programs that are opened and started, or the overhead caused by saving this information, the overhead is reduced when the program 5 operates. it can.

[0064]

As described above, according to the first aspect of the present invention, the information on the activation environment of the program is saved in the information management area on the shared memory at the time of activation, and according to the request during and after the operation of the program. Since it is configured to provide the stored information, the information can be searched quickly, and the time for investigating the cause of the failure can be shortened. In addition, since the information remains stored in the information management area even after the program ends, it is possible to obtain the information related to the boot environment of the failed program even after the program ends, and to retrieve the necessary information at any time later. ,
It is effective in investigating the cause of the program failure when necessary.

According to the second aspect of the present invention, since the arbitrary information regarding the program provided by the user as the information regarding the boot environment is stored in the information management area, the user can determine the cause of the program failure. The user can arbitrarily specify the information determined to be necessary,
This has the effect of preventing omission of information that may be the cause of a failure.

According to the third aspect of the invention, when the executable program is generated from the source program by the compiler, the compile information such as the compile options is embedded in the executable program, and the compile information is used as the information about the boot environment. Since the configuration is such that the program is stored in the file, it is possible to prevent the loss of the information when the cause of the program failure is when the executable program is generated.

According to the fourth aspect of the invention, the information that cannot be stored in the executable program is stored in the information management area as the information about the boot environment. Therefore, when the cause of the program failure is at the time of booting the program. There is an effect that the omission of the information can be prevented.

According to the fifth aspect of the present invention, since the information related to the access of the started program is stored in the information management area as the information about the start environment, when the cause of the program failure is the file access. There is an effect that the omission of the information can be prevented.

According to the invention of claim 6, the storage of the information on the startup environment is stopped in accordance with the selection by the user or the program, so that it is not necessary to store the information on the startup environment of the program. Also, there is an effect that the overhead can be reduced at the time of operating a program that needs to reduce the overhead due to saving information.

[Brief description of drawings]

FIG. 1 is a block diagram showing a method of managing program operation information according to an embodiment of the present invention.

FIG. 2 is a diagram showing a format of a program information management table used in the program operation information management method shown in FIG.

FIG. 3 is a flowchart showing a flow of a process of acquiring and storing information about a program activation environment in the program operation information management method shown in FIG.

FIG. 4 is a flowchart showing a flow of a process of displaying information about a boot environment in the program operation information management method shown in FIG.

FIG. 5 is a block diagram showing a method of managing program operation information according to another embodiment of the present invention.

FIG. 6 is a flowchart showing a processing flow of a program operation information management method shown in FIG.

FIG. 7 is a block diagram showing a method of managing program operation information according to another embodiment of the present invention.

8 is a block diagram showing a method of embedding compile information in an executable program in the method of managing program operation information shown in FIG.

9 is a flowchart showing a processing flow of the compilation information embedding method shown in FIG.

10 is a flowchart showing a processing flow of the program operation information management method shown in FIG.

FIG. 11 is a block diagram showing a method of managing program operation information according to another embodiment of the present invention.

FIG. 12 is a flowchart showing a processing flow of a program operation information management method shown in FIG. 11.

FIG. 13 is a block diagram showing a method of managing program operation information according to another embodiment of the present invention.

FIG. 14 is a flowchart showing a processing flow of the program operation information management method shown in FIG.

FIG. 15 is a block diagram showing a method of managing program operation information according to another embodiment of the present invention.

16 is a flowchart showing a processing flow of a program operation information management method shown in FIG.

FIG. 17 is a block diagram showing a conventional method of managing program operation information.

[Explanation of Codes] 6 shared memory, 8 files, 61 program information management table (information management area), 7 compiler, 721 source program, 725 executable program, 725
1 Compilation information.

Claims (6)

[Claims] 1. A program information storage step of storing information on a boot environment of the program in an information management area on a shared memory when the program is started, and the program information storage step stored upon request during and after the operation of the program. A method for managing program operation information for executing a program information providing step for providing information. 2. In the program information storage step, by calling a dedicated function provided in the program, any information regarding the program provided by the user as the information regarding the boot environment is stored in the information management area. The method for managing program operation information according to claim 1, wherein: 3. When generating an executable program from a source program of the program by a compiler,
A compile information embedding step of embedding compile information such as a compile option in the executable program is executed, and the compile information is saved in the information management area as the information about a boot environment in the program information saving step. The method for managing program operation information according to claim 1 or 2. 4. In the program information storage step, the executable information such as a start date and time of the program, a person who started the program, information about a started executable program, and information about a core file generated when the program ends abnormally. 4. The program operation information management method according to claim 1, wherein information that cannot be stored in a program is stored in the information management area as the information related to a boot environment. 5. In the program information storage step, information on files opened by the program during operation of the program, information on other programs running the program, and access by the program. The management of the program operation information according to claim 1, wherein information regarding access such as information regarding a device driver is stored in the information management area as the information regarding a boot environment. Method. 6. The program information storage step according to claim 1, wherein the storage of the information on the boot environment is stopped in accordance with a selection made by the user or the program. The method for managing program operation information according to item 1.