JP2827724B2 - Program debug processing method - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to debugging of execution of a program described in a high-level programming language of a computer, and more particularly to debugging at a so-called source program level, which enables detailed debugging of a reference portion of an expansion function. It relates to a program debug processing method.

[0002]

2. Description of the Related Art In the so-called source program level execution debugging of a source program written in a high-level programming language, as is known, the execution of a target program translated from a source program is as if the source program was executed as it is. Debugging operations can be performed as follows.

That is, a program line in a source program is designated and instructed to a debugger which controls the execution of a program to be debugged by a position in the program in the source program (hereinafter referred to as a program line number) or the like. , Stepping, stopping, referencing execution results, and other debugging operations.

[0004] For this purpose, a compiler that translates the source program simultaneously generates information indicating the correspondence between each program line number of the source program and the address of a machine language instruction in the target program when generating the target program. Generate and output as debug information.

[0005] The debugger determines the address of the target program by referring to the debug information for the program line number specified in the operand of the debug command.
Performs the control specified by the command for the execution of the target program.

For example, assume that there is a source program as shown in FIG. The main body of this program starts from the program line number “100”, for example, where the numbers in the leftmost column of the figure are the program line numbers, and it is assumed that there are program lines of various definition statements and declaration statements before that.

In this example, the program line number "101"
Is a program line that refers to the defined macro “KAKAKU”, “102” is a program line of the output instruction, and the quoted macro “KAKAKU” is an expansion consisting of program line numbers “12” and “13”. It is defined by a “define” statement in the function part, and in this case, is defined to be expanded into two program lines.

In this definition, the macro "ZEIK
IN ", a so-called two-stage nest of quotation relations is formed, and the macro" ZEIKIN "has a program line number" 10 ".
It is defined in the same format as the above by the “define” statement of the expansion function part of “11”.

In such a case, the compiler expands the program line with the program line number "101" into a three-line program as shown in FIG. Translated together with the program of the number “102”, a target program as illustrated in FIG. 4C is generated.

At the same time, the compiler generates, as debug information, information as shown in FIG. 4 (d) indicating a correspondence between a program line number and an instruction word address. In the figure, the instruction word addresses are displayed in hexadecimal.

[0011]

As described above, as expansion functions referred to in the expansion function section, expansion functions referred to as expanding a program line include a macro definition and an external file import function.

In these cases, the original 1
Generally, a program line is expanded into a plurality of program lines, but each program line expanded into a plurality of lines has no program line number in the source program.

Therefore, in the debug information for that part, the original one program line number and the instruction word group of the target program generated from a plurality of program lines are made to correspond collectively.

For this reason, even when there is a bug in the expanded part, the user of the debugger may stop by specifying a specific program line in the expanded part, for example, to check the intermediate state. There is no means for issuing such a command.

Therefore, in such a case, the user needs to guess the location of the bug by examining the citation relation of the expansion function and analyzing the contents of the expansion part on the program list. This is one of the inefficiencies.

It is an object of the present invention to provide a program debugging processing method that enables detailed debugging in an expanded portion citing an expansion function in the same manner as a main program line.

[0017]

FIG. 1 is a block diagram showing the configuration of the present invention. The figure shows the configuration of the program debug processing method. The compiler 2 solves the source program 1
When creating a target program 3 by decomposing
Is added to each line of the source program 1 composed of lines.
Program line number to be executed and each line of source program 1
The instruction word of target program 3 generated corresponding to
Information 4 indicating the correspondence between the addresses in the memory to be loaded and
Is generated, and the program line number of the source program 1 is
Command, and the debugger 5 executes the program
By referring to the debug information 4 according to the line number,
Performs debugging control of the generated target program 3
In the system,

Compiler 2 is an expansion that defines a processing process.
A quotation program line that cites the function section and the expansion function section;
For the source program 1 including
Program line is replaced with the process of the expansion function section
The target program 3 with the program line number
And furthermore, a quoted program line for the
Citation level and the program line of the replaced process
Citation relationship indicating number and correspondence with objective program 3
Generate information 6,

The program line number of the replaced process
The program line number including the number for the target program 3
Is input to the debugger 5 as the debug command, Device
Logger 5 is based on debug information 4 and citation-related information 6.
To identify the program line number of the debug command,
Debug control is performed on the program line in the changed process .

[0020]

According to the processing method of the present invention, each program line in the expanded part can be identified by the citation relationship represented by, for example, the nesting level of the citation and each program line number of the definition statement of the citation destination. The correspondence with the address of the target program is shown, and this information is incorporated into the debug information as citation-related information.

When the user specifies a program line in the expanded portion as an operand by a debug command, for example, starting from the program line number of the quoted source body, the program line numbers of the definition statement of the quoted destination are arranged in the order of the nesting level. By specifying, one program line in the expansion result is specified.

The debugger analyzes the operand specification based on the citation relation information, determines a specified program line, and performs debugging control on the determined program line in the same manner as in a normal case.

[0023]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The compiler 2 shown in FIG. 1 adds citation relation information 6 to debug information 4 to generate a table as shown in FIG. The figure corresponds to the example of the source program shown in FIG.

The table shown in the figure has columns of “program line number”, “nest level”, and “instruction word address” from the left, and the nest level corresponding to the program line number of each program line of the program body is “1”. ".

The nesting level of the program line extracted and expanded from the main program is set to "2", and then the nesting level of the program line expanded and referenced further is set to "3". I do. Each program line in the expanded portion displays the program line number of the program line defined in the expanded function section.

When the execution is interrupted, in order to obtain a program line from the address, the elements in FIG. 4E are arranged in ascending order of instruction word addresses. In the example of the figure, since the macro “KAKAKU” is quoted with the program line number “101”, the line with the program line number “101” is at the nesting level “1”, followed by the quoted program line number “12”,
They are expanded to “13” and their nesting level is “2”.

Next, since the macro "ZEIKIN" is further quoted with the program line number "13", the macro is expanded into the quoted program line numbers "10" and "11", and their nesting level is "3".

The instruction word address indicates the head address of the instruction group corresponding to the target program, as apparent from the target program illustrated in FIG. 4D. Since there is no directly corresponding command word in the program line (for example, program line number “101”), the command word address is set to a predetermined invalid display.

For example, when debugging a program as shown in FIG.
When specifying the program line number "10" of the macro "ZEIKIN" cited by the program line number "13" of the macro "KAKAKU" cited by "1" as the operand of the debug command, specify the program line number including the citation relation For example, "1
01/13/10 "(this expression is hereinafter referred to as a sentence number).

The debugger 5 is provided with a statement number management block as shown in FIG. 2 to hold each statement number designation by a series of debug commands and the corresponding instruction word address, and use the instruction word address as usual. When control is performed and execution is interrupted at a certain address, a search is made for the statement number management block using the address value as a key, and the value of the statement number specification retained in the matching block is obtained. This is used as a sentence number to be expressed in a message or the like to notify the user.

By retaining the format of the statement number in this way, the trouble of generating the statement number expression specified by the user in reverse from the command address can be omitted, and the program of FIG. In this case, "101/13/10"
Even if the specification is "101/13", the stop is performed at the instruction word address "0546" in the same manner. It can be so.

The debugger 5 performs a process of determining an instruction word address by referring to the debug information table as shown in FIG. 4E from the statement number of the operand designation in the expression as described above.

FIG. 3 is a flow chart of a process in which the debugger sets the statement number management block. First, in processing step 10, the search target nest level is set to 1, and the item number to be searched is initialized to the first item of the debug information table.

In processing step 11, the program line number of the position of the current search target nest level of the specified statement number (level / level 2 from left with "/" as a delimiter) is set to the search target line. Take out as a number.

By repeating the processing steps 12 to 14, the first item having the nesting level to be searched is searched from the top of the debug information table. If the program line number does not match, identify whether the end of the debug information table in processing step 13; if not, proceed with the term in processing step 14,
The process returns to the processing step 12 and starts again from the nest level search.

If the program line numbers match, it is determined in step 16 whether the current search target line number is the last program line number of the designated statement number.
Step 17 advances the search target nesting level by one,
Returning to 11, the same processing is performed for the new nest level as described above.

When it is identified in the processing step 16 that the processing has been performed up to the end of the designated statement number, in the processing step 18 the instruction word address of the current item of the debug information table is taken out, and the statement number and The instruction word address is set, and in step 19, the sentence number management block is connected to the beginning of the chain shown in FIG.

[0038]

As is apparent from the above description, according to the present invention, in the execution debugging of a high-level programming language program of a computer, each program line of the expansion result is specified by a debug command for the expansion section citing the expansion function section. By doing so, the detailed debugging of the expanded part can be performed in the same manner as the program line of the main body, so that there is a remarkable industrial effect of improving the efficiency of the debugging work.

[Brief description of the drawings]

FIG. 1 is a block diagram showing the configuration of the present invention.

FIG. 2 illustrates a statement number management block.

FIG. 3 is a flowchart of a process performed by a debugger.

FIG. 4 is a diagram illustrating debug information.

[Explanation of symbols]

 1 Source program 2 Compiler 3 Object program 4 Debug information 5 Debugger 6 Citation related information 10-19 Processing steps

Claims (1)

(57) [Claims] The compiler (2) is a source program.
Decode and decompose (1) to generate the target program (3)
At the time, a source program whose processing is composed of lines
The program line number assigned to each line in (1) and the source program
The target program generated corresponding to each line of the program (1)
Address in memory where instruction word of program (3) is loaded
And debug information (4) indicating the correspondence between the source code and the program line number of the source program (1).
Command, and the debugger (5)
By referring to the debug information (4) according to the number
And a debugging system for the generated target program (3)
In the control system, the compiler (2) includes an expansion function unit that defines a processing process.
And a quoting program line that cites the expansion function section.
For the composed source program (1),
Replace the program line with the process of the
Generate target program (3) with program line number
And furthermore, a quoted program line for the
Citation level and the program line of the replaced process
Quotation indicating correspondence with number and objective program (3)
The relation information (6) is generated, and the program including the program line number of the replaced process is generated.
Gram line number is debug for target program (3)
An instruction is input to the debugger (5) , and the debugger (5) receives the debug information (4) and the citation-related information.
Based on (6), change the program line number of the debug command
Identify and replace the program line of the replaced process
A program debug processing method that performs debug control .