JPH05181656A - Symbol information management system - Google Patents

Abstract

PURPOSE:To efficiently execute information management in the symbol informa tion management system. CONSTITUTION:From a source file 10, a program object data file 102 is generated, and whether symbol information is generated or not is decided. In the case it is not designated, only an object file 104 is generated, and a generating flag of a symbol table state flag is reset. In the case the generation is designated, the generating flag of the symbol table state flag is set and it is generated and contained in a symbol information file 103, and in the next step, the object file 104 is generated from program object data. Whether symbol information exists in the symbol information file 103 or not is decided, and in the case its existence is confirmed, it is contained in a symbol table file 105, and an (i) node number in the symbol table file 105 is set to an (i) node number of the symbol table file in the object file 104.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a symbol information management system, and more particularly to a symbol information management system used for managing the symbol table information of a program object in a file separate from the program object.

[0002]

2. Description of the Related Art In the conventional symbol information management system of this type, a program object and the symbol table information of the program object are managed in the same object file. Alternatively, access to the symbol table information is generally performed by an offset value managed in the object file. Therefore, the symbol table information is deleted from the object file by changing the offset value and deleting the symbol table information data. The sizes are different.

[0003]

In the above-mentioned conventional symbol information management system, since the symbol table information exists in the object file, the size of the object file having the symbol table information becomes large. There is. Therefore, in deleting the symbol table information, the procedure for deleting the symbol table data in the object file is as follows:
The symbol information is not deleted because it is necessary to recompile the source file in order to restore the symbol table information, and thus it is impossible to restore the symbol table information when the source file does not exist. The object file or the source file and the environment for creating the object file have to be saved, and there is a disadvantage that extra man-hours are required to manage them.

[0004]

According to the symbol information management method of the present invention, as a processing procedure for creating a file of the symbol information management method of a program object having symbol information, a program object Data is created, and the created program object data is
First to be stored in the object data file 102
And the second processing step for determining whether or not to specify the creation of the symbol information, and when the creation of the symbol information is not specified in the second processing step, only the object file is written. Create
In the third processing step of resetting the creation flag of the symbol table status flag and in the second processing step, when creation of the symbol information is designated, the creation flag of the symbol table status flag is set. Then, the symbol information is created, and the created symbol information is stored in the symbol information file 103.
A fifth step of creating the object file from the program object data stored in the program object data file 102 after the third processing step and the third and fourth processing steps Processing step, a sixth processing step for determining the presence / absence of symbol information in the symbol information file 103, and in the sixth processing step, if the presence of the symbol information is confirmed, the symbol The symbol table file is created from the information file, and the symbol table file 10
And a seventh processing step of setting the inode number in the symbol table file 105 to the inode number of the symbol table file in the object file 104. When the presence of the symbol information is not confirmed in the processing step of No. 2 and after the processing of the seventh processing step is completed, all the file creation processing is ended.

[0005]

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

FIG. 1A is a configuration diagram of an object file in one embodiment of the present invention. As shown in FIG. 1A, the object file 1 of this embodiment
Is composed of file information 2 and program object data 3, and file information 2 is composed of object file information 4 and symbol table file information 5
The table file information 5 includes a symbol table status flag 6 and an inode number 7 of the symbol table file.

FIG. 2B is a configuration diagram of the symbol table file in one embodiment of the present invention. As shown in FIG. 1B, the symbol table file 8 of this embodiment is composed of file information 9 and symbol information 10, and the file information 9 is a symbol file.
It is composed of file information 11 and inode number 12 of the object file.

Next, FIG. 2 is a flow chart showing a processing procedure for creating a file in this embodiment. Below, Figure 1
With reference to (a) and (b) and FIG. 2, a processing procedure for creating a file of the symbol management method in the present embodiment will be described.

In response to the start of the file creation process for symbol information management, first, the program object data 3 from the source file 101 (see FIG. 1A).
Is performed, and the created program object data is stored in the program object data file 102 (step 21). Next, a process of determining whether or not to specify the creation of the symbol information 10 (see FIG. 1B) is performed (step 2
2) If the creation of the symbol information 10 is not designated, only the object file is created, and the creation flag of the symbol table status flag 6 (see FIG. 1A) is reset (step 23), Proceed to next processing step 25. When the creation of the symbol information 10 is designated, the symbol table status flag 6
The creation flag of (see FIG. 1A) is set, the process of creating the symbol information 10 (see FIG. 1B) is performed, and the created symbol information 10 is stored in the symbol information file 103. (Step 24), the process proceeds to the next process step 25. In processing step 25, the program object data 3 stored in the program object data file 102 (see FIG. 1).
(See (a)), the object file 104 is created, and then the process for determining the presence or absence of the symbol information 10 in the symbol information file 103 is performed (step 26). If the presence is not confirmed, the process is performed. When all the work is completed and the presence of the symbol information 10 is confirmed, the process proceeds to step 27, where the symbol information file 103 is used for the symbol table file 8
(See FIG. 1B) is created and stored in the symbol table file 105, and the symbol table is added to the inode number (see FIG. 1B) of the symbol table file 8 in the object file 104. -The inode number in the file 105 is set, and all processing operations are completed.

Next, FIG. 3 is a flow chart when the symbol information is accessed from the object file in the present embodiment. In FIG. 3, first, when there is access to the symbol information, a determination process of whether or not the creation flag of the symbol table state flag 6 (see FIG. 1A) is set is performed (step 3
1) If it is not set, the process ends, and if it is set, the process proceeds to the next step 32. In step 32, the object file 1 (see FIG.
It is determined whether or not the file with the inode number of the symbol table file 8 (see FIG. 1B) managed in (a) is present (step 32), and the file Is not present, the process ends, and if the presence is confirmed, the process proceeds to the next step 33. In step 33, the symbol table
The inode number of the object file 1 (see FIG. 1A) managed by the file 8 (see FIG. 1B) and the symbol table file 8 (see FIG. 1B)
The comparison / determination process is performed to determine whether or not the node number of the reference number of the reference number) matches (step 33). If the node numbers of both do not match, the process ends, and if they match, the symbol information 10 (see FIG. 1 (see (b)) is executed (step 34) and the process ends.

[0011]

As described above, according to the present invention, the size of the object file can be reduced by managing the program object data and the symbol table information in separate files. Even when the symbol table information exists in the object, the size of the object file does not change, and by holding the information for each file in both the object file and the symbol table file,
The symbol table file can be managed independently.

[Brief description of drawings]

FIG. 1 is a diagram showing configurations of an object file and a symbol table file in an embodiment of the present invention.

FIG. 2 is a flowchart showing an example of operation in the present embodiment.

FIG. 3 is a flowchart showing an example of symbol information access according to the present embodiment.

[Explanation of symbols]

1 Object File 2 File Information 3 Program Object Data 4 Object File Information 5 Symbol Table File Information 6 Symbol Table Status Flag 7 Symbol Table File Inode Number 8 Symbol Table File 9 File information 10 Symbol information 11 Symbol file information 12 Object file i number 21 Program object data creation processing 22 Symbol information creation determination processing 23 Symbol table status Flag creation flag reset processing 24 Symbol table status Flag creation processing Set flags 25 Object file creation processing 26 Symbol information existence determination processing 27 Symbol table file creation processing 31 Symbol Creating a flag status flag Judgment processing 32 Symbol table file search processing from inode number 33 Inode number comparison processing 34 Symbol information access processing 101 Source file 102 Program object data file 103 Symbol information file 104 object file 105 symbol table file

Claims (1)

[Claims] 1. As a processing procedure for creating a file of a symbol information management method of a program object having symbol information, program object data is created from a predetermined source file 101, and the created program object is created. A first processing step of storing data in the program object data file 102, a second processing step of determining whether or not to specify creation of symbol information, and a second processing step of: If the creation of the symbol information is not designated, only the object file is created and the creation flag of the symbol table status flag is reset, and the symbol information is created in the second processing step. If the creation of After the third and fourth processing steps, in which the flag information is created by setting the creation flag of the flag table status flag, and the created symbol information is stored in the symbol information file 103. In response, the fifth processing step of creating the object file from the program object data stored in the program object data file 102, and the presence of the symbol information in the symbol information file 103. A sixth processing step for determining the presence / absence, and in the sixth processing step, when the presence of the symbol information is confirmed, a symbol table file is created from the symbol information file, and a symbol table is created.・ Store in file 105 And a seventh processing step of setting an inode number in the symbol table file 105 to an inode number in the symbol table file in the file 104, and the symbol information in the sixth processing step. Is not confirmed, and after completion of the processing of the seventh processing step, all file creation processing is ended.