JP2010122759A - Debugging device, method of storing and restoring dump file, and program thereof - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a debugging device and the like that can store a dump file in a smaller file size and restore it so that a command executed previously can be executed again. <P>SOLUTION: The debugging device 10 includes: a reference position recording means 44 for recording, if a debugger tool 21 refers to a dump file 31, a position where the dump file is referred to as a tag file 33; a reduced dump file creation means 45 for reading data at the position recorded in the tag file from the dump file, and creating a reduced dump file 34 that records the position and the data at the position; and a reduced dump file restoration means 46 for reading the position and the data at the position recorded in the reduced dump file, and positioning the data at the position to create a restored dump file 35. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to dump file debugging, and more particularly to saving and restoring the dump file.

  In many computers, when normal calculation processing cannot be continued, data in the physical memory of the computer in operation is stored in a data storage device such as a disk for investigation of the cause. This is called a dump file. An application program that analyzes a dump file is called a debugger tool.

  When investigating failures in operating systems and application programs, investigations are often conducted by comparing past cases with new cases. In many cases, it is effective to compare and investigate a plurality of dump files having similar failures. Therefore, regarding the saving of the dump file, it is important to save the part once referred to by the debugger tool while keeping the position in the referenced dump file as it is. The dump file is preferably stored for a long time.

  There are the following related techniques for debugging dump files, especially for saving dump files. Patent Document 1 describes a technique for reducing the size of a dump file by dividing the dump file into a certain size and compressing the dump file. Patent Document 2 describes a technique of writing an area registered as a dump target area on a memory into a dump file. Patent Document 3 describes a technique in which a dump file is collected and then compressed. Patent Document 4 describes a technique of compressing a main storage image and writing it in a dump file.

JP 2001-256082 A JP 2005-332421 A JP 09-171476 A JP 09-325903 A

  The dump file is often a large file. In addition, as the physical memory capacity of future computer devices further increases, the dump file is expected to become a larger file. Therefore, storing a larger number of dump files over a long period of time requires a huge capacity data storage device, which is more difficult.

  For this reason, in the above Patent Documents 1, 3, and 4, the dump file is compressed and stored. In these documents, file compression and decompression are based on the premise that a reversible data compression and decompression method such as ZIP or LHA is used.

  However, as described above, a dump file that increases as the size of the physical memory increases can be sufficiently compressed even if it is compressed by the above-described reversible data compression and decompression method. The file does not become small. For this reason, there is a need for a dump file reduction method that is different from compression.

  Further, in the method involving reversible compression and decompression, the data during the compression and decompression work is written into the physical memory or nonvolatile storage device of the computer, so that there is a problem that the associated storage capacity and processing load are applied. is there.

  An object of the present invention is to provide a debugging device, a dump file saving and restoring method, and a program thereof that can save a dump file with a smaller file size and restore a previously executed command so that it can be executed again. It is in.

  In order to achieve the above object, a debugging device according to the present invention is a debugging device having a debugger tool for debugging a dump file, and when the debugger tool refers to the dump file, the position where the dump file is referenced is determined. Reference location recording means for recording as a tag file, reduced dump file creating means for reading data at a position recorded in the tag file from the dump file, and creating a reduced dump file recording the data at the position and location, and a reduced dump A reduced dump file restoring unit that reads data at a position and a position recorded in the file and arranges the data at the position to create a restored dump file.

  In order to achieve the above object, a method for saving and restoring a dump file according to the present invention is a method for saving and restoring a dump file referenced by a debugger tool. When the debugger tool references a dump file, the dump file is restored. Record the location where the file was referenced as a tag file, read the data at the location recorded in the tag file from the dump file, create a reduced dump file recording the data at that location and location, and record it in the reduced dump file. In this case, the restored data is read at the specified position and the position, and the read data corresponding to the position is arranged to create a restoration dump file.

  In order to achieve the above object, a dump file storage / restoration program according to the present invention provides a computer that constitutes a debugging device with a tag file at a location where the dump file is referenced when a debugger tool references the dump file. The procedure for recording, the procedure for reading the data at the position recorded in the tag file from the dump file, the procedure for creating the reduced dump file recording the data at the location and position, and the position and position recorded in the reduced dump file And a procedure for arranging the read data corresponding to the position and creating a restoration dump file.

  As described above, the present invention creates a reduced dump file in which only data at a position where the debugger tool refers to the dump file is left as described above, and places the data at the position to create a restored dump file. Now that you have configured it, you can re-execute previously executed commands. This makes it possible to save a dump file with a smaller file size and restore it so that a previously executed command can be executed again. Can be provided.

[First Embodiment]
Hereinafter, the configuration of the first embodiment of the present invention will be described with reference to the accompanying drawings.
First, the basic content of the present embodiment will be described, and then more specific content will be described.
The debugging device 10 according to the present embodiment includes a debugger tool 21 that debugs a dump file 31, and when the debugger tool 21 refers to the dump file 31, the position at which the dump file is referenced is tagged. Reference location recording means 44 for recording as file 33 and reduced dump file creation means for reading data at a position recorded in tag file 33 from dump file 31 and creating reduced dump file 34 in which data at the position and position is recorded 45, and reduced dump file restoring means 46 that reads data at the position and position recorded in the reduced dump file 34 and arranges data corresponding to the position to create the restored dump file 35.

Further, the debug device 10 includes a debugger management unit 41 that starts the debugger tool and writes the file name (dump file name 26b) of the dump file referred to by the debugger tool to the monitoring table 26.
Then, the reference location recording unit 44 recognizes the file name (dump file name 26b) of the dump file with reference to the monitoring table 26, and detects the position where the dump file 31 indicated by this file name is referred.

  Then, the reduced dump file restoring means 46 writes temporary data, which is temporary temporary data such as all “0”, for example, at positions not recorded in the reduced dump file 34 of the restored dump file 35.

  With the configuration described above, the debug device 10 can save the dump file 31 with a smaller file size and restore the previously executed command so that it can be executed again.

Furthermore, the debug device 10 includes a command history creation unit 43 that creates a command history file 32 that records commands executed on the dump file 31 by the debugger tool 21, and a user from the commands recorded in the command history file 32. The command selection means 42 for receiving the selection by the command and executing the selected command on the dump file 31 again. By configuring in this way, re-execution of a command once executed is further facilitated.
This will be described in further detail below.

(Basic principle)
As described above, regarding the saving of the dump file, it is important to save the part once referenced by the debugger tool while keeping the position in the referenced dump file as it is. It is not necessary to save the parts that are not referenced by the debugger tool. The present invention utilizes this fact, and when the debugger tool refers to the dump file, the reduced dump file is created by leaving only the referenced portion and deleting the unreferenced portion. For this process, it is not necessary to use a reversible data compression and decompression method such as ZIP or LHA.

  Further, when restoring the original dump file from the reduced dump file, it is not necessary to reversibly restore the entire file including the unreferenced portion. The part already referenced by the debugger tool only needs to be reproduced at the same position on the original dump file. For this reason, in the present invention, the data portion already deleted at the reduction stage is made a file having the same size as the original dump file size by adding temporary data. In this way, it is possible to execute a previously executed command again without depending on the type of debugger tool.

(Device and data configuration)
FIG. 1 is an explanatory diagram showing the configuration of the debugging device 10 according to the first embodiment of the present invention. The debugging device 10 is a general computer device including a control unit 11 including a CPU, OS, RAM, and the like, and a storage unit 12 including a nonvolatile storage device such as a hard disk.

  The control unit 11 which is a main body for executing the computer program executes respective functional units such as a debugger tool 21, a command history creating unit 22, a tag file creating unit 23, a reduced dump file creating unit 24, and a reduced dump file restoring unit 25. . At the same time, the control table 11 also holds a monitoring table 26 as temporary data. The storage unit 12 stores data such as a dump file 31, a command history file 32, a tag file 33, a reduced dump file 34, and a restored dump file 35.

  The debugger tool 21 is a debugger tool used for examining the dump file 31. The command history creation unit 22 includes a debugger management unit 41, a command selection unit 42, and a command history creation unit 43. These units generally operate as follows.

  The debugger management unit 41 activates and terminates the debugger tool 21 and writes data to the monitoring table 26 in order to notify the tag file creation unit 23 of activation of the debugger tool 21.

  FIG. 2 is an explanatory diagram showing the data structure of each table and file shown in FIG. 2A is a monitoring table 26, FIG. 2B is a command history file 32, FIG. 2C is a dump file 31, FIG. 2D is a tag file 33, and FIG. 2E is a reduced dump file. 34 and FIG. 2F show the data structure of the restoration dump file 35, respectively. Each data structure will be described later when the corresponding table and file appear.

  The monitoring table 26 shown in FIG. 2A is stored as temporary data in the control unit 11 in association with the debugger start flag 26a and the dump file name 26b. Therefore, the monitoring table 26 is not a file stored in the storage unit 12. The debugger start flag 26 a is a flag that is set when the debugger tool 21 is activated and cleared when the debugger tool 21 is terminated. The dump file name 26 b is the file name of the dump file 31 that is referenced by the debugger tool 21.

  The command history creation means 43 inputs a command to be executed by the debugger tool 21 to the debugger tool 21 and writes to the command history file 32 which command has been executed at the same time. In the command history file 32 shown in FIG. 2B, commands executed by the debugger tool 21 are written in order.

  When the debugger tool 21 finishes examining the dump file 31, the command selection means 42 stores the dump file 31 that is referred to by the command selected by the user from the command history recorded in the command history file 32. In order to create the reduced dump file 34 while leaving only the data, the contents of the tag file 33 are once deleted, and the command selected by the user is executed again. Thus, the tag file 33 is reconstructed.

  The tag file creation unit 23 includes reference location recording means 44. The reference location recording means 44 generally operates as follows. FIG. 3 is an explanatory diagram showing operations of the debugger tool 21 and the reference location recording means 44 shown in FIG. FIG. 3A shows an operation in which the debugger tool 21 refers to the dump file 31, and FIG. 3B shows an operation in which the reference location recording unit 44 records the location in which the debugger tool 21 referred to the dump file 31.

  As shown in FIG. 3A, normally, when the debugger tool 21 refers to the dump file 31, the operating system 101 makes a reference request to the dump file 31, and the operating system 101 refers to the dump file 31. The location is read and the data is passed to the debugger tool.

  On the other hand, the reference location recording means 44 resides in the operating system 101 as shown in FIG. 3B and traces the input / output of the operating system 101. The reference location recording means 44 refers to the monitoring table 26, confirms the debugger start flag 26a, confirms that the debugger tool 21 is being activated, and then confirms the dump file name 26b. If it is a reference to the dump file 31, the reference location is written to the tag file 33 as tag data.

  The tag data recorded in the tag file 33 is generated as follows. The dump file 31 shown in FIG. 2C is divided into blocks of a certain size, and block numbers are given in order from the top. As shown in FIG. 2D, the block number of the location where the debugger tool 21 referred to the dump file 31 is written into the tag file 33 by the reference location recording means 44.

  The reduced dump file creation unit 24 includes a reduced dump file creation means 45. The reduced dump file creating means 45 operates generally as follows. The reduced dump file creating means 45 first writes the original dump file size 34a at the head of the reduced dump file 34 shown in FIG. Subsequently, the tag data is read from the tag file 33, and the read tag data 34b is written to the reduced dump file. Subsequently, the tag data 34 b is referred to, the corresponding block data 34 c in the original dump file 31 is read, and the data is written to the reduced dump file 34. As a result, the reduced dump file 34 having the data configuration shown in FIG.

  The reduced dump file restoring unit 25 includes a reduced dump file restoring means 46. The reduced dump file restoring means 46 operates generally as follows. First, the original dump file size 34a and tag data 34b recorded at the head of the reduced dump file 34 are read. For the blocks included in the tag data, the data 35a is read from the reduced dump file 34 and written in the same block position as the original dump file. For the blocks not included in the tag data, the temporary data 35b is written at the same block position. As a result, the restoration dump file 35 having the data configuration shown in FIG. 2F is created by the reduced dump file restoration means 46.

  The temporary data 35b here may be very simple data such as “all 0”, for example. The operation in which the reduced dump file restoring unit 46 generates the restored dump file 35 from the reduced dump file 34 in this way is referred to as restoration of the reduced dump file 34.

(Create command history file and tag file)
FIG. 4 is a flowchart showing an operation in which the command history file 32 and the tag file 33 are written when the debugger tool 21 shown in FIG.

  When the debugger management unit 41 activates the debugger tool 21 (step S201), the debugger management unit 41 sets the debugger start flag 26a in the monitoring table 26 shown in FIG. 2A (step S202), and the dump file name 26b. Is written (step S203). When a command is input from the debugger management means 41 to the debugger tool 21 and this command is started (step S204), the command history creation means 43 writes the input command to the command history file 32 (step S205).

  When the debugger tool 21 requests the operating system 101 to refer to the dump file (step S206), the reference location recording unit 44 confirms the monitoring table 26 and the debugger start flag 26a is set (debugging is started). And the dump file 31 represented by the target dump file name 26b is confirmed (step S207).

  The reference location recording unit 44 confirms whether the input / output detected by the operating system 101 is a reference to the dump file 31. If it is not a reference to the dump file 31, it waits until a reference to the dump file comes (step S208). When the reference to the dump file 31 is detected, the reference location recording unit 44 writes the reference location as tag data in the tag file 33 (step S209).

  If there is a next command to be executed by the debugger tool 21, the process returns to step S204 to execute the next command. If there is no command to be executed next, the process proceeds to step S211 (step S210).

  The command selection means 42 confirms whether the user selects a command (step S211). If so, the process proceeds to step S212 and the command selection means 42 is executed. The operation of the command selection means 42 will be described later with reference to FIG. If no command is selected, the debugger management means 41 clears the debugger start flag 26a of the monitoring table 26, deletes the dump file name 26b (step S213), and ends the debugger tool 21 (step S214).

  FIG. 5 is a flowchart showing details of the operation of the command selection means 42 shown in step S212 of FIG. The command selection means 42 first reads the command history file 32 (step S251), and accepts an input for the operator to select a command from the read commands (step S252).

  Then, the command selection means 42 deletes all the contents of the tag file 33 (step S253), inputs the command selected in step S252 to the debugger tool 21, and starts this command (step S254). In response to this, the command selection means 42 requests the operating system 101 to refer to the dump file from the debugger tool 21 (step S255).

  The monitoring part 26 is confirmed by the reference location recording means 44, the debugger start flag 26a is set (debugging has started), and the dump file 31 represented by the dump file name 26b that is the target is recorded. Check the reference. If it is not a reference to the dump file 31, it waits until a reference to the dump file 31 comes (step S256). When the reference to the dump file 31 is detected, the reference location recording means 44 writes the reference location in the tag file 33 (step S257).

  If the command to be executed remains among the commands selected by the operator, the process returns to step S254 to execute the subsequent command. If not, the process ends (step S258).

(Create a reduced dump file)
FIG. 6 is a flowchart showing the operation of the reduced dump file creating means 45 shown in FIG. The reduced dump file creating means 45 first reads tag data from the tag file 33 (step S301), and writes the original dump file size 34a at the head of the reduced dump file 34 (step S302). Subsequently, the tag data 34b read in step S301 is written following the original dump file size 34a (step S303).

  Here, when the reduced dump file creation means 45 reads the data of the block corresponding to the block number described in the tag data from the original dump file 31 (step S304), the reduced data 34c of the corresponding block read is reduced. After writing to the dump file 34 (step S305), the original dump file 31 is deleted (step S306).

(Create a restoration dump file)
FIG. 7 is a flowchart showing the operation of the reduced dump file restoring means 46 shown in FIG. Hereinafter, n is a natural number representing a block number. The reduced dump file restoring means 46 first reads the tag data 34b and the original dump file size 34a from the reduced dump file 34 (step S401). The block number n is set to 1 (step S402), and it is confirmed whether the block number n exists in the tag data 34b (step S403).

  If it exists, the data 35a is read from the reduced dump file 34 (step S404) and written to the block n of the restored dump file 35 (step S405). If the block number n does not exist in the tag data 34b in step S403, the temporary data 35b is written in the block n of the restoration dump file 35 (step S406).

  After completion of steps S405 and 406, it is confirmed whether or not the value of n has advanced to a block corresponding to the original dump file size 34a (step S407). If not, 1 is added to n (step S408), and the process returns to step S403. If it is advanced, the part larger than the original dump file size 34a is deleted from the end of the restore dump file 35 so that the file size of the restore dump file 35 matches the original dump file size 34a. The fraction of the size is adjusted (step S409), and the restoration process of the reduced dump file 34 is terminated.

(Overall operation)
Next, the overall operation of the first embodiment will be described. A method for saving and restoring a dump file referred to by the debugger tool 21 according to the first embodiment of the present invention is such that when the debugger tool 21 refers to the dump file 31, the position where the dump file is referenced is tagged. Data is recorded as the file 33 (FIG. 4: steps S206 to S209), then the data at the position recorded in the tag file 33 is read from the dump file 31, and the data at the position (tag data 34b) and the position (of the corresponding block The reduced dump file 34 in which the data 34c) is recorded is created (FIG. 6: Steps S303 to 305), and the data at the position and position recorded in the reduced dump file 34 are read (FIG. 7: Steps S401 and 404). Data corresponding to the read position (the data 35a The disposed (FIG. 7: Step S405) to create a restore dump file 35.

  Here, each of the above operation steps may be programmed so as to be executable by a computer, and these may be executed by the debug device 10 which is a computer that directly executes each of the steps.

  As described above, in the present embodiment, the following effects can be obtained by performing the operations described above. Since the dump file debugging device 10 according to the present embodiment is configured to save only the portion referenced by the debugger tool 21 in the dump file 31, the command executed on the dump file 31 is executed again. The reduced dump file 34 can be created while leaving the data necessary for this. Further, since the restored dump file 35 created from the reduced dump file 34 has been restored with the portion referenced by the command executed once, the investigation by the command can be reproduced.

  Furthermore, in the present embodiment, a command that has been executed once is recorded in the command history file 32, and it is also possible to save and restore a portion referenced by the command. It becomes easier to re-execute the command for the restored dump file 35.

[Second Embodiment]
FIG. 8 is an explanatory diagram showing the configuration of the debugging device 510 according to the second embodiment of the present invention. Compared with the debug device 10 according to the first embodiment, the debug device 510 only has the command selection unit 42, the command history creation unit 43, and the command history file 32 omitted. And the action is the same. The same elements as those in the first embodiment are denoted by the same reference numerals, and the operation of each element is as described in the first embodiment. However, since the command selection means 42 and the command history creation means 43 do not exist, steps S205, 211, 212 in FIG. 4 and the operation shown in FIG. 5 are omitted.

  Even in this configuration, the debugger management means 41 writes the debugger start flag 26 a and the dump file name 26 b in the monitoring table 26. Therefore, the tag file creation unit 23 can grasp the location of the dump file 31 from the monitoring table 26. Therefore, the tag file creation unit 23 can create the tag file 33 by the same operation as that of the first embodiment for the command executed by the debugger tool 21 on the dump file 31.

  For this reason, the reduced dump file creation unit 24 can also create the reduced dump file 34 in which only the portion referred to by the debugger tool 21 is written. Furthermore, the reduced dump file 34 can be created by the reduced dump file restoring unit 25 using the reduced dump file 34.

  As a result, the debug device 510 according to the second embodiment of the present invention can execute commands executed by the debugger tool 21 on the dump file 31 with respect to the command history file 32 as compared with the debug device 10 according to the first embodiment. However, the same effect as that of the debugging device 10 according to the first embodiment can be obtained.

[Third Embodiment]
FIG. 9 is an explanatory diagram showing the configuration of the debugging device 610 according to the third embodiment of the present invention. The debug device 610 is obtained by adding a dump file compression unit 647 to the reduced dump file creation unit 24 and a dump file decompression unit 648 to the reduced dump file restoration unit 25 of the debug device 10 according to the first embodiment. . The dump file compression unit 647 and the dump file decompression unit 648 compress and decompress the file by a reversible method such as ZIP or LHA.

  FIG. 10 is a flowchart showing the operation of the reduced dump file creating means 45 shown in FIG. The reduced dump file creation unit 24 performs the same operation as steps S301 to S305 shown in FIG. 6, and then compresses the reduced dump file 34 for which data has been written by the dump file compression means 647 (step S707). The original dump file 31 is deleted (step S306). The reduced dump file 34 after being compressed in step S707 is referred to as a compressed dump file 634.

  FIG. 11 is a flowchart showing the operation of the reduced dump file restoring means 46 shown in FIG. The reduced dump file restoring unit 25 decompresses the compressed dump file 634 by the dump file decompression unit 648 to generate the reduced dump file 34 (step S801), and then performs the same processing as steps S401 to S409 to perform the restored dump file 35. Is generated.

  In the first and second embodiments, the reversible compression operation of the file is not performed. In the third embodiment, the reversible compression operation is added to the file, so that the dump file can be generated with a smaller amount of data. Can be saved. However, as described above, the compression and decompression processing has a problem that the storage capacity and processing load associated therewith are increased. Therefore, it is possible to select whether or not to perform the compression and decompression processing at the user's discretion. Is desirable.

  Of course, the above effect can be obtained even if the dump file compression unit 647 and the dump file decompression unit 648 are added to the debug device 510 having the configuration shown in the second embodiment.

  The present invention has been described with reference to the specific embodiments shown in the drawings. However, the present invention is not limited to the embodiments shown in the drawings, and any known hitherto provided that the effects of the present invention are achieved. Even if it is a structure, it is employable.

  The present invention is applicable to uses such as an operating system using a dump file and a failure investigation of an application program. The present invention can also be applied to applications such as long-term storage of dump files and analysis of failure trends of operating systems and application programs. At that time, it does not particularly depend on the type of the debugger tool.

It is explanatory drawing which shows the structure of the debugging apparatus which concerns on the 1st Embodiment of this invention. It is explanatory drawing shown about the data structure of each table and file shown in FIG. 2A is a monitoring table, FIG. 2B is a command history file, FIG. 2C is a dump file, FIG. 2D is a tag file, FIG. 2E is a reduced dump file, and FIG. f) shows the data structure of the restored dump file. It is explanatory drawing shown about operation | movement of the debugger tool and reference location recording means 44 shown in FIG. FIG. 3A shows an operation in which the debugger tool refers to the dump file, and FIG. 3B shows an operation in which the reference location recording unit records the location in which the debugger tool referred to the dump file. 7 is a flowchart showing an operation of writing a command history file and a tag file when the debugger tool shown in FIG. 1 examines a dump file. It is a flowchart which shows the detail of operation | movement of the command selection means shown to step S212 of FIG. It is a flowchart shown about operation | movement of the reduced dump file preparation means shown in FIG. It is a flowchart shown about operation | movement of the reduced dump file decompression | restoration means shown in FIG. It is explanatory drawing which shows the structure of the debugging apparatus which concerns on the 2nd Embodiment of this invention. It is explanatory drawing which shows the structure of the debugging apparatus which concerns on the 3rd Embodiment of this invention. 10 is a flowchart showing the operation of the reduced dump file creating means shown in FIG. FIG. 10 is a flowchart showing the operation of the reduced dump file restoring means shown in FIG. 9. FIG.

Explanation of symbols

10, 510, 610 Debugging device 11 Control unit 12 Storage unit 21 Debugger tool 22 Command history creation unit 23 Tag file creation unit 24 Reduced dump file creation unit 25 Reduced dump file restoration unit 26 Monitoring table 26a Debugger start flag 26b Dump file name 31 Dump file 32 Command history file 33 Tag file 34 Reduced dump file 34a Original dump file size 34b Tag data 34c Corresponding block data 35 Restored dump file 35a Data 35b Temporary data 41 Debugger management means 42 Command selection means 43 Command history creation Means 44 Reference location recording means 45 Reduced dump file creation means 46 Reduced dump file restoration means 634 Compressed dump file 647 Dump file Compression means 648 dump file decompression means

Claims (8)

A debugging device having a debugger tool for debugging a dump file,
When the debugger tool refers to the dump file, a reference location recording means for recording a position where the dump file is referenced as a tag file;
Reading the data at the position recorded in the tag file from the dump file, a reduced dump file creating means for creating a reduced dump file recording the data at the position and the position;
A reduced dump file restoring means for reading the position recorded in the reduced dump file and data at the position, and arranging the data corresponding to the position to create a restored dump file;
A debugging device comprising:   The debugging apparatus according to claim 1, further comprising a debugger management unit that activates the debugger tool and writes a file name of the dump file referred to by the debugger tool in a monitoring table.   The reference location recording unit recognizes a file name of the dump file by referring to the monitoring table, and detects a position where the dump file indicated by the file name is referred to. The debugging device described in 1.   The debug according to claim 1, wherein the reduced dump file restoring means writes temporary data that is temporary temporary data at a position of the restored dump file that is not recorded in the reduced dump file. apparatus. Command history creating means for creating a command history file in which commands executed on the dump file by the debugger tool are recorded;
2. The apparatus according to claim 1, further comprising a command selection unit that accepts a selection made by a user from commands recorded in the command history file and executes the selected command again on the dump file. Debug device. Dump file compression means for reversibly compressing the reduced dump file;
The debugging apparatus according to claim 1, further comprising dump file decompression means for decompressing the compressed reduced dump file. A method for saving and restoring a dump file referenced by a debugger tool, comprising:
When the debugger tool refers to the dump file, the position where the dump file is referenced is recorded as a tag file,
Read data at the location recorded in the tag file from the dump file,
Create a reduced dump file that records the location and data at the location,
Read the position recorded in the reduced dump file and the data at the position,
A method for saving and restoring a dump file, comprising arranging the read data corresponding to the position to create a restored dump file. To the computer that configures the debugging device,
When the debugger tool refers to the dump file, a procedure for recording the referenced position of the dump file as a tag file;
A procedure for reading data from the dump file at a position recorded in the tag file;
A procedure for creating a reduced dump file in which the position and data at the position are recorded;
Reading the position recorded in the reduced dump file and the data at the position;
A dump file storage / restoration program that executes a procedure of arranging the read data corresponding to the position and creating a restoration dump file.

Images