JPH0695915A - Method for debugging processing - Google Patents

Abstract

PURPOSE:To improve debugging efficiency by continuing tracing when a storage area is not changed, and stopping tracing only at the time of a brake point in a prescribed condition. CONSTITUTION:A breakpoint is set up (S1) and non-conditional setting or conditional setting is determined (S2) at the time of setting up the breakpoint. In the case of conditional setting, a condition indicating which processing requires the stop of program execution at its end is set up (S3). Then, whether the setting of the breakpoint ends or not is judged (S4). After ending the setting of the breakpoint, the execution of a source program is started (S5), a symbolic debugger is sequentially executed, and when a condition set up in each breakpoint is satisfied, the exection of the program is stopped (S6). In other cases, the continuation of program execution is judged (S7).

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a debug processing method mainly by a symbolic debugger for detecting and diagnosing and correcting an error in a program during development.

[0002]

2. Description of the Related Art FIG. 6 shows a general block configuration of a debug system for performing a debug process. A source program (1) is compiled into a load module (3) by a compiler (2), and the load module (3) is compiled. Is debugged by the symbolic debugger (4). Further, the symbolic debugger (4) has a breakpoint setting function of interrupting the program being executed by the monitor program used during debugging. For example, when the source program processed according to the flowchart shown in FIG. 7 is debugged by the symbolic debugger (4),
When it is desired to interrupt the execution of the program and confirm the system state in the process 6 after the process 5, a breakpoint is set in the process 6 and the process is executed.

[0003]

However, the execution of the program stops at the breakpoint of the process 6 not only after the process 5, but also after any of the processes 3 and 4 is not intended. Even in the situation, the execution of the program is stopped. Therefore, the intended situation,
In other words, the trace must be repeatedly stopped and continued until the situation of the process 6 after the process 5 is reached, and the operator must perform an operation for restarting the trace each time the process is stopped. There is a drawback to decrease.

Further, since it is troublesome for the operator to carry out an operation for restarting the tracing each time it is stopped,
It is also possible to preset how many times the required point is the break point, count the breakpoints, and stop the trace only at the breakpoint in the required situation, but the required situation is It is necessary to find in advance how many break points the breakpoints are, and the problem of reducing the efficiency of the debug processing cannot be solved even if complicated operations can be eliminated.

Therefore, it is a technical object of the present invention to provide a debug processing method in which a breakpoint can be set with a condition added so that processing efficiency is markedly improved.

[0006]

According to the present invention, the debugging process is performed by the following method as a technical means for achieving the above-mentioned problems. After setting a breakpoint at an arbitrary point in the source program, stop the trace at the breakpoint and the trace at the breakpoint in the debug processing method that stops the trace when the trace position reaches the breakpoint. A condition for causing the condition to be stored in a memory means, and a memory area for determining the condition is provided in the memory means, and the condition is judged when a condition that matches the content of the condition is obtained during execution of a trace. For changing the contents of the storage area for, comparing the contents of the storage area for determining the condition when the trace position comes to the breakpoint, and continue tracing when the contents have not changed, And the memory to judge the condition by stopping the trace only when the contents are changed. And characterized by performing the procedure for changing to restore the rear contents.

[0007]

For example, the processing 6 after the processing 5 of the source program
If you want to stop the trace at the time of, set a breakpoint in process 6 and process 5 as the content of the condition.
To set. Then, during the execution of the trace, processing 5
When it comes to, the storage area for judging the condition that has been cleared in advance is set. After that, when the trace position comes to the process 6, the trace is stopped by comparing and determining that the storage area for determining the condition is set, that is, the content has been changed from clear to set. Therefore, when the trace position reaches the breakpoint before the contents of the storage area for determining the condition is changed,
Tracing is continued because the storage area for determining the condition is not changed, and the tracing is stopped only at the break point in the predetermined situation where the process 5 to the process 6 is performed, so that the debugging efficiency is significantly improved. be able to.

[0008]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A preferred embodiment of the present invention will be described in detail below with reference to the drawings. FIG. 1 shows a schematic block diagram of a system relating to the implementation of the debug processing method of the present invention.
It is composed of a central processing unit (5), an internal storage device (6), an external storage device (7), a display device (8) and an input device (9). The internal storage device (6) has a storage area for storing breakpoint conditions and a storage area for condition determination.

First, an outline of the debug processing of the present invention will be described with reference to the flowchart of FIG. First, a break point is set (step S1), and it is decided whether the break point is unconditional or conditional (step S2). If it is conditional, a condition is set to stop the execution of the program only when which process is finished (step S3). Then, it is determined whether or not the setting of the break points is completed (step S4), and when the break points are set at a plurality of points, the process jumps to step S1 to perform the same break point setting process. Then, when the setting of the breakpoint is completed, the execution of the source program is started (step S
5) The symbolic debugger sequentially executes the program to stop the execution of the program when the above-mentioned set conditions are satisfied at each breakpoint (step S6), and otherwise continues the execution of the program. Is determined (step S7) and the process jumps to step S6.

If the above-mentioned processing is performed for the source program shown in the flow chart of FIG. 7, a breakpoint is set in processing 6 in step S1.
Conditional is selected in step S2, and step S3
In step 5, processing 5 is set as a condition. Then, the source program is executed (step S5), and the execution of the program is stopped only when the condition that is the breakpoint of the process 6 after the process 5 is executed is satisfied in step S6.

Next, FIG. 3 showing the process of the flowchart of FIG. 2 in more detail and FIG. 4 showing a part of the process of FIG.
In addition, each flowchart of FIG. 5 will be described. Figure 3
First, it is determined whether or not a breakpoint is set (step S10). If it is determined that the breakpoint is set, a breakpoint setting process is executed (step S11). In FIG. 4 showing this breakpoint setting processing, the address of the breakpoint is registered in the storage area of the internal storage device (6) (step S111), and subsequently it is determined whether or not it is conditional ( In step S112), if there is a condition, the content of the condition is stored in the storage area, a storage area for condition determination is secured, and the flag for determination of this storage area is cleared (step S113).

If the setting process of the break point is carried out in this way, then it is judged whether or not the information is displayed, and if it is displayed, the information display process is executed (step S13). After that, it is determined whether or not to move to the execution of the trace, that is, whether or not the setting of the break point is completed. If it is determined that the setting of the break point is not completed, the process jumps to step S10. The breakpoint setting process is repeated, and when it is determined that the setting is completed, a trace is performed for each step of the source program (step S15), and a breakpoint determination process is performed for each trace (step S16).

In FIG. 5, which shows a flowchart of this breakpoint determination processing, it is first determined whether or not it is a breakpoint (step S161), and, for example, processing 3 or processing during tracing the source program shown in FIG. If it is determined in step 6 that the breakpoint has been reached after step 4, the condition determination area is then determined (step S162), but the condition determination area remains cleared and set in step S113. It is determined that there is not (step S165),
Tracing is continued by jumping to step S15 in FIG. Then, when the processing 5 set as the condition in the source program of FIG. 7 is traced, it is determined to be the condition point of the conditional break point (step S163), and after setting the condition determination area, the process of FIG.
Jump to step S15 and continue tracing.
Then, when the process moves from the process 5 to the process 6, it is determined that the breakpoint is conditional and conditional (steps S161 and 162), and further it is determined that the condition setting area is set (step S165), and the condition is set. Stop the trace after clearing the judgment area. If it is determined that the trace has ended (step S167), the end processing is performed (step S168), then the trace is stopped, and it is determined that the breakpoint is an unconditional break point (step S162). If you want to stop the trace immediately. In any of the above cases, when the trace is stopped, the process proceeds to step S17 in FIG. 3 to determine whether or not to display information (step S17), and if it is displayed, the information display process is executed (step S18). After that, it is determined whether or not the trace is continued (step S19). If the trace is continued, the process jumps to step S15 to continue the trace, otherwise the process jumps to step S17.

[0014]

As described above, according to the debug processing method of the present invention, the breakpoint and the condition for stopping the trace by this are stored in the storage means, and the storage area for determining the condition in the storage device. Is provided to change the contents of the storage area for judging the condition when the situation matches the contents of the condition during execution of the trace, and trace before the contents of the storage area for judging the condition are changed. When the position comes to the break point,
Tracing is continued because the storage area for determining the condition has not been changed, and the trace is stopped only when the content of the storage area for determining the condition has been changed and a break point in a given situation has occurred. Therefore, the trace can be stopped only in a required situation without requiring a complicated operation and without any pre-processing of the debug processing, and the debugging efficiency can be remarkably improved.

[Brief description of drawings]

FIG. 1 is a schematic block diagram of a system according to an embodiment of the present invention.

FIG. 2 is a flowchart showing a schematic process of debugging of the above.

FIG. 3 is a flowchart showing detailed debug processing of the same.

FIG. 4 is a flowchart showing details of steps of block point setting processing in FIG.

5 is a flowchart showing details of steps of a breakpoint determination process in FIG.

FIG. 6 is a block configuration diagram of a general debug system to which the present invention is applied.

FIG. 7 is a flowchart of an example of a source program that can be debugged according to the present invention.

[Explanation of symbols]

 1 Source Program 4 Symbolic Debugger 5 Central Processing Unit 6 Internal Storage Device

Claims (1)

[Claims] 1. A debug processing method for setting a breakpoint at an arbitrary position of a source program and then stopping the trace to check the system state when the position to be traced reaches the breakpoint, the breakpoint and the breakpoint. The condition for stopping the trace at the point is stored in the storage means, and the storage area for determining the condition is provided in the storage means, and when the condition of the trace condition is met during execution of the trace. The contents of the storage area for determining the condition are changed, and the contents of the storage area for determining the condition are compared when the trace position comes to the breakpoint, and when the contents are not changed, Continue the trace and stop the trace only when the contents are changed to judge the condition. A debug processing method characterized in that the contents of the storage area for saving are changed so as to be restored.