JP2702356B2 - Debug information access method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a debug information access method for accessing debug information in an object file in a large-scale software source code level debugger.

[0002]

2. Description of the Related Art Conventionally, in this kind of debug information access method, a source code level debugger searches a debug information in an object file in order from the beginning to find a target one, or a search function by a binary search. Is being done.

[0003]

In this conventional debug information access method, the debug information in the file is searched in order from the top and read until the target is found. Significant time was needed to get the information. Also,
For the same reason, in the binary system, file access to large-scale software requires much time.

An object of the present invention is to provide a debug information access method which can reduce the processing time for searching for debug information in an object file in a large-scale software source code level debugger.

[0005]

SUMMARY OF THE INVENTION A debug information access method according to the present invention is a program management method for a source code level debugger in a data processing device, which comprises file management information having information on an object file constituting a load module to be debugged. It has an information area, an area for file management information for accessing debug information, an area for storing file management information used in the past, and an area for temporarily storing an area for file management information for accessing debug information. When it is necessary to input debug information from the debug target load module and refer to initialization debug information for creating the program management information, file management information corresponding to the execution address of the debug target load module is temporarily stored. Save to the first A second step of checking whether or not the file management information for the execution address and the necessary information for the object file exist; and, if the corresponding information did not exist in the second step, A third step of checking whether necessary information is included in the file management information that has been used in the third step, and when the corresponding information does not exist in the third step, all of the components constituting the load module A fourth step of checking the file management information of the object file, a fifth step of storing the file management information for the used object file when the corresponding information exists in the fourth step, And a sixth step of returning to the value stored in the step.

[0006]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the present invention will be described with reference to the drawings.

FIG. 1 is a flow chart showing a processing procedure according to an embodiment of the present invention, in which logic for determining which object file should be accessed based on an address is shown. Implemented by source code level debugger. The source code level debugger has an area for program management information composed of file management information having information on object files constituting the load module to be debugged, an area for file management information for accessing debug information, and file management information used in the past. Initialization debug information that has each data area of an area for accumulating data and an area for temporarily storing an area for file management information for accessing debug information, and for creating program management information by inputting debug information from a load module to be debugged When it becomes necessary to refer to the file management information, the file management information corresponding to the execution address of the load module to be debugged is temporarily stored (step;
S1) It is checked whether necessary information exists for the currently used object file (S2).

Next, when the corresponding information does not exist in S2, it is checked whether or not the corresponding information exists in the object file which has been used in the past (S2).
3) When the corresponding information does not exist in S3, it is checked whether or not the corresponding information exists in all the object files (S4). When the corresponding information exists in S4, the file management information for the used file is accumulated (S5), necessary information is extracted from the object file (S6), and finally the information stored in S1 is restored (S7). .

The reason for using the logic described with reference to FIG. 1 is that the frequency of access is high in the order of the object file currently used, the object file used in the past, and the object file never used. Is expected to be high.

FIG. 2 is a diagram showing an image of an area for storing program configuration management information used when deciding a file by the logic of FIG. In this area, an object file name 21 constituting the program to be debugged,
Since the start address 22 of the object file and the end address 23 of the object file are entered, it is possible to find a target object file without directly reading the object file.

FIG. 3 is a diagram showing an image of an area for buffering information of an object file once accessed. This area is used to store the used information of the program configuration management information shown in FIG. 2, and includes an object file name 31, an object file start address 32, an object file end address 33, And a file descriptor 34 of an object file corresponding to. This area is used because an object file that has been accessed once is highly likely to be accessed in the future, and if information necessary for access is stored, the next processing is not required and the speed can be increased.

FIG. 4 is a diagram showing an image of an area for saving the current state so that the information currently in use does not change before and after referring to debug information of another object file. This area includes a currently used object file name 41, a starting address 42 of the object file,
It is composed of an end address 43 of the object file and a file descriptor 44 of the object file. Using this area, save as S1 and S7 in FIG.
If the recovery is performed, the currently referred file does not change before and after the process, and therefore, the next access to the currently referred file is accelerated.

[0013]

As described above, according to the present invention, as a logic for determining a file to refer to debug information in an object file, a file currently being referenced, a file which has been referenced in the past, and all files are accessed in this order. Since the target file is determined in this way, the time required to obtain information on the file that has been referred to is shortened.

[Brief description of the drawings]

FIG. 1 is a flowchart illustrating a processing procedure according to an embodiment of the present invention.

FIG. 2 is a diagram showing an image of a storage area of program configuration management information used for determination in the logic shown in FIG. 1;

3 is a diagram showing an image of an area for temporarily buffering information used once in the information of FIG. 2 together with information necessary for file access.

FIG. 4 is a diagram showing an image of an area for saving and restoring information so that a file referred to by accessing debug information in a file is not changed;

Claims (1)

(57) [Claims] In a source code level debugger in a data processing device, an area of program management information composed of file management information having information of an object file constituting a load module to be debugged, and a file management information for debugging information access. An area for storing file management information used in the past, and an area for temporarily storing an area for file management information for accessing debug information. A first step of temporarily saving file management information corresponding to an execution address of the load module to be debugged when it is necessary to refer to initialization debug information for creating the program management information; Management information and A second step of checking whether necessary information exists for the object file; and a step of checking file management information which has been used in the past when the corresponding information did not exist in the second step. A third step of checking whether there is any necessary information from among them, and checking file management information of all object files constituting the load module when the corresponding information does not exist in the third step A fourth step, a fifth step of storing file management information for the used object file when the corresponding information is present in the fourth step, and a sixth step of returning to the value stored in the first step. And a debug information access method.