JPH0764819A - Debugger - Google Patents

Abstract

PURPOSE:To provide a debugger which gives a break for a desired condition (function and argument) to temporarily stop a program. CONSTITUTION:A start instruction of debugging processing, a break condition, etc., are inputted through an input part 1. The break condition is set as a pair of a function name and the value of an abnormal argument given to the function and is stored in a storage part 3. A program execution part 2 performs the normal debugging processing in accordance with the start instruction and sends a function to a break discriminating part 4 at the time of finding the function in instructions of the program. The discriminating part 4 compares the argument in the break point set position detected by the program execution part 2 and the break condition stored in the storage part 3 with each other to discriminate whether the break processing should be executed or not, and, when the condition is satisfied, the break processing is executed, and the source code of the function to which the break point is set, is displayed on a display part 5.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a debugging device, and more particularly to improvement of a break processing mechanism.

[0002]

As is well known, during program development,
In order to detect a bug existing in a source level or assembler level program and correct it to complete the program, the program under development is input to a debug processing device called a debugger, debugging system, etc. It's supposed to run from the beginning.

A breakpoint may be set when performing the debug process. That is, the name of a function whose program execution is desired to be stopped is input in advance, and when a certain function in the program to be debugged is called, the execution of the program is stopped so that the subsequent processing can be performed interactively.

[0004]

However, the above-mentioned conventional debug device has the following problems.
That is, an abnormal argument to a function (for example, 0 or NULL
When fixing the bug that the pointer is given), the conventional break processing based on the function name causes the execution of the program to be suspended even if the function is given a normal argument. Therefore, after that, the debug processor has to interactively proceed with the execution of the program until an abnormal argument is given, and the work is complicated. In particular, depending on the program, when the break setting function is called several tens to several hundreds of times, the above-described debug processing is practically difficult.

The present invention has been made in view of the above background, and an object of the present invention is to provide a debugging device capable of breaking and temporarily stopping a program under a desired condition (function and argument). To do.

[0006]

In order to achieve the above-mentioned object, in a debugging device according to the present invention, a processing means for performing a debug process on a given program, and the program temporarily during the debug process. The program includes a storage unit that stores a break condition to be stopped, and a break determination unit that determines whether or not a portion of the program being executed that satisfies the break condition stored in the storage unit is included, and the break condition is a function. The name and the value of a given argument given to the function are stored as a pair.

[0007]

With the given program, the processing means is executed to carry out the usual debug processing. Further, prior to the start of this debug processing, a break point is set and the break condition is stored in the storage means. Then, during the debug processing, the break determination means detects whether or not there is a function name stored in the storage means in the instruction of the program being executed, and if there is that function name, the function is The value of the given argument is referred to and it is determined whether or not it is the predetermined value stored in the storage means. Then, when the function name stored in the storage means and the argument value match, break processing is performed. In other words, even if the function names are the same, if the argument values are different, the program execution (debug processing) continues without breaking.

[0008]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT A preferred embodiment of a debug device according to the present invention will be described in detail below with reference to the accompanying drawings. FIG. 1 shows an embodiment of a debug device according to the present invention. Same figure (A)
A middle numeral 1 is an input unit such as a keyboard and a mouse, and is adapted to input a start instruction of debug processing, a breakpoint setting location and conditions.

The output of the input unit 1 is connected to the program execution unit 2 and the storage unit 3. The program execution unit 2 executes a program to be processed, various predetermined debug commands, and the like based on the activation instruction given from the input unit 1, and is a so-called debugger main body. The program execution unit 2 sends the function name to the break determination unit 4 at the next stage each time the function is drawn.

The storage unit 3 stores break conditions. In this example, as shown in FIG. 1B, a function name for temporarily stopping the program and arguments given to the function are stored. Creating a table that pairs values (abnormal arguments).

Then, the break determination unit 4 compares the argument at the breakpoint setting location detected by the program execution unit 2 with the break condition stored in the storage unit 3 to determine whether or not to perform break processing. A judgment is made and the judgment result is sent back to the program execution unit 2, and when a break occurs, the source code of the function in which the breakpoint is set is sent to the display unit 5 and the source code concerned is displayed there. ing.

Next, the operation of the above embodiment will be described with reference to the flow chart shown in FIG. That is, first, a debug process activation instruction is input to the program execution unit 2 via the input unit 1, and a breakpoint is set (a function to be broken and an abnormal argument are paired and stored in the storage unit 3) (S101). , 102). In this example, FIG.
As shown in (B), a certain function f is used as a break condition.
When (x) is called, breaks when the value of the argument x given to the function is "0".

Then, the program execution section 2 sequentially executes each instruction and command in the preset program (S103). Then, if there is a function in the program, it is sent to the break determination unit 4, and it is determined whether or not the function is f (x) which is one of the break conditions (S104). If it is not f (x), a continuation instruction is sent to the program execution unit 2, and the program execution unit 2 continues execution of the instruction and the command.

On the other hand, if the function is f (x), the value of the argument given when the function is called is referred to, and whether the value is an abnormal value (0) stored in the storage unit 3 or not. If it is not 0, the process returns to step 103 to continue the execution of the program. When it is 0, break processing is performed, the program is temporarily stopped, and the source code of the function at that time is displayed on the display unit 5 (S1
07, 108).

That is, according to this example, even if the function f (x), which is one of the break conditions, is called in the program, the value of the argument input thereto is normal (in this example, In the case of (other than 0), the program continues to be executed without break processing, and the break occurs only when the argument has an abnormal value. Therefore, the function at the time of occurrence of the problem can be identified by one break processing.

In the above embodiment, the function of the break condition and the value of the argument are one for the sake of convenience of explanation, but the present embodiment is not limited to this, and a plurality of values may be set. .

[0017]

As described above, in the debug device according to the present invention, as a breakpoint setting, the value of the function and the argument called to the function are set as a pair, and the break processing is performed when the both conditions are matched. Therefore, even if the same function as the function name of the breakpoint stored in the storage means is called, the value of the argument given to that function is normal (different from the one stored in the storage means). If so, program execution continues without breaking. Therefore, the function at the time of occurrence of a problem can be specified by one break processing, and the debugging efficiency is improved.

[Brief description of drawings]

FIG. 1A is a block diagram showing an embodiment of a bag device according to the present invention. (B) is a diagram showing an example of a data structure stored in the storage unit.

FIG. 2 is a flowchart illustrating an operation.

[Explanation of symbols]

 1 input section 2 program execution section (processing means) 3 storage section 4 break determination section 5 display section

Claims (1)

[Claims] 1. A processing unit for performing a debug process on a given program, a storage unit for storing a break condition for temporarily stopping the program during the debug process, and a storage unit for the program being executed. And a break determining means for determining whether or not there is a stored portion that satisfies the break condition, and the break condition is stored as a pair of a function name and a value of a predetermined argument given to the function. .