WO2018158906A1 - Process data recording device and process data recording program - Google Patents

Abstract

A process management unit (23) of a process data recording device (10) generates a fork process (32) that is a fork of a process (31) from which process data is acquired. A dump acquisition unit (21) of the processor data recording device (10) reads process data pertaining to the fork process (32) generated by the process management unit (23) as process data pertaining to the process (31) from which process data is acquired and outputs same as dump data (42).

Description

Process data recording apparatus and process data recording program

This invention relates to a technique for acquiring and storing process data.

In response to an event such as occurrence of an abnormality, there has been a data collection technique in which an operating system stops process operation and collects process data that is data used by a running process.
For example, a UNIX (registered trademark) operating system has a function of outputting memory information called a core dump when an abnormality occurs (see Non-Patent Document 1).

Patent Document 1 describes that execution information such as a time and a function name of a dynamic library function is acquired when a dynamic library is called. Thereby, in patent document 1, the information of the process in process is collected, without stopping a process.

JP-A-8-147199

Norman Matloff (Author), Peter Salzman (Author), Aikawa Aizo (Translation), "Practical Debugging Techniques-Debugging with GDB, DDD, Eclipse" O'Reilly Japan, published on June 8, 2009, p. 124-127

In the conventional data collection technology, the process data is acquired at a specific timing after the process is stopped at a specific timing so that the process data in the memory is not updated. In the conventional data collection technology, it is not possible to acquire process data at a specific timing while the process is being executed.
In the conventional data collection technology, since it is necessary to acquire process data after stopping the process, the scenes in which the process data can be acquired are limited during the operation of the system. As a specific example, in the case of a conventional data collection technique, when a process cannot be operated due to an abnormality, the process is stopped and the process data is acquired before the process is terminated. However, with this method of use, only process data immediately before the occurrence of an abnormality can be acquired. The cause of the abnormality is not always related to the previous operation. For this reason, this usage may not be able to identify the cause of the occurrence of an abnormality.

In the method described in Patent Document 1, information on library calling can be acquired while the process is being executed. However, the method described in Patent Document 1 cannot acquire information inside the process such as variables used by the process. For this reason, the cause of the abnormality may not be identified.

An object of the present invention is to make it possible to acquire process data at a specific timing while executing a process.

The process data recording apparatus according to the present invention is:
A process management unit that creates a fork process by copying a target process for obtaining process data, and operates the fork process separately from the target process;
A dump acquisition unit that reads out process data for the fork process generated by the process management unit as process data for the target process and stores the process data as dump data;

In the present invention, a fork process that is a fork of a process for which process data is acquired is generated, and process data about the fork process is acquired. Therefore, process data can be acquired without stopping the target process.

1 is a configuration diagram of a process data recording apparatus 10 according to a first embodiment. 3 is a flowchart of the operation of the process data recording apparatus 10 according to the first embodiment. FIG. 3 is a configuration diagram of a process data recording apparatus 10 according to a second embodiment. FIG. 6 is a configuration diagram of a process data recording apparatus 10 according to a third embodiment. 10 is a flowchart of an operation when an acquisition condition is set in the acquisition condition information 43 according to the third embodiment. FIG. 10 is a flowchart of operations when referring to acquisition condition information 43 according to Embodiment 3. FIG. FIG. 6 is a configuration diagram of a process data recording apparatus 10 according to a fourth embodiment. 10 is a flowchart of the operation of the process data recording apparatus 10 according to the fourth embodiment. FIG. 6 is a configuration diagram of a process data recording apparatus 10 according to a fifth embodiment. 10 is a flowchart of the operation of the process data recording apparatus 10 according to the fifth embodiment.

Embodiment 1 FIG.
*** Explanation of configuration ***
With reference to FIG. 1, the configuration of a process data recording apparatus 10 according to the first embodiment will be described.
The process data recording device 10 is a computer.
The process data recording apparatus 10 includes hardware including a processor 11, a memory 12, and a storage 13. The processor 11 is connected to other hardware via a signal line, and controls these other hardware.

The processor 11 is an IC (Integrated Circuit) that performs processing, and is a device that controls the entire process data recording apparatus 10. Specific examples of the processor 11 are a CPU (Central Processing Unit), a DSP (Digital Signal Processor), and a GPU (Graphics Processing Unit).

The memory 12 is a storage device that temporarily stores data. As a specific example, the memory 12 is an SRAM (Static Random Access Memory) or a DRAM (Dynamic Random Access Memory).

The storage 13 is a storage device that stores data. As a specific example, the storage 13 is an HDD (Hard Disk Drive) or an SSD (Solid State Drive). Further, the storage 13 is a portable storage such as an SD (registered trademark, Secure Digital) memory card, CF (CompactFlash), NAND flash, flexible disk, optical disk, compact disk, Blu-ray (registered trademark) disk, DVD (Digital Versatile Disk). It may be a medium.

The storage 13 stores a program for the operating system 20. This program is read into the memory 12 by the processor 11 and executed by the processor 11. Thereby, the function of the operating system 20 is implement | achieved.
The operating system 20 includes a dump acquisition unit 21, a memory management unit 22, a process management unit 23, and an acquisition management unit 24 as functional components. The dump acquisition unit 21 has a function of acquiring process data of the application process 31 as dump data 42. The memory management unit 22 has a function of performing allocation and release of a memory area requested by the process 31 and the fork process 32 and access control of the memory 12. The process management unit 23 is a function that performs control such as generation, execution, and stop of a plurality of processes 31. The acquisition management unit 24 is a function for managing the acquisition timing of the dump data 42 and the acquired dump data 42.
The process management unit 23 includes a list management unit 231 and a process fork unit 232. The acquisition management unit 24 includes a condition determination unit 241, a fork request unit 242, an adjustment unit 243, and an acquisition instruction unit 244.
On the operating system 20, one or more application processes 31 are operating. On the operating system 20, a fork process 32 in which the process 31 from which process data is acquired is forked may operate.

In FIG. 1, only one processor 11 is shown. However, the process data recording apparatus 10 may include a plurality of processors that replace the processor 11. The plurality of processors share execution of functional components included in the operating system 20. Each processor is an IC that performs processing in the same manner as the processor 11.

The operation of the process data recording apparatus 10 according to the first embodiment will be described with reference to FIG.
The operation of the process data recording apparatus 10 according to the first embodiment corresponds to the process data recording method according to the first embodiment. The operation of the process data recording apparatus 10 according to the first embodiment corresponds to the process of the process data recording program according to the first embodiment.

(Step ST101: Determination unit activation process)
When the application process 31 is being executed, the condition determination unit 241 of the acquisition management unit 24 is activated.

(Step ST102: Acquisition determination process)
The condition determining unit 241 refers to the acquisition condition information 43 to determine whether it is time to acquire the dump data 42.
The acquisition condition information 43 is information indicating an acquisition condition for acquiring the dump data 42. As specific examples, the acquisition condition is determined by a cycle, access to a specific memory area, access to a memory area where access is prohibited, start or end of another process, and change in memory usage. It is done. In the first embodiment, the acquisition condition information 43 is preset in the operating system 20.
The condition determination unit 241 determines whether or not it is time to acquire the dump data 42 by determining whether or not the acquisition condition indicated by the acquisition condition information 43 is satisfied. As a specific example, when the acquisition condition information 43 indicates access to a specific memory area, the condition determination unit 241 determines whether or not the specific memory area has been accessed. Then, the condition determination unit 241 determines that it is time to acquire the dump data 42 when a specific memory area is accessed.
If the condition determination unit 241 determines that it is not time to acquire the dump data 42, the process proceeds to step ST103. On the other hand, if the condition determination unit 241 determines that it is time to acquire the dump data 42, the process proceeds to step ST104.

(Step ST103: Standby process)
The condition determination unit 241 returns to step ST102 after waiting for a predetermined time.

(Step ST104: State determination process)
The condition determination unit 241 determines whether or not the process 31 is in an execution state.
If the process 31 is in the execution state, the condition determination unit 241 advances the process to step ST105. On the other hand, if the process 31 is not in the execution state, the condition determination unit 241 advances the process to step ST106. The case where the process 31 is not in the execution state is a case where the process 31 is not operating, such as a case where the process 31 is in an executable state or a case where the process 31 is waiting for input / output or an event.

(Step ST105: State change process)
The condition determination unit 241 changes the process 31 to an executable state so that the process 31 does not operate. The executable state is a state in which the processor 11 enters the execution state when the processor 11 becomes empty.

(Step ST106: Fork request processing)
The fork request unit 242 transmits the fork request for the process 31 to the process fork unit 232 of the process management unit 23.
Fork is to create a fork process 32 that is a copy of the process 31 and start it separately from the process 31 (by Daniel P. Bovet, Marco Cesati, supervised by Hirokazu Takahashi, Yumiko Sugita, Masaaki Shimizu, Masaaki Takasugi Translated by Masahiro Hiramatsu and Takahiro Yasui, “Detailed Description Linux (Registered Trademark) Kernel 3rd Edition” O'Reilly Japan, February 17, 2009, first edition 3rd edition, p.123).

(Step ST107: ID issuing process)
When receiving the fork request transmitted in step ST106, the process fork unit 232 issues a process ID for identifying the fork process 32 to be generated.

(Step ST108: ID addition process)
The list management unit 231 adds the process ID issued in step ST107 to the process list 41. At this time, the list management unit 231 adds the process ID issued in step ST107 as a child of the process ID of the fork source process 31.
The process list 41 is a list of process IDs of the activated process 31 and fork process 32. The process list 41 is a list for managing the parent-child relationship and the state of the process 31 and the fork process 32.

(Step ST109: Fork processing)
The process fork unit 232 generates a fork process 32 that is a copy of the process 31.
At this time, in the operating system 20 such as Unix (registered trademark), in order to copy the execution state of the process, if all the process data in the memory 12 used by the copy source process 31 is copied, 31 cannot operate. Therefore, the process fork unit 232 creates a fork process 32 by copying the process 31 by copy-on-write.
Copy-on-write is a method of writing to another memory space when the copy source process 31 and the copy destination fork process 32 share the memory space of the memory 12 and update data in the memory 12 (Daniel). P. Bovet, written by Marco Cesati, directed by Hirokazu Takahashi, Yumiko Sugita, Masaaki Shimizu, Masanori Takasugi, Masami Hiramatsu, translated by Takahiro Yasui. Issue No. 3, see pages 414 to 415).

The processing from step ST106 ^* to step ST109 ^* is the same as the processing from step ST106 to step ST109.

(Step ST110: State restoration process)
The fork request unit 242 returns the process 31 changed to the executable state in step ST105 to the execution state.

(Step ST111: Fork source ID acquisition process)
The fork request unit 242 transmits to the adjustment unit 243 an acquisition request for the process ID of the copy source process 31 of the fork process 32 generated in step ST109. The adjustment unit 243 acquires the process ID of the copy source process 31 that has received the acquisition request, and transmits the process ID to the fork request unit 242.

(Step ST112: Fork destination ID acquisition process)
The fork request unit 242 transmits the process ID acquisition request for the fork process 32 generated in step ST109 to the adjustment unit 243. The adjustment unit 243 acquires the process ID of the fork process 32 that has received the acquisition request, and transmits the process ID to the fork request unit 242.

(Step ST113: Process data acquisition process)
The acquisition instruction unit 244 transmits the process data acquisition instruction of the fork process 32 generated in step ST109 to the dump acquisition unit 21. At this time, the acquisition instruction unit 244 transmits the process ID of the copy source process 31 acquired in step ST111 and the process ID of the fork process 32 acquired in step ST112 to the dump acquisition unit 21 together with the acquisition instruction. .
The dump acquisition unit 21 acquires the process data in the memory space of the memory 12 used by the fork process 32 as the dump data 42 of the copy source process 31 and writes it in the memory 12. At this time, the dump acquisition unit 21 writes the process ID of the copy source process 31 acquired in step ST111 and the process ID of the fork process 32 acquired in step ST112 in association with the dump data 42. Note that the dump acquisition unit 21 may write only the process ID of the copy source process 31 acquired in step ST111 in association with the dump data 42.
The dump acquisition unit 21 acquires the process data after stopping the fork process 32 at the timing of acquiring the process data so that the data is not updated. Even if the fork process 32 is stopped, the copy source process 31 can continue its operation.

(Step ST114: Fork process deletion processing)
The process fork unit 232 deletes the fork process 32 generated in step ST109.

*** Effects of Embodiment 1 ***
As described above, the process data recording apparatus 10 according to the first embodiment generates the fork process 32 that forks the process 31 when acquiring the dump data 42. Then, the process data recording device 10 acquires the process data of the fork process 32 as the dump data 42 of the process 31.
As a result, the dump data 42 of the process 31 can be acquired only by stopping the process 31 for a short time such as a task switch. Therefore, it becomes possible to acquire the dump data 42 of the process 31 during the operation of the system.

Further, the process data recording apparatus 10 according to the first embodiment stores the process ID of the process 31 in association with the dump data 42. Therefore, it can be specified that the dump data 42 is the process data of the process 31.

Note that since the operating system 20 implements the above contents, it is not necessary to modify the process 31 of the application.

*** Other configurations ***
<Modification 1>
In FIG. 1, the dump data 42 is shown in the operating system 20. This means that the dump data 42 is stored in a memory space used by the operating system 20. However, the dump data 42 may be stored in the user space instead of the memory space used by the operating system 20.

Embodiment 2. FIG.
The second embodiment is different from the first embodiment in that the dump data 42 is replaced when the dump data 42 is periodically generated. In the second embodiment, this different point will be described, and the description of the same point will be omitted.

*** Explanation of configuration ***
The configuration of the process data recording apparatus 10 according to the second embodiment will be described with reference to FIG.
The process data recording apparatus 10 is different from the process data recording apparatus 10 shown in FIG. 1 in that the operating system 20 includes a dump management unit 25 as a functional component.

*** Explanation of operation ***
The operation of the process data recording apparatus 10 according to the second embodiment will be described.
The dump data 42 is stored in the memory 12 by the method described in the first embodiment.
The dump management unit 25 replaces a plurality of dump data 42 stored in the memory 12 according to rotation conditions such as a certain timing and the total size and number of dump data 42. As a specific example, the dump management unit 25 deletes the dump data 42 after a predetermined time has elapsed.

*** Effects of Embodiment 2 ***
As described above, the process data recording apparatus 10 according to the second embodiment replaces the dump data 42 according to the rotation condition. As a result, even when there is a limit to the area where the dump data 42 is stored, the acquisition of the dump data 42 can be continued.

Embodiment 3 FIG.
The third embodiment is different from the first embodiment in that the acquisition condition information 43 can be set. In the third embodiment, this different point will be described, and the description of the same point will be omitted.
Note that Embodiment 3 can be combined with Embodiment 2.

*** Explanation of configuration ***
The configuration of the process data recording apparatus 10 according to the third embodiment will be described with reference to FIG.
The process data recording device 10 is shown in FIG. 1 in that the acquisition management unit 24 includes an instruction communication unit 245 and the condition specifying unit 33 operates on the operating system 20. And different. The condition specifying unit 33 is a process that operates on the operating system 20.

*** Explanation of operation ***
With reference to FIGS. 5 and 6, the operation of the process data recording apparatus 10 according to the third embodiment will be described.
With reference to FIG. 5, an operation when an acquisition condition is set in the acquisition condition information 43 will be described.
(Step ST201: Setting request processing)
The condition designating unit 33 transmits a condition setting request for requesting a setting change of the acquisition condition information 43 to the command communication unit 245.
For example, when receiving an input of a new acquisition condition from the user of the process data recording apparatus 10, the condition specifying unit 33 transmits a condition setting request for requesting addition of a new acquisition condition. In addition, upon receiving an input for deleting an existing acquisition condition from the user of the process data recording apparatus 10, the condition specifying unit 33 transmits a condition setting request for requesting deletion of the existing acquisition condition.

(Step ST202: Condition editing process)
The command communication unit 245 receives the condition setting request transmitted in step ST201, and edits the acquisition condition information 43 according to the condition setting request.

(Step ST203: Completion notification process)
The command communication unit 245 transmits a setting completion notification indicating that the editing of the acquisition condition information 43 has been completed in step ST202 to the condition specifying unit 33.

(Step ST204: Completion Notification Reception Processing)
The condition designating unit 33 receives the setting completion notification transmitted in step ST203.

With reference to FIG. 6, the operation when referring to the acquisition condition information 43 will be described.
(Step ST301: Condition acquisition process)
The condition designating unit 33 transmits a condition acquisition request for requesting acquisition of the acquisition condition information 43 to the command communication unit 245.
For example, the condition specifying unit 33 transmits a condition acquisition request when receiving an input of a reference to an existing acquisition condition from the user of the process data recording apparatus 10.

(Step ST302: Condition acquisition process)
The command communication unit 245 receives the condition acquisition request transmitted in step ST301 and acquires a list of acquisition condition information 43.

(Step ST303: Condition notification process)
The command communication unit 245 transmits the list of acquisition condition information 43 acquired in step ST302 to the condition specifying unit 33.

(Step ST304: Condition notification reception process)
The condition designating unit 33 receives the list of acquisition condition information 43 transmitted in step ST303.

*** Effects of Embodiment 3 ***
As described above, in the process data recording apparatus 10 according to the third embodiment, since the operating system 20 includes the command communication unit 245, the acquisition condition information 43 is set from the condition designating unit 33 operating on the operating system 20. And reference is possible. Thereby, the acquisition condition information 43 can be changed without rebuilding the operating system 20.

Embodiment 4 FIG.
The fourth embodiment is different from the first embodiment in that the dump data 42 is analyzed. In the fourth embodiment, this different point will be described, and the description of the same point will be omitted.
Note that Embodiment 4 can be combined with Embodiment 2 or Embodiment 3.

*** Explanation of configuration ***
With reference to FIG. 7, the configuration of the process data recording apparatus 10 according to the fourth embodiment will be described.
The process data recording apparatus 10 is different from the process data recording apparatus 10 shown in FIG. 1 in that the operating system 20 includes a failure prediction unit 26 as a functional component.
The failure prediction unit 26 includes an analysis unit 261 and a notification unit 262.

*** Explanation of operation ***
The operation of the process data recording apparatus 10 according to the fourth embodiment will be described with reference to FIG.
(Step ST401: Generation notification process)
When the dump acquisition unit 21 writes the dump data 42 to the memory 12 in step ST113 of FIG. 2, the dump acquisition unit 21 transmits a generation completion notification indicating that the generation of the dump data 42 is completed to the failure prediction unit 26.

(Step ST402: Generation Notification Process)
The analysis unit 261 receives the generation completion notification transmitted in step ST401.

(Step ST403: Update determination processing)
The analysis unit 261 determines whether or not the dump data 42 has been newly generated.
If it is determined that the dump data 42 is not newly generated, the analysis unit 261 advances the process to step ST404. On the other hand, when it is determined that the dump data 42 is newly generated, the analysis unit 261 advances the process to step ST405.

(Step ST404: Standby process)
The analysis unit 261 waits for a predetermined time and then returns the process to step ST403.

(Step ST405: read processing)
The analysis unit 261 reads the dump data 42 when the generation completion notification is received at step ST402 and when it is determined that the dump data 42 is newly generated at step ST403.

(Step ST406: Analysis processing)
The analysis unit 261 determines whether or not the dump data 42 read in step ST405 indicates a precursor state of occurrence of an abnormality.
When the dump data 42 indicates a precursor state of occurrence of abnormality, the analysis unit 261 advances the process to step ST407. On the other hand, the analysis part 261 returns a process to step ST404, when the dump data 42 does not show the precursor state of abnormality occurrence.
As a specific example, the analysis unit 261 uses the dump data 42 continuously acquired a plurality of times as input, and determines whether or not an abnormal state sign is indicated by the dump data analysis tool. The dump data analysis tool is, for example, GDB (the GNU Project debugger).
For example, when the heap area of the process 31 continues to increase, the analysis unit 261 detects that there is a possibility that the area of the memory 12 may be exhausted. Further, the analysis unit 261 may cause a buffer overflow when the amount of use of the buffer used by the process 31 increases and when the value of a specific variable exceeds an assumed threshold value. Detect that there is.

(Step ST407: Notification process)
The notification unit 262 notifies at least one of the user and the application of the content of the abnormality that has been determined by the analysis unit 261 to indicate a precursor state in step ST406. As a specific example, the notification unit 262 notifies by a method such as output to a screen, data communication, and a signal.

*** Effects of Embodiment 4 ***
As described above, since the operating system 20 includes the failure prediction unit 26, the process data recording apparatus 10 according to the fourth embodiment can analyze the acquisition condition information 43 in real time. Further, since the process data recording device 10 can continuously acquire the dump data 42 continuously, the process data recording device 10 can detect a change with time from the dump data 42.
Thereby, it is possible to detect a precursor state of occurrence of an abnormality based on the dump data 42.

Embodiment 5 FIG.
The fifth embodiment is different from the first embodiment in that the dump data 42 is acquired using a process debug tool. In the fifth embodiment, this different point will be described, and the description of the same point will be omitted.
Note that Embodiment 5 can be combined with any of Embodiments 2 to 4.

*** Explanation of configuration ***
With reference to FIG. 9, the structure of the process data recording apparatus 10 which concerns on Embodiment 5 is demonstrated.
The process data recording apparatus 10 includes a point that the operating system 20 does not include the dump acquisition unit 21 as a functional component but a debug support unit 27, and a point that the dump acquisition unit 34 operates on the operating system 20. 1 is different from the process data recording apparatus 10 shown in FIG.
The dump acquisition unit 34 is a process that operates on the operating system 20. The dump acquisition unit 34 is a process debug tool. As a specific example, the dump acquisition unit 34 is GDB.

*** Explanation of operation ***
The operation of the process data recording apparatus 10 according to the fifth embodiment will be described with reference to FIG.
The basic processing is the same as that of a general process debugging tool, except that the fork process 32 is targeted.

(Step ST501: Fork completion notification process)
When step ST101 to step ST112 in FIG. 2 are executed, the acquisition instruction unit 244 transmits a fork completion notification indicating that the generation of the fork process 32 has been completed to the dump acquisition unit 34. At this time, the acquisition instruction unit 244 transmits the process ID of the copy source process 31 acquired in step ST111 and the process ID of the fork process 32 acquired in step ST112 to the dump acquisition unit 34 together with a fork completion notification. To do.
The dump acquisition unit 34 receives the fork completion notification, the process ID of the copy source process 31, and the process ID of the fork process 32.

(Step ST502: attach request process)
The dump acquisition unit 34 transmits the process ID of the fork process 32 received in step ST501 to the debug support unit 27 and requests attachment of the fork process 32.

(Step ST503: attach process)
The debugging support unit 27 receives the process ID of the fork process 32 transmitted in step ST502. The debug support unit 27 transmits the received process ID to the memory management unit 22 and attaches the fork process 32.

(Step ST504: reference information acquisition process)
The memory management unit 22 identifies the memory area of the memory 12 used by the fork process 32 indicated by the process ID transmitted in step ST503, and transmits reference information indicating the identified memory area to the dump acquisition unit 34.

(Step ST505: reference information output process)
The dump acquisition unit 34 receives the reference information transmitted in step ST504. The dump acquisition unit 34 outputs the received reference information to the user, for example, by outputting it on the screen.

(Step ST506: Reference request processing)
The dump acquisition unit 34 receives designation of reference content from the user. The dump acquisition unit 34 transmits a reference request indicating the designated reference content to the debug support unit 27.

(Step ST507: Address conversion process)
The debugging support unit 27 receives the reference request transmitted in step ST506. The debug support unit 27 converts the received reference request into the corresponding address of the memory 12. That is, when the reference request indicates a variable, the debug support unit 27 converts the reference request to the address of the memory 12 in which the variable indicated by the reference request is stored.
The debug support unit 27 transmits the converted address to the memory management unit 22 and requests acquisition of the process data stored in the memory area of the memory 12 indicated by the address.

(Step ST508: Data reply process)
The memory management unit 22 receives the address transmitted in step ST507. The memory management unit 22 reads the process data stored at the received address from the memory 12. The memory management unit 22 transmits the read process data to the debug support unit 27.

(Step ST509: Value shaping process)
The debug support unit 27 receives the process data transmitted in step ST508. The debug support unit 27 converts the received process data into a format that can be received by the dump acquisition unit 34, and transmits the converted process data to the dump acquisition unit 34.

(Step ST510: Data output processing)
The dump acquisition unit 34 receives the process data having the format converted transmitted in step ST509. The dump acquisition unit 34 outputs the received process data to the user, for example, by outputting it to the screen.

*** Effect of Embodiment 5 ***
As described above, the process data recording apparatus 10 according to the fifth embodiment can acquire process data with the process debug tool. As a result, it is possible to confirm the state of a specific variable and to confirm whether an abnormality has occurred in the execution state without waiting for the output of the dump data 42 at the development stage or the like.

10 process data recording device, 11 processor, 12 memory, 13 storage, 21 dump acquisition unit, 22 memory management unit, 23 process management unit, 231 list management unit, 232 process fork unit, 24 acquisition management unit, 241 condition determination unit, 242, fork request unit, 243 adjustment unit, 244 acquisition instruction unit, 245 command communication unit, 25 dump management unit, 26 failure prediction unit, 261 analysis unit, 262 notification unit, 27 debug support unit, 31 process, 32 fork process, 33 Condition specifying part, 41 process list, 42 dump data, 43 acquisition condition information.

Claims (7)

A process management unit that creates a fork process by copying a target process for obtaining process data, and operates the fork process separately from the target process;
A process data recording apparatus comprising: a dump acquisition unit that reads out process data for a fork process generated by the process management unit as process data for the target process and stores the process data as dump data. The process data recording apparatus according to claim 1, wherein the process data recording apparatus stores a process ID of the target process in association with the dump data. The process data recording apparatus according to claim 1, wherein the process management unit generates the fork process by copying the target process by copy-on-write. The process data recording device further includes:
4. The process data recording apparatus according to claim 1, further comprising a dump management unit that deletes the dump data stored by the dump acquisition unit according to a rotation condition. 5. The process data recording device further includes:
A condition designating unit for designating an acquisition condition for identifying the target process;
5. The process data recording apparatus according to claim 1, wherein the process management unit sets a process satisfying the acquisition condition specified by the condition specifying unit as the target process. 6. The process data recording device further includes:
The process data recording according to any one of claims 1 to 5, further comprising a failure prediction unit that analyzes the dump data stored by the dump acquisition unit and outputs a failure prediction notification that predicts the occurrence of a failure. apparatus. A process management process for generating a fork process by copying a target process for obtaining process data, and operating the fork process separately from the target process;
A process data recording program for causing a computer to execute a dump acquisition process for reading process data for a fork process generated by the process management process as process data for the target process and storing the process data as dump data.

Images