JPH0695917A - Method for specifying execution interrupting point - Google Patents

Abstract

PURPOSE:To speed up the setting processing of interruption points by setting up interruption points on all corresponding positions specified by flags and validating the flags so that the flags are reused as they are at the time of inputting a succeeding sub command and specified interruption points can be set up or deleted. CONSTITUTION:Debugging information 8 storing whether interruption points can be set up or not in a program 6 to be debugged and an execution interrupting point specification execution validating flag 9 for expressing whether interruption points (NEXT) in the program 6 are valid or invalid are prepared. When the flag 9 is invalid correspondingly to an execution interrupting point specification executing instruction (NEXT), the interruption points (NEXT) are set up in all lines allowed to set up interruption points based upon the information 8 and validated, and then the program 6 is executed and interrupted at the interruption points. When the flag is valid on the other hand, the program 6 is executed and interrupted at the interruption points.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an execution interruption point designating method for designating an interruption point for interrupting the execution of a program, and an execution interruption point of a debugger for realizing a function of executing a user program up to a designated position. It is related to the designation method.

[0002]

2. Description of the Related Art In a conventional debugger, when a user program is executed up to a position specified by the user and interrupted, the specification method has some flexibility so that the user can easily use the program. For example, in addition to specifically specifying execution up to the "1000th line" of the user program, execution up to the "line at which the breakpoint is executed" is permitted.

[0003]

For this reason, it is difficult to exactly obtain the position designated by the user in the processing of the debugger. For example, if the currently suspended position is an IF statement and if "execute to the next execution position" is specified, is the next execution position the THEN clause?
Since it depends on the condition of the conditional expression of the IF statement whether it becomes the LSE clause is difficult to find.

Therefore, the debugger sets breakpoints at all the positions that are likely to correspond to the positions designated by the user, executes the user program, and interrupts the user program at any of the set breakpoints. In that case, all the set break points were deleted.

Therefore, when there is an instruction to specify an execution break point, the break points are set at all positions that may correspond to the designation, and if any of them is interrupted, all the break points are deleted. When the instruction to specify the execution break point is given again, the setting of the break point is repeated at all the positions that may be applicable.

Therefore, the larger the number of positions that may correspond to the position designated by the user, the more the setting and deletion of the break point is repeated each time, which deteriorates the performance of the execution break point designation function. There was a problem.

The present invention solves these problems.
Execution break point specification Execution valid flag is set to set the break points to all positions that may correspond to the specification and enable the flag, and it is reused as it is when the next subcommand is input, and the specified break point The purpose is to speed up the process of setting the interruption point by setting or deleting the interruption point.

[0008]

[Means for Solving the Problems] Means for solving the problems will be described with reference to FIG. In FIG. 1, the debug information 8 is information that stores whether or not the breakpoint 6 of the program 6 to be debugged can be set.

The execution break point designation execution valid flag 9 is a flag indicating whether or not a break point is set in the program 6 to be debugged. The break point (NEXT) is a break point set at all positions where the next break will occur.

The break point (AT) is the break point set at the designated position.

[0011]

According to the present invention, as shown in FIG. 1, the debug information 8 is issued when the execution breakpoint designation execution valid flag 9 is invalid in response to the execution breakpoint designation execution instruction (NEXT) from the user.
Breakpoints (NE
After setting and enabling XT), program 6
Is executed to interrupt at the interruption point, while the program 6 is executed to interrupt at the interruption point when it is valid.

Further, the interruption point (AT) is set at the position of the designated line number in response to the user's interruption point setting instruction (AT). In addition, all interruption points (NE
XT) is deleted and the execution interruption point designation execution valid flag 9 is set to invalid, then the execution of the program 6 is restarted, and the processing is terminated at the interruption point (AT) or without interruption.

Further, the program 6 is used to set the break point.
Embed an SVC instruction that calls the debugger in the corresponding position of
The instruction is restored to the original instruction that was saved.

Therefore, execution interruption point designation execution valid flag 9
Is set to set break points at all positions that may correspond to the designation and enable the flag 9 so that it can be reused as it is when the next subcommand is input, or the designated break point (AT) can be set. By setting or deleting the break point, the process of setting the break point can be speeded up.

[0015]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, the construction and operation of an embodiment of the present invention will be described in detail with reference to FIGS.

FIG. 1 shows a block diagram of an embodiment of the present invention.
In FIG. 1, an input unit 1 is for inputting various instructions and the like, and here, an execution interruption point designation execution instruction (NE
XT) 2, user interruption point setting instruction (AT) 3, execution resumption instruction (GO) 4, and the like.

The execution interruption point designation execution instruction 2 is an instruction (for example, NEXT) for setting an interruption point at all positions in the program 6 to be debugged that will be interrupted next.
The setting of the break point is to embed the call instruction (SVC instruction) of the debugger in the designated position of the program 6 to be debugged and save the original instruction.

The user break point setting instruction 3 is an instruction to set a break point at a position designated by the user. For example 100
It is an instruction (for example, AT) to set an interruption point on the 0th line.
The execution resumption instruction 4 is an instruction (for example, GO) for resuming the execution of the program 6 from a state where the user has interrupted.

The debugger processing unit 5 is for performing debugging. Here, in accordance with various instructions from the input unit 1, a break point is set in the program 6 to be debugged, deleted, or executed. It is something to do.

The program 6 is a program to be debugged and is, for example, a user program as shown in FIG. The memory 7 stores various data, and here stores the debug information 8.

The execution break point designation execution valid flag 9 indicates the break point (N) set in correspondence with the execution break point designation execution instruction 2.
This is a flag for setting whether EXT) is valid or invalid. FIG. 2 shows an example of a user program of the present invention. The number on the left is the line number. For example, 000100 has a line number of 1.
It is line 00.

000100 IDENTIFICATION DIVISION. Describes that the definition section is described below the line number 100. Similarly, it is described that the procedure section is described below the line number 800.

FIG. 3 shows an example of debug information of the present invention.
This is to set a break point in association with a line number, which is set as "impossible" or "possible". In response to the user's execution instruction 2 for specifying the execution break point, when setting break points at all the positions where the next break will occur, the line numbers that are set to "possible" in the debug information example Set a break point at. For example, line number 1000
To the line number 2200, and the break point is not set to the line number 2200 (the break point is not set because the position does not correspond to the position where the break will occur).

FIG. 4 shows an example of flags and instructions according to the present invention. FIG. 4A shows an example of the execution interruption designation execution valid flag. The execution interruption designation execution valid flag 9 corresponds to the execution interruption designation execution instruction 2 when the interruption point is set at the position of the line number for which the interruption point can be set by referring to the debug information 8. Is set to "valid", while "invalid" is set when not set (described later with reference to FIG. 5).

FIG. 4B shows an example of execution instruction designating an execution interruption point. This execution interruption point designation execution instruction 2 indicates that the subcommand name is, for example, "NEXT" and that the interruption points are set at all positions from the current position of the program 6 to be debugged that will be interrupted next. It is a subcommand.
Specifically, a break point is set at a position (line number) set as “enabled” in the example of the debug information 8 of FIG. 3 (that is, control is passed to the debug processing unit 5 by embedding the SVC instruction) Save settings and original instructions).

FIG. 4C shows an example of a user interruption point setting instruction. The user break point setting instruction 3 has a subcommand name of "AT", for example, and sets a break point in a line designated by an operand in the program 6 to be debugged. Here, a break point is set at the position of line number 1300.

FIG. 4D shows an example of an instruction to restart execution.
This execution resumption instruction 4 has a subcommand name of "G
It is O "and is an instruction to restart the execution from the position where the program 6 to be debugged was interrupted.

Next, the operation of the configuration of FIG. 1 will be described in detail in the order shown in the flowchart of FIG. In FIG. 5, S1 initializes the execution breakpoint instruction execution valid flag 9 to "invalid". This sets the execution breakpoint designation execution valid flag 9 to "invalid" before starting the debugging of the program 6 to be debugged, and initializes it when the breakpoint (NEXT) is not set.

In step S2, a sub command is input. This is the subcommand "NEX" shown in FIG.
The user inputs "T", "AT", "GO", etc. from the input unit 1 of FIG.

In S3, the subcommand name is NEXT, A
Either T or GO is discriminated. In the case of NEXT, since the execution interruption point designation execution instruction 2 is input, S
From 4 to S8, the interruption point (NEXT) is set, the execution interruption point designation execution valid flag 9 is set valid, and the execution of the user program (program 6) is restarted. In the case of AT, since the user's interruption point setting instruction 3 is input, the interruption point (AT) is set at the position of the line number designated by the operand in S9. In the case of GO, since the execution restart instruction 4 is input, all the interruption points (NEXT) are deleted when the execution interruption point designation execution valid flag 9 is valid in S10 to S12, S7, and S8. After the execution interruption point designation execution valid flag 9 is invalidated, the execution of the user program (program 6) is restarted. This will be described below.

In S4, "N" is set as the subcommand name in S3.
Since it has been determined that "EXT" has been input, it is determined whether the execution interruption point designation execution valid flag 9 is valid or invalid. If it is valid, the process proceeds to S7, and if it is invalid, the process proceeds to S5.

In step S5, since the execution interruption point designation execution valid flag 9 is determined to be invalid in step S4, the NEXT interruption point (NEXT) is set in all the lines in which the interruption points can be set. Specifically, this is at the break point (N
EXT) is set (specifically, the SVC instruction is embedded and the original instruction is saved).

S6 is an execution interruption point designation execution valid flag 9
Set to “Enabled”. As a result, the interruption point (NEX
The fact that T) is set valid is stored, and the fact that it is set for reuse next time is stored.

In step S7, the execution of the user program (program 6) is restarted. This restarts the execution of the user program after setting the interruption point (NEXT) and enabling the execution interruption point designation execution valid flag 9 in S5 and S6 (or when it has already been set previously).

In step S8, it is determined whether the interruption has occurred at the interruption point of NEXT or AT. If it is interrupted, the process returns to S2. If it is not interrupted, it is executed until the end of the user program and then terminated.

In S3 above, the subcommand name "NEXT"
If the input is, the steps S4 to S8 make it possible to reuse the previously set break point (NEXT) when the execution break point designation execution valid flag 9 is "valid", thereby reducing the labor for setting. On the other hand, when the execution break point designation execution valid flag 9 is "invalid" at the first time, a break point (NEXT) is set and the execution break point designation execution valid flag 9 is set to "valid".

Next, in S9, since it is found that "AT" is input as the subcommand name in S3, AT is placed at the position of the line number designated by the operand of "AT" (user break point setting instruction 3). Set the break point (AT) of. this is,
For example, in the case of the subcommand name “AT” in FIG. 4C, the break point (AT) is set on the line with the line number “1300” specified by the parameter. Then, the process returns to S2.

When the subcommand name "AT" is input in S3 above, an interruption point (AT) is set in the position of the line number designated by the operand in S9. As a result, it becomes possible to set an interruption point (AT) on a line individually designated by the user.

In S10, since it was found that "GO" was input as the subcommand name in S3, it is determined whether the execution interruption point designation execution valid flag 9 is valid or invalid. Sometimes it goes to S7.

In step S11, since it is determined in step S10 that the execution interruption point designation execution valid flag 9 is valid, all the interruption points (NEXT) of NEXT are deleted. In S12, the execution interruption point designation execution valid flag 9 is set to be invalid. And S7
Proceed to.

In step S7, the execution of the user program (program 6) is restarted. This is to restart the execution of the user program after deleting the interruption point (NEXT) and disabling the execution interruption point designation execution valid flag 9 in S11 and S12.

In step S8, it is determined whether the AT has been interrupted. If it is interrupted, the process returns to S2. If it is not interrupted, it is executed until the end of the user program and then terminated.
When the subcommand name "GO" is input in S3 above, S10 to S12, S7, and S8 delete the breakpoint (NEXT) when the execution breakpoint designation execution valid flag 9 is "valid", Resume execution. As a result, the break point set by the subcommand name "NEXT" (N
EXT) and delete execution point designation execution valid flag 9
Can be disabled.

Next, a specific example will be described with reference to the flowchart of FIG. (1) Input the first subcommand name "NEXT". When the subcommand name "NEXT" (execution breakpoint designation execution instruction) is input, the debugger processing unit 5 checks whether the execution breakpoint designation execution valid flag 9 is "invalid".
At the first time, since it is invalid, the break point (NEXT) is set to all the lines where the break point setting of the debug information 8 in FIG. 3 is “enabled”, and the execution break point designation execution valid flag 9 To “enable”. When the execution of the user program (program 6) is restarted, it is interrupted at 1000 lines.

(2) Subcommand name "NEX" for the second time
Input T ". When the subcommand name" NEXT "(execution breakpoint designation execution instruction) is input, the debugger processing unit 5 checks the execution breakpoint designation execution valid flag 9. Since it is valid here, , When the execution of the user program (program 6) is restarted, it is interrupted at line 1100.

(3) Third subcommand name "AT
1300 ”. When the subcommand name“ AT ”(user break point setting instruction) is input, the debugger processing unit 5 searches the debug information 8 for a line corresponding to the line number 1300 specified by the operand, and Set the break point (AT) at the position.

(4) Fourth subcommand name "GO"
Enter. When the subcommand name “GO” (execution restart instruction) is input, the debugger processing unit 5 checks the execution interruption point designation execution valid flag 9. Since it is enabled here,
After deleting the breakpoints (NEXT) set in all the lines for which the breakpoint setting of the debug information 8 is “enabled”, the execution breakpoint designation execution valid flag 9 is set to “invalid”. When the execution of the user program (program 6) is restarted, it is interrupted at line 1300 here.

(5) Fifth subcommand name "GO"
Enter. When the subcommand name “GO” (execution restart instruction) is input, the debugger processing unit 5 checks the execution interruption point designation execution valid flag 9. Here, since it is invalid, when the execution of the user program (program 6) is restarted, the interruption point is not reached here, and the process ends.

[0048]

As described above, according to the present invention,
An execution break point designation execution valid flag 9 is provided to set a break point (NEXT) at all positions that may correspond to the designation, and the execution break point designation execution valid flag 9 is validated. Since the configuration that reuses the input as it is, sets a specified break point (AT), or deletes the break point is adopted, speeds up the setting process of the break point during debug processing. be able to. In particular, input the subcommand name "NEXT" to set the break point (NEXT) on all lines that may be interrupted and set the execution break point designation execution valid flag 9 to be valid, and the next subcommand name " It can be reused at the time of inputting “NEXT”, eliminating the wasteful process of setting and deleting the interruption point (NEXT) every time conventionally, and speeding up can be achieved.

[Brief description of drawings]

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

FIG. 2 is an example of a user program of the present invention.

FIG. 3 is an example of debug information of the present invention.

FIG. 4 shows examples of flags and instructions according to the present invention.

FIG. 5 is a flowchart explaining the operation of the present invention.

[Explanation of symbols]

 1: Input part 2: Execution break point designation execution instruction (NEXT) 3: User break point setting instruction (AT) 4: Execution restart instruction (GO) 5: Debugger processing part 6: Debug target program (user program) 7: Memory 8: Debug information 9: Execution breakpoint specification execution valid flag

Claims (4)

[Claims] 1. In an execution breakpoint designating method for designating an breakpoint for interrupting the execution of a program, debug information (8) storing whether or not the breakpoint of a program (6) to be debugged can be set, and a program to be debugged. Break point of (6) (NEXT)
Has an execution-breakpoint-designated-execution-effective flag (9) that indicates whether it is valid or invalid. At that time, after setting and setting the break point (NEXT) to all lines where the break point can be set in the debug information (8), the program (6) is executed to break at the break point. On the other hand, the execution breakpoint designating method characterized in that the program (6) is executed to suspend at the breakpoint when it is valid. 2. A user interrupt point setting instruction (AT) from the user
Corresponding to, the break point (AT) at the position of the designated line number
2. The execution interruption point designating method according to claim 1, wherein 3. A program (6) after deleting all the interruption points (NEXT) and setting the execution interruption point designation execution valid flag (9) to invalid in response to the execution resumption instruction (GO) from the user. 3. The execution interruption point designating method according to claim 1 or 2, wherein the execution of (1) is restarted and the processing is terminated at the interruption point (AT) or without interruption. 4. The setting of the break point includes embedding an SVC instruction for calling a debugger at a corresponding position of the program (6) and saving the original instruction to delete the break point.
4. The execution breakpoint designating method according to claim 1, wherein the SVC instruction is restored to the original instruction that has been saved.