JPS63257040A - Debugging system - Google Patents

Abstract

PURPOSE:To improve the efficiency of debugging work, by stopping the execution of a program only when an execution stop condition is satisfied. CONSTITUTION:When the trace of the program is performed by an operator, the program is executed after a CPU register which becomes a condition to stop the execution of the program at a break point other than an address where the break point is set, or a specific value for a memory address is inputted from a command input processing part 121. When the execution of the program is started and the address on which the break point is set is indicated, the program stops transiently, and control is delivered to the program execution stop processing part 123 of a debugging device. The processing part 123 decides coincidence between the value of the CPU register or the memory and the specific value. When the coincidence is obtained, the execution of the program is stopped, and when it is not, the return of the program is performed.

Description

[Detailed description of the invention]

[Field of Industrial Application] The present invention relates to a program debugging method, and particularly to a debugging method for controlling program execution stop, which is suitable for tracing work such as a subroutine that is called multiple times from other routines.

[Prior Art J] As described in Japanese Patent Application Laid-Open No. 59-206955, a conventional debugging device sets a breakpoint at a predetermined address of a program, stops execution of the program at this breakpoint, and saves memory and The program is traced while referring to the contents of the CPU's registers. [Problem to be Solved by the Invention 1] In the conventional debugging device as described above, once a breakpoint is set, execution of the program is unconditionally stopped at this breakpoint. Therefore, 1. For example, in a subroutine that is called multiple times from other routines, if you want to trace only when the input parameter of the subroutine set in the CPU register etc. becomes a specific value, you can trace the input parameter of the subroutine. The operator has to set breakpoints and execute the subroutine many times until a specific value is reached, which poses a problem in terms of debugging efficiency. An object of the present invention is to provide a debugging method that stops execution of a block diagram at a breakpoint only when the contents of a specified CPU register or memory reach a specific value. Means for Solving Problem E] The above object is achieved by the configuration of the present invention as shown in the flowchart of FIG. That is, the debugging method according to the present invention is a debugging method in which a breakpoint is set at an arbitrary address in a program, and debugging is performed by tracing the program while referring to the contents of a CPU register or memory. , set the above breakpoint and execution stop condition, start execution of the above program, and when the above program executes or reaches the above breakpoint, determine whether the above execution stop condition is satisfied, and It is characterized in that the execution of the block diagram is stopped at the breakpoint only when an execution stop condition is satisfied. The above-mentioned execution stop condition can be set to match a predetermined value, for example, a value in a specific CPU register or a value in a memory at a specific address. [Operations] In the present invention, when stopping program execution at a breakpoint, the program execution stop condition is such that the program execution is stopped only when the value of a specific CPU register or memory at a specific address reaches a specific value. a block diagram execution stop processing unit that causes the CPU to execute the program, the specified CPU register or the memory at the specified address, and the specified CPU
A command input processing unit is newly provided that allows an operator to input the specific value for the U register or the memory at the specific address to the debugging device as a condition for stopping execution of the block diagram. In the debugging method according to the present invention, when an operator traces a program, in addition to the address at which a breakpoint is set for the debugging device, the operator also selects a CPU register or memory address that is a condition for stopping program execution at a breakpoint. After inputting a specific value for the CPU register or memory address by the command input processing unit, the program is executed. When the program starts running and reaches the breakpoint setting address, the program is temporarily stopped and control is transferred to the program execution stop processing section of the debugging device. The program execution stop processing unit determines whether the value of the CPU register or the memory matches a specific value, and if they match, the execution of the program is stopped; if they do not match, the program is re-executed. Through the above processing, program execution will stop at the breakpoint only if the condition that the value of a specific CPU register or memory at a specific address, given by the operator as a program stop condition, matches a specific value is satisfied. becomes possible. Therefore, there is no need for wasteful program execution work when the above conditions are not satisfied, making it possible to improve debugging work efficiency. [Example] Hereinafter, an example of the present invention will be described using the drawings. FIG. 3 is a block diagram showing a standard system configuration to which the present invention is applied. CPU (central processing unit) 1
．． The ROM 2, RAM 3, display device 4, keyboard 5, and disk device 6 are connected to the system bus 7, respectively.
Connected by A debug device that executes the debug method of the present invention is RO
As a program on M2, RAM3, it is controlled by CPU 1, and while controlling the display device 4, keyboard 5, and disk device 6, the same < ROM2, RAM
This is for debugging the user program on A. FIG. 2 is a memory map showing the structure of programs on the ROM 2 and RAM 3 that constitute the main memory of the system to which this embodiment is applied. The main memory includes a system program 11, a debug device 12, and a user program 13.
assigned to. The system program 11 performs input/output of the display device 4 and keyboard 5, management of files on the disk device 6, and the like. The debug device 12 includes a command input processing section 121, a program execution processing section 122, a program execution stop processing section 123, and a debug device data area 1, which are features of the present invention.
There are 24. The debug device data area 124 also includes a breakpoint setting address area 1241. Instruction save area 124
2. Condition switch area 1243, register ID area 12
44, memory address area 1245 and specific value area 1
There are 246. The operation of the debugging device 12 will be explained with reference to flowcharts shown in FIGS. 4, 5, 6, and 7. FIG. 4 is a block diagram showing the flow of control between the debug device 12 and the user program 13. When the operator inputs a program execution command via the keyboard 5 and the system program 11, the command input processing unit 121 receives the break input from the operator together with the program execution command, as shown in the flowchart of FIG. A point setting address is set in the breakpoint setting address area 1241 (step Kl). Next, it is determined whether or not there is a stop condition based on an instruction input by the operator (Step 2). If there is a stop condition, the process goes to Step 3; if there is no stop condition, the process goes to Step 9. In step 3, the stop condition is a specific CPU.
Determine whether it is a register value or a memory value at a specific address, and
If it is a PU register value, go to step 4; if it is a memory value, go to step 7. In step 4, 2 is set as condition switch information in the condition switch area 1243, and 2 is set in the register ID area 124.
5, the CPU register ID input by the operator is set. On the other hand, in step 7, 3 is set as condition switch information in the condition switch area 1243, and the memory address input by the operator is set in the memory address area 1245. In step 6, the specific value input by the operator is set in the specific value area 1246, and the program execution processing unit 1
Control is transferred to 21. In step 2 above, if there is no stop condition, in step 9, l is set as condition switch information in the condition switch area 1243, and the program execution processing unit 121
transfer control to Next, as shown in FIG. 6, the program execution processing unit 122 saves the l instruction located at the breakpoint setting address of the user program 13 to the instruction save area 1242 (step L1), and further saves the l instruction at the breakpoint setting address IN is a software interrupt instruction for the CPU.
After setting the T instruction 20 and replacing it with the saved instruction (step L2), a jump is made to the start address of the user program 13, and execution of the user program is started. Here, the INT command 20 is set in advance so that when this command is issued, the program execution stop processing unit 123 is called as an interrupt process. When the user program 13 is executed and reaches the breakpoint setting address, a software interrupt is generated by the INT instruction 20, and the program execution stop processing unit 123 is called. As shown in the flowchart of FIG. 7, the program execution stop processing unit 123 determines whether the value of the condition switch information in the condition switch area 1243 is 1, 2, or 3 (step M1, step M2); If the result is 2, the process moves to step M3; if the result is 3, the process moves to step M6. In step M3, the value of the CPU register indicated by the register ID area 1244 is obtained. On the other hand, step M
6, the value of the memory at the address indicated by the memory address area 1245 is obtained. Furthermore, in step M4, this CPU register value or memory value is compared with the value in the specific value area 1246, and if they match, the process goes to step M7, and if they do not match, the process goes to step M5.
Move to. In step M7, the saved l instruction is restored from the instruction save area 1242 to the user program 13, control is transferred to the command input processing section 121, and the next command from the operator is awaited. On the other hand, if it does not match the specific value in step M4 and is 1, then in step M5, the command save area 1242
The user program 13 is executed again from the instruction next to the breakpoint. In other words, if the operator specifies a specific CPU register or memory at a specific address, as well as a specific value for these, as a stop condition at a breakpoint, it is determined that the value of the CPU register or memory matches the specific value. Only then will the execution of the user blockram be stopped at the address where the breakpoint was set. In this embodiment, a CPU register and a memory are used to provide a condition for stopping program execution, but it is of course possible to use other hardware registers and the like. [Effects of the Invention] As described above, according to the present invention, when tracing a user program by setting a breakpoint, a specific execution stop condition specified by the operator as a stop condition at the breakpoint is satisfied. Since it is possible to stop program execution only when the above conditions are not met, the operator can avoid unnecessary tracing work when the above conditions are not met, improving debugging efficiency and operability of the debugging device. .

[Brief explanation of drawings]

FIG. 1 is a flow chart showing the configuration of the present invention, and FIG. 2 is a memory map showing the system configuration of an embodiment of the present invention.
Fig. 3 is a standard system configuration diagram to which the present invention is applied, Fig. 4 is a block diagram showing the control flow between the debug device and the user program, Fig. 5 is a flow chart showing program execution command processing, and Fig. 6 7 is a flowchart showing program execution processing, and FIG. 7 is a flowchart showing program execution stop processing. 1-...CPU 2...ROM3...R
A M 4-...Display 5...Keyboard 6...Disk 11...System program 12...Debug device 121...Command input processing section 122...Program execution processing section 123...Program Execution Suspension Processing Department Applicant Hitachi, Ltd. Representative Patent Attorney Tomi 1) Kazuko Figure 1 Figure 2N Figure 3 Figure 4 Figure 5 Figure 6 Figure 7

Claims (1)

[Claims] 1. In a debugging method in which debugging is performed by setting a breakpoint at an arbitrary address in a program and tracing the program while referring to the contents of a CPU register or memory, before setting the breakpoint and execution stop condition, starting execution of the program, and determining whether or not the execution stop condition is satisfied when execution of the program reaches the breakpoint; A debugging method characterized in that execution of the program is stopped at the breakpoint only when the execution stop condition is satisfied. 2. The above execution stop condition is when the value of the specific CPU register is
The debugging method according to claim 1, wherein the debugging method matches a specific value specified in advance. 3. The debugging method according to claim 1, wherein the execution stop condition is that a value in the memory at a specific address matches a specific value specified in advance.