JPH05233357A - Symbolic debugging method - Google Patents

Abstract

PURPOSE:To save a memory resource and shorten an access time by discriminating a load module among object modules and symbol information (symbol contrast table) and saving them in different files. CONSTITUTION:When a source program 1 is compiled by a compiler 2, an object file 3 and the symbol contrast table 4 is generated. When they are linked by a linker 5 to other programs to generate the load module, the object file generated by the compiler 2 is divided into a program object file 3 and the symbol contrast table 4. The divided program object file 3 is stored in a load module file 6 and the symbol contrast table 4 is stored in a contrast table file 7. When the program is debugged by using a symbolic debugger 8, the symbolic debugger 8 performs a symbolic debugging process by referring to both the load module file 6 and contrast table file 7.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a symbolic debugging method for debugging a program under test with a symbolic debugger.

[0002]

2. Description of the Related Art Conventionally, symbolic debugging has been known in which a program is debugged using symbol information.

In this symbolic debugging, when a debug option is specified when a source program is compiled to create an object program, a symbol comparison table (symbol table) in which symbols and addresses are associated with each other is created. The created comparison table is incorporated in the object program, linked with another program by the linker, and then debugged by the symbolic debug. In this way, the object program after completion of debugging is loaded as a completed program.

By the way, this symbol comparison table is used only at the time of symbolic debugging and is unnecessary after the completion of debugging, but the size of the load module becomes enormous because it is incorporated in the object and the load module.

Therefore, conventionally, a load module is created by designating a debug option while using a symbolic debugger, and when the program is completely debugged, the debug option is removed and the load module is made compact again to make the size of the load module compact. I was compiling and linking.

[0006]

However, according to such a conventional method, if the developer mistakenly uses the load module of the program with the debug option specified as the load module of the completed program,
Since a huge program including an unnecessary symbol comparison table is executed, there are problems that a large amount of memory resources are used and it takes a lot of time to access the auxiliary storage device. In addition, there is a problem that it affects other programs.

The present invention has been made in view of the above circumstances, and an object thereof is to always create a compact load module regardless of whether a debug option is specified, to save memory resources and shorten access time. It is to provide a possible symbolic debugging method.

[0008]

In order to achieve the above object, the present invention is a computer system equipped with a symbolic debugger, wherein a load module and symbol information required by the symbolic debugger are separated from the object modules. It is characterized in that it is saved in another file, and during debugging, the symbolic debug for the program in the load module file is executed using the symbol information file required by the symbolic debugger.

[0009]

According to the present invention, the load module and the symbol information (symbol comparison table) are selected from among the object modules.
Since and are separated and saved in separate files, the reference table can be removed from the load module, and the memory resources can be significantly reduced. In addition, the file can be configured compactly and it will not affect other programs.

[0010]

1 is a block diagram showing an embodiment to which a symbolic debugging method according to the present invention is applied.

As shown in the figure, in the present embodiment, a compiler 2 which compiles a source program 1 to create an object, an object created by the compiler 2 is divided into a program object 3 and a symbol comparison table 4 and loaded respectively. It is composed of a linker 5 that files in a module file 6 and a comparison table file 7, and a symbolic debugger 8 that performs symbolic debugging using the load module file 6 and the comparison table file 7.

Next, the operation of this embodiment will be described.

When the compiler 2 compiles the source program 1, an object 3 and a symbol comparison table 4 are created. When the linker 5 links this with another program to create a load module, the compiler 2
The object created by is divided into a program object 3 and a symbol comparison table 4. The divided program object 3 is stored in the load module file 6, and the symbol comparison table 4 is stored in the comparison table file 7.

When the program is debugged using the symbolic debugger 8, the symbolic debugger 8 refers to both the load module file 6 and the comparison table file 7 to execute the symbolic debugging.

As described above, according to this embodiment, a compact execution program can be created regardless of whether or not the debug option is specified. Therefore, it is not necessary to recompile or link the debugged program after debugging is completed. Further, if a problem occurs in the completed and executed program, it is possible to perform symbolic debugging using the load module as it is without recompiling or linking. Also, since the symbol comparison table is not included in the load module, it is possible to prevent the influence on other programs.

[0016]

As described above, according to the present invention, it is possible to always create a compact load module regardless of whether or not a debug option is specified, and it is possible to save memory resources and shorten access time.

Further, since the load module does not include the symbol information, it is possible to prevent the influence on other programs.

[Brief description of drawings]

FIG. 1 is a configuration diagram showing an embodiment to which a symbolic debugging method according to the present invention is applied.

[Explanation of symbols]

 1 Source program 2 Compiler 3 Object 4 Symbol comparison table 5 Linker 6 Load module file 7 Comparison table file 8 Symbolic debugger

Claims (1)

[Claims] 1. In a computer system equipped with a symbolic debugger, the load module and the symbol information required by the symbolic debugger are separated from the object modules and saved in separate files, and the symbols required by the symbolic debugger are debugged. A symbolic debugging method characterized in that an information file is used to perform symbolic debugging for a program in a load module file.