JP2003058392A - Software development environment program, its recording medium, program debugging device, and program debugging method - Google Patents

Abstract

(57) [Summary] (Modified) [Problem] In debugging a product version program recompiled so that a debugging statement is invalidated by a compile option, a statement for diagnosis instruction written in a test version program is valid. Enable debugging as if it were. SOLUTION: When a compile option is specified, a compiler generates an object module in which a debug statement is invalidated, and generates diagnostic debug information for a diagnostic instruction statement. When the debugger detects the debugging information for diagnosis, the debugger sets a break point for diagnosis at an address corresponding to a line position where a statement for instructing diagnosis of the source program is described for the load module. When the debugged program is executed and an interrupt occurs at the diagnostic interruption point, the debugger is configured to substitute for the processing of the diagnostic statement as if the diagnostic instruction statement is valid.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a debugging support function of a program, and in particular, diagnoses the correctness of a program to be inserted into a test version program under development even when a problem occurs in a product version program provided to a customer. The present invention relates to a compiler and debugger technology for automatically executing processing equivalent to the function of a diagnostic instruction statement prepared for the purpose.

[0002]

2. Description of the Related Art In a program for operating a computer, when a relational expression between (adjacent) statements expressing an algorithm must always be established, when this relational expression is not established when the program is executed. You can judge that there is a tap in the program. In order to diagnose the correctness of the program by utilizing this characteristic, in a language such as C / C ++, a macro (assert macro) for instructing the correctness of the program so that debugging can be easily performed. Is prepared.

The assert macro checks whether or not this relational expression holds, and if this relational expression does not hold, it is considered that the program has a bug and outputs diagnostic information to a standard error stream or the like. If this relational expression is satisfied, it is considered that the program has no bug, and the program execution is continued without doing anything. The assert macro is converted into a code only when it is compiled in the debug mode (when the definition character strings "DEBUG" and "_DEBUG" are defined), and the assert macro is processed when the program is executed. In addition, release mode (definition character string “NDEBUG” is defined, “DEBUG” and “_
(When "DEBUG" is not defined), the assert macro is converted into a void expression and nothing is done when the program is executed.

When debugging a test version program under development, a break point is usually set in the program to set conditions for checking variables and control tables, and a program interrupt occurs due to the break point during execution of the program under test. Check while setting the contents when you do. However, in a program related to processing such as parameter analysis in which the upper and lower limits of variables are determined or the attributes of variables are determined, basic debugging is possible only by checking the values of variables. In such a case, assert
If you insert macros in the key points of the program, you can debug when the program is running. Therefore, as
The sert macro is widely used during program development.

The test version program under development is compiled in the debug mode so that the assert macro is valid when the program is executed. On the other hand, the product version program provided to the customer is recreated based on the debugged test version program so that diagnostic information is not output when the program is executed. In this case, it is common to provide a recompiled release mode program without changing the debugged test version source program. With this provision method, if a problem occurs in the product version program, set the breakpoint at the line position where the assert macro converted into the void expression is described by referring to the source program list. , Asser
It was possible to display and confirm the relational expression specified by the parameter of the t macro by entering the command of the debugger.

[0006]

However, in the above-mentioned providing method, even if the statement for the diagnostic instruction is inserted in the source program, it is manually interrupted in debugging the product version program provided to the customer. If you do not set a point and check the relational expression that is true with the command of the debugger, or recompile the program by specifying the compile option so that the debug statement is valid, it is equivalent to the test version program. Debugging was not possible and debugging efficiency was very poor.

Even when trouble occurs in the product version program, the invalid diagnostic instruction statement inserted in the source program can be used, and the debug processing equivalent to the function of the diagnostic instruction statement is automatically performed. It is very convenient to do so, and the debugging efficiency of the product version program is improved.

[0008]

FIG. 1 shows an overall configuration diagram of a first embodiment of the present invention. The software development environment program of the present invention comprises a compiler 1 and a debugger 2, and the computer uses a diagnostic instruction to identify a diagnostic instruction statement for diagnosing the correctness of the program in the source program using a computer. A parsing means 11 for analyzing a statement such as a syntax analysis including an identifying means 12, an object output means 13 for generating an object from a source program, diagnostic information for a diagnostic instruction statement and a debug information file 5
Debug information output means 14 including the diagnostic information output means 15 for outputting to the control information, the control means 21 for controlling the debugger 2 in the debugger 2, and the program interruption caused by the interruption point. The breakpoint management means 22 including the diagnostic breakpoint identifying means 23 for identifying whether or not the diagnostic breakpoint is set, and the diagnostic breakpoint setting means for setting the diagnostic breakpoint when the diagnostic information is detected from the debug information file 5. Debug information managing means 24 for managing debug information including 25, diagnostic interrupt point processing means 26 for performing diagnostic processing based on diagnostic information when a program interrupt is generated due to diagnostic information, and variable processing means for managing variable processing. 27, which functions as a process processing unit 28 that controls process processing.

After the source program 3 is debugged, when the compiler instruction is given to the source program 3 by designating a compile option so as to invalidate the debugging statement, the analysis means 11 of the compiler 1 After analyzing the state statement and invalidating the debugging statement, the object output means 13
The object module 4 is output via. When the diagnostic instruction identification means 12 identifies a diagnostic statement during statement analysis, the diagnostic information output means 15, which is part of the debug information output means, outputs the diagnostic information to the debug information file 5.

After that, the load module 6 is generated from the object module 4 by the linkage editor 9 to create a product version. The product version of the program is attached with the debug information file generated by the compiler 1. When a failure occurs in the product version program and the user activates the debugger 2, the debug information management means 24 searches the debug information file 5. When the debug information management unit 24 detects the diagnostic information in the debug information file 5, the debug information management unit 24 sets a diagnostic breakpoint at a predetermined location in the load module 6 via the diagnostic breakpoint setting unit 25. The load module 6 is executed as the debugged process 7 through the processing of the variable processing means 27 and the process processing means 28, but since it is not a main part of the present invention, its details are omitted. The debugged process 7 generates a program interrupt at the position of the interruption point. When the process to be debugged 7 causes a program interrupt due to a break point, the break point management means 22 identifies whether or not the interrupt occurred at the break point for diagnosis through the break point identifying means 23 for diagnosis. When an interruption due to a diagnostic break point occurs, the diagnostic break point processing means 26
Based on the diagnostic information output to the debug information file 5, the debugging process defined by the diagnostic instruction statement is substituted.

As described above, in the software development environment in which the compiler and the debugger cooperate, a product created by specifying the compile option so as to invalidate the debug statement when the diagnostic instruction statement is inserted in the source program. For the edition program,
Debugging equivalent to the test version can be performed automatically without recompiling or setting breakpoints.

[0012]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS FIG. 1 shows an overall configuration diagram of a first embodiment of the present invention. The compiler 1 and the debugger 2 cooperate to provide a software development environment and are recorded in a computer-readable recording medium. It should be noted that the compiler 1 and the debugger 2 described in FIG. 1 describe not the entire program but the parts related to the present invention. Although the description is based on the development environment program using the C language, the development environment program to which the present invention can be applied is not limited to the one using the C language.

The compiler 1 includes a diagnostic instruction identifying means 12 for identifying a diagnostic statement in the analysis means 11, and a diagnostic information output means 15 for outputting debug information (diagnostic information) for the diagnostic statement in the debug information output means 14. A new function is added so that the diagnostic information of diagnostic statements can be output as an addition to the existing compiler functions. Further, the debugger 2 includes a diagnostic break point setting means 25 for setting a diagnostic break point in the debug information managing means 24 so that the debugger can substitute the function of the diagnostic statement, and a break point managing means 22 for the break point managing means 22. When a program interrupt occurs due to a diagnostic interrupt point, the diagnostic interrupt point identification means 23 for identifying whether the interrupt is due to a diagnostic interrupt point corresponds to the function of a diagnostic statement when an interrupt due to a diagnostic interrupt point occurs. The diagnostic interruption point processing means 26 for executing the processing is newly provided, and the problem is solved in cooperation with the compiler to which the function is added.

The source program 3 is a source program to be debugged. In this embodiment, a case of debugging the program shown in FIG. 2 will be described. The object module 4 is the result of the source program 3 being specified by the compile option so that the debug statement is invalidated and translated by the compiler 1.

The debug information file 5 is a file for storing the debug information shown in FIG. 3 for the assert macro when the source program 3 is specified by a compile option so that the debug statement is invalidated and translated by the compiler 1. is there. The load module 6 is obtained by converting the object module 4 into an executable program through a linkage editor.

The debugged process 7 is a process in which a break point is set for the load module 6 to be debugged so that the load module 6 can be debugged. The input / output device 8 is for inputting commands to the debugger and outputting messages from the debugger. Even if the display or typewriter device is locally connected to the CPU, it is a personal computer or other device remotely connected. This computer system may be used.

FIG. 2 shows an example of a program used in the first embodiment. This program is an example of a subroutine that returns the corresponding message from the error number. An assert macro, which is a statement for a diagnostic instruction, is inserted in the 20th, 21st, and 34th lines. In this example, the assert macro in the 20th line assumes that there is no bug in the program and continues the program without doing anything when the integer type variable ErrNo is not 0 (a relational expression that is true). When ErrNo is 0, it is considered that the program has a bug, and the diagnostic information is output to the standard error stream. Two
When the character type variable pMsg is not empty, the assert macro in the first line assumes that the program has no bug and continues the program without doing anything. Indicates that diagnostic information will be output to the standard error stream. Also, the assert macro on the 34th line is (because it was when the message was not found when coming here)
It always indicates that the program is buggy (always false), indicating that diagnostic information will be printed to the standard error stream.

FIG. 3 describes diagnostic information which is an example of the debug information output to the debug information file.
This example corresponds to the program example of FIG. 2, and the assert on the 20th line of the source program shown in FIG.
For the macro, the line position is 20 lines, and the true comparison condition is when the variable ErrNo is not 0. Similarly 21
The line position is 21 lines with respect to the assert macro of the line,
The true comparison condition indicates when the character type variable pMsg is not empty. Further, it is shown that the line position is 34 lines and is always false with respect to the assert macro of the 34th line.

FIG. 4 shows an example of the breakpoint management information. Line positions 6, 30 and 36 indicate the break points set by the user for debugging at the entrance and exit of the subroutine (program) shown in FIG. 2 using the commands of the debugger. In this case, the flag is Break, because it can be distinguished from the interruption point that is automatically set for diagnosis (assert macro).
Row positions 20, 21 and 34 are for diagnostic (assert)
Macro) represents an interruption point, and as a flag, Assert
However, a true comparison condition at the break point is set.

FIG. 5 shows the processing operation of the diagnostic instruction statement of the compiler. The compiler 1 reads the source program 3 via the analysis means (S50
1), it is determined whether the statement read by the diagnostic instruction identification means 12 is an assert macro (S502). If it is not an assert macro, each statement is processed (S506), but since this processing is the original processing of the compiler and is not a main part of the present invention, its details are omitted.

The read statement is assert
If it is a macro, it is determined whether or not the translation option is in the debug mode for invalidating the debug statement (S503). In the debug mode, the process of the assert macro is performed (S50
4). The processing of the assert macro is also a processing of one statement, and therefore the details are omitted. When not in the debug mode, the assert macro is converted into a void expression and the diagnostic information of the assert macro is output to the debug information file 5 (S505). It is determined whether the above processing has been performed for all the read statements (S507).

FIG. 6 shows the processing operation of the debugger related to the present invention. When the debugger is activated, the load module 6 of the program to be debugged is read via the debug information management means 24 (S601), and subsequently the debug information for the program to be debugged is read from the debug information file 5 (S602). It is determined whether the read debug information has diagnostic information (S
603) If there is diagnostic information, an interruption point for the assert macro is set at the address on the load module corresponding to the line position on the source program in which the assert macro is described (S604). Corresponding the line position on the source program to the address on the load module is a conventional function of the compiler / debugger, and thus its details are omitted.

When the setting of the break point for the assert macro is completed, the debugger 2 enters a state of waiting for a command from the user to the debugger (S605). The commands to the debugger include commands for setting and releasing breakpoints, commands for displaying and changing display data, and execution-type commands for executing a debugged process or executing only one step. When the user inputs a command, it is determined whether the command is an execution type command (S
507) If the command is not an execution command, the input command is processed (S606). In this embodiment, it is assumed that the user has input a command for setting a break point for debugging at the entrance and exit of the program shown in FIG. 2, and the break point management information shown in FIG. , 30 and 36, the Break flag is set.

When an execution system command is input, the debugger 2 executes the process to be debugged 7 (S60
8). When the debugged process 7 is executed and a program interrupt due to an interrupt point occurs, it is determined whether the interrupt is an interrupt point by the assert macro based on the interrupt point management information shown in FIG. 4, and if it is not by the assert macro, a step is executed. The command waiting state of S605 is entered (S609).

When the interrupt is caused by the assert macro, the interruption condition of the assert macro is extracted from the interruption point management information, and it is determined whether the relational expression designated by the assert macro is true or false. The program execution process of step S608 is performed (S61).
1). If it is false, the user is notified of the assert error, and if the diagnostic instruction statement is inserted in the source program by entering the command input waiting state in step S605 (S612), the debug statement is invalidated. Even for a product version program created by specifying with the compile option as described above, debugging equivalent to the test version can be automatically performed without performing operations such as recompilation and setting of break points.

[0026]

As described above, according to the present invention,
It has the following effects. Without recompiling the product version of the program or setting breakpoints,
Debugging efficiency is improved by automatically enabling the same debugging as during product development testing with the load module as shipped.

[Brief description of drawings]

FIG. 1 is an overall configuration diagram of a first embodiment of the present invention.

FIG. 2 is an example of a program.

FIG. 3 is an example of debug information.

FIG. 4 is an example of breakpoint management information.

FIG. 5 is a flowchart showing processing of a diagnostic instruction statement of the compiler.

FIG. 6 is a flowchart showing processing of a debugger.

[Explanation of symbols]

1 compiler 2 Debugger 3 Source program 4 Object module 5 Debug information file 6 load module 7 Process to be debugged 8 I / O device 9 Linkage Editor 11 Analytical means 12 Diagnostic instruction identification means 13 Object output means 14 Debug information output means 15 Diagnostic information output means 21 Control means 22 Break point management means 23 Diagnosis Break Point Identification Means 24 Debug information management means 25 Break point setting means for diagnosis 26 Breakpoint Processing Means for Diagnosis 27 variable processing means 28 Process processing means

Claims (4)

[Claims] 1. A software environment program comprising a compiler and a debugger, which debugs a source program described in a high-level language based on compiler output information output when the source program written in the high-level language is translated by the compiler. Diagnostic instruction identifying means for identifying a diagnostic statement, and diagnostic information output means for outputting diagnostic information for the diagnostic instruction statement to a debug information file, wherein the debugger detects the diagnostic information from the debug information file and loads the load module. A diagnostic break point setting means for setting a diagnostic break point, and a diagnostic break point identifying means for identifying whether or not the program is caused by the diagnostic break point when a program interrupt occurs due to the break point; Program by interruption point When write occurs, the software development environment program for causing a computer to function as a diagnostic interrupt point processing means for performing a diagnostic process on the basis of the diagnostic information. 2. A program debug device comprising a compiler and a debugger, which debugs a source program written in a high-level language based on compiler output information output when the compiler translates the program, wherein the compiler gives a diagnostic instruction. Diagnostic instruction identifying means for identifying a diagnostic statement, and diagnostic information output means for outputting diagnostic information for the diagnostic instruction statement to a debug information file, wherein the debugger detects the diagnostic information from the debug information file and loads the load module. A diagnostic break point setting means for setting a diagnostic break point, and a diagnostic break point identifying means for identifying whether or not the program is caused by the diagnostic break point when a program interrupt occurs due to the break point; Interruption by program interruption point When There occurs, program debugging apparatus characterized by having a diagnostic interrupt point processing means for performing a diagnostic process on the basis of the diagnostic information. 3. A recording medium comprising a compiler and a debugger, and recording a software environment program for debugging the source program written in a high-level language based on the compiler output information output when the compiler translates the program. The compiler is a diagnostic instruction identifying unit that identifies a diagnostic instruction statement, and a diagnostic information output unit that outputs diagnostic information for the diagnostic instruction statement to a debug information file, and the debugger is configured to output the diagnostic information from the debug information file. When it is detected, a diagnostic breakpoint setting means for setting a diagnostic breakpoint in the load module, and a diagnostic breakpoint identifying means for identifying whether or not the diagnostic breakpoint is caused when a program interrupt occurs due to the breakpoint And the break point for the diagnosis If program interrupt due occurs, a recording medium which records the software development environment program for causing a computer to function as a diagnostic interrupt point processing means for performing a diagnostic process on the basis of the diagnostic information. 4. A debugging method, comprising a compiler and a debugger, for debugging a source program written in a high-level language based on compiler output information output when the compiler translates the source program, wherein the compiler is a translated object. module,
And at least output compiler output information consisting of debug information having a line position on the source program corresponding to the diagnostic instruction statement and a true / false judgment condition, and the debugger corresponds to the diagnostic instruction state-member based on the debug information. A program debugging method for performing diagnostic processing on the basis of the debug information, by setting an interrupt point for diagnostics described above, and identifying that a program interrupt has occurred due to the interrupt point for diagnostics.