JP2000330823A - Device and method for debugging program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To set a brake point in each object. SOLUTION: A setting device 221 converts an object specified as a command argument of a brake point setting command inputted from an input device 1 and information concerned with a stop position into a pointer to an object storage area in its corresponding program and an execution address and stores these converted values in a brake information storage device 32 as brake point information. An execution code changing device 41 pads a brake code in an intra-program text area corresponding to the stored execution address. When an execution command is inputted from the input device 1, an execution control device 231 starts the execution of the program. When the execution of the program is stopped by the brake code during the execution of the program, a stop judging device 232 judges whether the execution of the program is to be restarted or not on the basis of the brake point information stored in the storage device 32.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to program debugging for an object-oriented language.

[0002]

2. Description of the Related Art Conventionally, in a debugging apparatus for an object-oriented language, setting a breakpoint on a method involves acquiring an execution address in a program corresponding to a method of interest from debug information or the like, and setting a break at that address. This is achieved by embedding the code.

[0003]

However, since the execution address of a method is generally common to all objects generated from the class defining the method, in the above-described conventional method, which object It is not possible to set a breakpoint by distinguishing which method belongs. Therefore, when there are a plurality of class objects having the method of interest during debugging, no matter which method of the object is executed, the execution of the program will be stopped by the breakpoint set for that method. This phenomenon occurs. Therefore, there is a problem that when debugging a method executed by a specific object, it takes a very long time and effort to reach the location.

A debugging device for an object-oriented language is required to always have a debugging function that is conscious of an object, such as displaying the state of an object and controlling execution of each object. The problem of not being able to do so is a great hindrance to debugging, and is a factor in reducing debugging efficiency.

An object of the present invention is to provide a program debugging system which solves this problem and enables a breakpoint to be set for each object.

[0006]

According to a first aspect of the present invention, there is provided a program debugging apparatus for designating an object when setting a breakpoint in a text area of a program in a program debugging apparatus for an object-oriented language. By setting such a breakpoint, even if there are a plurality of class objects sharing the text, a break function is provided that can stop only the execution of the specified object.

According to a second aspect of the present invention, there is provided a program debugging device for a program debugging device for an object-oriented language, wherein an object and a stop position specified in a command argument of a breakpoint setting command input from an input device are provided. A setting device that converts the information about the object into a pointer and an execution address to an object storage area in the corresponding program, and stores the value in the break information storage device as breakpoint information;
An execution code changing device for embedding a break code in a text area in a program corresponding to the stored execution address; an execution control device for starting execution of the program when an execution command is input from the input device; A stop judging device for judging whether or not to resume the execution of the program when the execution of the program is stopped by the break code, the stop judging device first obtains a current stop address, and then Searches the break information storage device for breakpoint information that includes an execution address that matches the current stop address, and if found, returns to the own object passed to the currently stopped method. The pointer contained in the found breakpoint information If the two pointers do not match, it is assumed that the object not targeted for the breakpoint execution has been executed, and the execution of the program is started again. In this state, the current stop position is output to the output device and the next command input is waited.

According to a program debugging method of the present invention, in a method of debugging a program for an object-oriented language, information on an object and a stop position specified in a command argument of a breakpoint setting command input from an input device is stored. A procedure for converting the pointer into an object storage area in the program corresponding to the execution address and an execution address, and storing the value as breakpoint information in the break information storage device, and a break in the program text area corresponding to the stored execution address. A step of embedding a code, a step of starting execution of a program when an execution command is input from the input device, and a step of restarting execution of the program when execution of the program is stopped by the break code during execution of the program. Whether or not The determining step includes first obtaining a current stop address, and then, in the break information storage device, there is breakpoint information including an execution address that matches the current stop address. Whether breakpoint information is found as a result of the search, and further, a step of obtaining a pointer to the own object passed to the currently stopped method, and a step of obtaining the pointer. A step of comparing whether or not the pointer matches the pointer to the object included in the found breakpoint information; and, as a result of the comparison, when the two do not match, it is assumed that the object not targeted for the breakpoint setting is being executed. The execution of the program is started again, but otherwise, the execution is stopped and the current And outputs to the output device a stop position, characterized in that it consists of a procedure to wait for the next command input.

[0009]

Next, embodiments of the present invention will be described with reference to the drawings.

Referring to FIG. 1 showing an embodiment of the present invention, the present debug apparatus comprises an input device 1 for inputting a debug command, a command processing device 2 for processing the input debug command, It includes a storage device 3 for storing information, a program control device 4 for directly controlling a program to be debugged, and an output device 5 for outputting a result of command processing.

The input device 1 includes a breakpoint setting command using the object specification information and the stop position specification information as arguments, a breakpoint release command using the breakpoint ID output after setting the breakpoint as an argument, a program execution Assume that a command is entered. In the breakpoint setting command, the specification of the object specification information can be omitted. In this case, the program is stopped by the specified method without distinguishing the objects.

The storage device 3 has a debug information storage device 31 and a break information storage device 32. The debug information storage device 31 stores in advance information such as addresses in a program corresponding to variable names and method names. Further, the break information storage device 32 stores a breakpoint target object and a value obtained by converting a stop position into a pointer to an object storage area and an execution address in the program, and a breakpoint management ID as one set of breakpoint information. To be stored.

The program control device 4 includes an execution code changing device 41 for embedding and restoring a break code in a program, a data acquisition device 42 for acquiring a value of a variable and a current stop address, and a program for executing a program. An execution device 43 is provided.

The command processing device 2 includes a command analysis device 21 for analyzing a debug command input from the input device 1.
And a break command processing device 22 for processing when a breakpoint setting / cancellation command is input,
When an execution command is input, the execution command processing unit 23 processes the command.

The break command processing device 22 includes a setting device 221 for setting a breakpoint and a release device 222 for releasing a set breakpoint.
The setting device 221 converts the object specification information and the stop position specification information specified in the command argument into a pointer to an object storage area in the program and an execution address using the debug information storage device 31 and the data acquisition device 42. And The information is stored in the break information storage device 32 together with the breakpoint ID. Then, the break code is embedded in the execution start address of the method by the execution code changing device 41. The release device 222 deletes the breakpoint information having the breakpoint ID specified in the command argument from the breakpoint storage device 32. If there is no other breakpoint information having the same execution address, the breakcode embedded in the execution address is released by the execution code changing device 41.

The execution command processing device 23 is an execution control device.
231 and a stop determination device 232. The execution control device 231
First, when the execution of the program is started by the program execution device 43 and the execution is stopped by the break code,
An inquiry is made to the stop determination device 232 as to whether or not to continue the execution. The stop determination device 232 acquires the current stop address from the data acquisition device 42, and checks whether or not there is information having the same execution address in the break point information stored in the break information storage device 32. If found, a pointer to the object passed to the currently executing method is acquired by the debug information and data acquisition device 42 stored in the debug information storage device 31 and stored in the breakpoint information. To see if it matches the pointer to the assigned object. If they do not match, the execution is resumed by the execution control device 231 again. In other cases, the execution is stopped as it is, and a stop message is output to the output device 5.

Next, the operation of this embodiment will be described first with reference to FIG. 1 and FIG.
Then, for details of each command processing, refer to Figs.
This will be described with reference to FIG. 4 and FIG.

When a command is input to the input device 1 (FIG. 2)
In step A1), the contents are supplied to the command analyzer 21. The command analysis device 21 analyzes the given command (step A2), and if it is a breakpoint setting command, executes the command to the setting device 221; if it is a breakpoint release command, it executes the release device 222; The contents of the command are given to the control device 231 and the processing of each command is performed in each device (step A).
3). Each device that executes the processing of these commands displays the result of the command processing on the output device 5 (step A4), and accepts a command input from the input device 1 again (step A4).
A1).

Next, the details of the breakpoint setting process will be described with reference to FIGS. Setting device 22
In step 1, it is checked whether or not the command argument includes object designation information (step B1 in FIG. 3). As a result, if the object specification information is included, the address at which the pointer to the object storage area in the program corresponding to the object specification information exists is obtained from the debug information storage device 31 (step B2). Then, the pointer to the object stored at the address is obtained by the data obtaining device 42 (step B3). On the other hand, if the command argument does not include the object designation information, the value of the pointer is set to 0x0 (step B4). Thereafter, the setting device 22 acquires an execution address in the program corresponding to the stop position information specified in the command argument from the debug information storage device 31 (step B5), and the execution code changing device 41 To embed a break code (step B6).

If all of these processes succeed, an ID for management is assigned to the breakpoint (step B7), and the ID, the pointer to the object and the execution address are set as a set of breakpoint information. Is stored in the break information storage device 32 (step B8).
Then, the breakpoint I assigned above to the output device 5
D is output (step B9). However, if any of these processes fails, an error is output to the output device 5 (step B10).

Next, the details of the breakpoint release processing will be described with reference to FIGS. Release device 22
Step 2 searches the break information storage device 32 for breakpoint information having the breakpoint ID specified by the command (step C1 in FIG. 4). As a result, when the breakpoint information is found, the information is deleted from the break information storage device 32 (Step C2). Next, a search is made from the break information storage device 32 for other breakpoint information that matches the execution address held by the deleted breakpoint information (step C3), and when no other breakpoint information is found Next, the break code embedded at the execution address in the program is released by the execution code changing device 41 (step C4). on the other hand,
If other breakpoint information is found, the break code is not released (step C4). If all the processing is successful, the deleted breakpoint ID is displayed on the output device 5 (step C5), and if it fails, an error is output (step C6).

Finally, the processing of the execution command will be described with reference to FIGS. The execution control device 231
The execution of the program is started by the program execution device 43 (step D1 in FIG. 3). At this time, when the program is stopped by the break code, the stop determination device 232 determines whether or not to continue the execution. Stop determination device 23
2 acquires the current stop position from the data acquisition device 42 (step D2) and searches the break information storage device 32 for breakpoint information including an execution address that matches the address (step D3). . As a result, if breakpoint information is found, it is checked whether the pointer to the object recorded in the breakpoint information is 0x0 (step D4) .If the pointer is 0x0, the object was specified at the time of setting the breakpoint. Therefore, the execution is stopped, and the current stop position is output to the output device 5 (step D8).

On the other hand, if the pointer to the recorded object is not 0x0, the data acquisition device 42 acquires a pointer to its own object passed as an argument to the currently stopped method (step D5). It is checked whether it matches the pointer to the recorded object (step D6). As a result, if they match, the current stop position is output to the output device 5 (step D8) .If they do not match, the execution control device 231 determines that a method of another object that is not a breakpoint target is being executed. The execution is continued again (step D7).

Next, another embodiment of the present invention will be described. Referring to FIG. 6, the present embodiment is different from the example in that program control device 6 has an object management device 44 in addition to the configuration of program control device 4 in the embodiment shown in FIG.

When the object management device 44 detects the release of the object stored in the break information storage device 32 during the execution of the program, it temporarily stops the execution of the program and sets the breakpoint ID for the released object. To the release device 222, and deletes the breakpoint corresponding to the specified ID. Thereafter, the execution is resumed by the execution control device 231.

The operation of the present embodiment will be described in detail with reference to the drawings. The processing of the breakpoint setting command and the release command is the same as the above-described operation described with reference to FIGS. Therefore, the processing of the execution command will be described with reference to FIG. 6 and FIG.

When an execution command is input from the input device 1, the execution control device 231 starts executing the program by the program execution device 43 (step D1 in FIG. 7). If the object management device 44 detects release processing for an object stored in the break information storage device 32 during execution of the program (step E1), the execution is stopped (step E2), and the breakpoint ID corresponding to the object is stopped. Is notified to the release device 222. The release device 222 deletes the breakpoint corresponding to the specified ID, similarly to the case where the breakpoint release command is input from the input device 1 (step E3). Thereafter, the execution is restarted by the execution control device 231 (step E4). When the program is stopped by the break code without detecting the release of the object (step E1), the same processing as steps D2 to D8 in FIG. 5 is performed.

When a breakpoint is set by specifying an object, the breakpoint is valid only while the specified object exists in the storage area without being released. The present embodiment has a function of automatically deleting a breakpoint that is no longer valid by detecting the release of an object and avoiding a program stop operation due to an illegal breakpoint.

[0029]

An effect of the present invention is to increase the debugging efficiency of a program described in an object-oriented language. The reason is that a breakpoint for a text area of a program can be set for each object so that debugging focusing on the object is facilitated.

[Brief description of the drawings]

FIG. 1 is a block diagram of one embodiment of the present invention.

FIG. 2 is a flowchart showing an overall operation of the embodiment shown in FIG.

FIG. 3 is a flowchart showing a breakpoint setting process in the embodiment shown in FIG. 1;

FIG. 4 is a flowchart showing a breakpoint release process in the embodiment shown in FIG. 1;

FIG. 5 is a flowchart showing processing of an execution command in the embodiment shown in FIG. 1;

FIG. 6 is a block diagram of another embodiment of the present invention.

FIG. 7 is a flowchart showing processing of an execution command in the embodiment shown in FIG. 6;

[Explanation of symbols]

 Reference Signs List 1 input device 2 command processing device 3 storage device 4 program control device 5 output device 6 program control device 21 command analysis device 22 break command processing device 23 execution command processing device 31 debug information storage device 32 break information storage device 41 execution code change device Reference Signs List 42 data acquisition device 43 program execution device 44 object management device 221 setting device 222 release device 231 execution control device 232 stop determination device

Claims (4)

[Claims] In a program debugging apparatus for an object-oriented language, when a breakpoint is set in a text area of a program, a class object sharing the text by setting a breakpoint specifying the object. A program debugging device having a break function capable of stopping only execution of a specified object even when a plurality of programs exist. 2. A debugger for a program for an object-oriented language, comprising: information relating to an object and a stop position specified in a command argument of a breakpoint setting command input from an input device; A setting device that converts a pointer to an object storage area and an execution address and stores the value as breakpoint information in a break information storage device; and an execution code for embedding a break code in a text area in a program corresponding to the stored execution address A change device, an execution control device that starts execution of a program when an execution command is input from the input device, and restarts execution of the program when execution of the program is stopped by the break code during execution of the program. Determine whether or not The stop determination device first obtains a current stop address, and then has breakpoint information including an execution address that matches the current stop address in the break information storage device. Search for, and if found, further obtain a pointer to its own object passed to the currently stopped method, which matches the pointer to the object included in the found breakpoint information If the two do not match, execution of the program is started again assuming that an object not targeted for breakpoint setting has been executed, but otherwise, execution has been stopped. Output the current stop position to an output device and wait for the next command input. Grayed apparatus. 3. An object that, when executing the program, detects release processing of an object stored in the break information storage device, stops execution of the program, and notifies release of a breakpoint corresponding to the object. 3. The program debugging device according to claim 2, further comprising a management device. 4. A method for debugging a program for an object-oriented language, comprising: information relating to an object and a stop position specified in a command argument of a breakpoint setting command input from an input device; Converting a pointer to an object storage area and an execution address and storing the value as breakpoint information in a break information storage device; embedding a break code in a program text area corresponding to the stored execution address; A step of starting execution of a program when an execution command is input from the input device; and determining whether or not to resume execution of the program when execution of the program is stopped by the break code during execution of the program. And determining The procedure includes: first obtaining a current stop address; then, searching the break information storage device for breakpoint information including an execution address that matches the current stop address. If the breakpoint information is found, further obtaining a pointer to the own object passed to the currently stopped method, and setting the obtained pointer to the object included in the found breakpoint information. And a procedure for comparing whether or not the pointers match, and if the two do not match as a result, the execution of the program is started again assuming that an object not targeted for the breakpoint setting is being executed. In other cases, the current stop position is output to the output device while execution is stopped. Debug a program characterized by comprising a procedure to wait for the next command input.