JPH06290072A - Program debugging system - Google Patents

Abstract

PURPOSE:To eliminate the necessity of preparing complicated processing for debugger by a program operating system (OS), to attain easy development and to prevent the operation efficiency of a debugger program from being reduced even when the load of a processor is increased by mounting the program OS and a debugger OS different from the program OS on the same processor. CONSTITUTION:User programs 160, 161 to be driven under the control of the program OS 153 are debugged by a debugger program 111 driven under the control of the debugger OS 105 independent of the program OS 153. Namely command information or various program information is priviously distributed to either one of the OSs 153, 105 by a hardware means, and when command information is generated, debugging processing is executed under the control of the OS 105. When various program information is generated, user program processing concerned is executed under the control of the OS 153.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a debugging method for a program executed by a microprocessor.

[0002]

2. Description of the Related Art Conventionally, as a method of debugging a program in a microprocessor, a method of using an in-circuit emulator device and a method of incorporating a program dedicated for debugging, and outputting to a medium such as a memory or a CRT device that can be referenced from the outside have been mainly used. It has been known.
Among these, as the latter implementation method, a method of incorporating a debugger program as a part of the function of an operating system (hereinafter referred to as OS) as shown in FIG.
There is a method of incorporating a debugger program as one of user programs controlled by the OS as shown in FIG.

First, in FIG. 2, reference numeral 1 is an information display / command operating unit which is provided independently of the main body of the microprocessor for inputting commands and displaying information, and 2 is the OS 3 of the microprocessor and information display / command. It is a line used to notify information to and from the operation unit 1.

Further, 4 is an interrupt determination unit provided in the OS 3 for determining the contents of the interrupt, 5 is a command notification, 6 is a factor for notifying the user program stop, and 7 and 8 are user program information. Reference numerals 9 and 9 denote a debugger interrupt factor determination unit and a user interrupt factor determination unit, respectively.

Further, 11 to 15 are interrupt acceptance processing corresponding to each interrupt, 16 is a program starting processing, 17 is a start judging section for judging whether the program is in a debugger starting state, 18 is a debugger program. , 19 is the start-up of this debugger program 18, 20 is a user program start-up determination section, and 21 and 22 are user programs.

Further, 23 and 24 are activations for the user programs 21 and 22, 25 and 26 are execution control and information reference / change for the user programs 21 and 22,
Reference numeral 27 is an information display request from the debugger program 18 to the OS 3, and 28 is a notification to the information display / command operating unit 1.

Next, the operation will be described. Now, when a command is input from the information display / command operating unit 1, the interrupt determination unit 4 in the OS 3 of the microprocessor is activated via the line 2 due to the command notification 5.

In the interrupt determination unit 4, other users
It is activated by the factor 6 for notifying the status such as program stop and the user program information 7, 8.

When the interrupt determination unit 4 receives the activation, it first determines whether it is a debugger interrupt or a user interrupt, and the debugger interrupt factor determination unit 9 or the user interrupt factor determination unit. Go to 10.

Further, the interrupt factor determination unit 9 for the debugger or the interrupt factor determination unit 10 for the user determines the detailed factors, and the interrupt acceptance processing 11 to 11 corresponding to each interrupt.
After executing 15, the program activation process 16 is performed.

In the program starting process 16, first, the starting judgment unit 17 judges whether the program is in the debugger starting state. If the debugger is in the activated state, the debugger program 18 in OS 3 is activated 19.

On the other hand, if the debugger is not activated, the user program activation determination unit 20 further determines the activation program type, and activates 23 and 24 the user programs 21 and 22.

In the debugger program 18, after being activated, the user program 21,
Execution control and information reference / change 25, 26 are performed on the data 22.

Then, as for the result,
The program 18 has an OS due to the information display request 27.
When booting to OS3, OS3 again determines the cause and
The information display / command operation unit 1 is notified 28 via the line 2 to complete the debug operation.

Further, FIG. 3 shows the debugger program incorporated as one of the user programs controlled by the OS as described above. In FIG.
Reference numeral 1 is a display / command operation unit, and 52 is a line used for notification of information.

Further, 53 is an OS, 54 is an interrupt determination unit,
Reference numeral 55 is a command notification, 56 is a factor for notifying the user program stop, 57 and 58 are user program information, and 59 to 63 are interrupt acceptance processing.

Further, 65 is a start-up determination unit, 66 is a debugger program, 67 and 68 are user programs, 6
Reference numerals 9, 70 and 74 are activations for the debugger program 66 and user programs 67 and 68, 72 and 73 are execution control and information reference / change for the respective user programs 67 and 68, 74 is an information display request, and 75 is display / This is a notification to the command operation unit 51.

Next, the operation will be described. First, when a command is input from the information display / command operation unit 51,
First, via the line 52, the OS of the microprocessor
The interruption determination unit 54 in 53 is activated due to the command notification 55.

In the interrupt judging section 54, the command notification 5
5 and the factor 56 for notifying the state such as the user program stop, the user program information 57,
Interruption and detailed factor determination processing is performed in the same manner as for 58, and interrupt acceptance processing 59 to 6 corresponding to each interruption.
After executing 3, the program activation process 64 is performed.

Then, the start determination unit 65 in the program start processing 64 determines the start program type and starts the debugger program 66 or the user programs 67, 68 69 or 70.
71 is done in exactly the same way.

In the debugger program 66, after receiving the activation, the user program 67,
For 68, execution control and information reference / change 72, 73 are performed. For the result, see the debugger program 66.
Issues an information display request 74 to the OS 53.

Therefore, the OS 53 sends the notification 75 to the information display / command operating section 51 via the line 52 by the same processing as the normal user programs 67 and 68, and the debugging operation is completed. There is a technique disclosed in Japanese Patent Laid-Open No. 105532/1998 as a technique for including processing for debugging in the OS3 or a program managed by the OS3.

[0023]

Since the conventional program debugging method is carried out as described above, if the debugger program 18 is incorporated in the OS3 in the debugging method of FIG. 2, only the cause for the debugger is judged in the OS3. , Start specially only for debugger program 18 1
However, there is a problem in that the processing of the OS3 becomes complicated and the size increases, and the efficiency of failure analysis during the development of the OS3 and the test of the OS3 decreases.

In the debugging method of FIG. 3, the debugger program 66 has little effect on the OS 53,
The premise is that the OS 53 operates normally. Therefore, before the development of the OS 53 is completed, the debugger cannot be developed, and when the load of the entire microprocessor including the OS 53 increases, the operation efficiency of the debugger program 66 decreases. There was a problem such as doing.

The present invention has been made in order to solve the above-mentioned problems, and by installing a debugger OS different from the OS for controlling the user program on the same processor, the program The operating system OS eliminates the need to prepare complicated processing in consideration of the start-up of the debugger program, thereby improving the development and productivity of the program OS, and even when the load on the entire microprocessor increases, the debugger program It is an object of the present invention to obtain a program debugging method that can prevent the deterioration of operation efficiency.

[0026]

A program debugging method according to the present invention is mounted on a microprocessor,
A user program operating under the control of a program operating system is debugged by a debugger program operating under the control of a debugger operating system independent of the program operating system in the microprocessor. Is.

[0027]

In the debugging method according to the present invention, first, command notification and various program information are distributed to one of two types of OSs by hardware (interrupt processing registration table), and when a command notification occurs. Move to the control of the OS for the debugger, execute the corresponding debug processing,
On the other hand, when various program information is generated, the process moves to the control of the program OS and the corresponding user program process is executed.

[0028]

【Example】

Example 1. An embodiment of the present invention will be described below with reference to the drawings. In FIG. 1, 101 is a display / command operating unit for operating commands necessary for debugging, and displaying the response and information of user programs.
A line 2 is provided between the display / command operation unit 101 and the microprocessor side for transmitting the above-mentioned commands and information.

Further, 103 is a command notification passed to the microprocessor side, 104 is a factor for notifying a state such as a user program stop, 105 is a debugger OS for controlling requests to the debugger by summarizing requests to the debugger.
Is.

Further, 106 is a debugger interrupt determination unit in the debugger OS 105, 107 and 108 are debugger interrupt acceptance processing, 109 is a debugger start processing, and 110 is
Is a debugger start-up determination unit therein, 111 is a debugger program, 112 is a data transmission request generated by debugger processing, and 113 is a debugger processing notification.

Further, 151 and 152 are user program information, 153 has a function equivalent to the conventional OS,
OS for user program for controlling execution of user program, 154 is OS for user program 1
53 is a user interrupt determination unit.

Further, 155 to 157 are user program interrupt acceptance processings, 158 is a user program activation processing in the OS 153 for user programs,
Reference numeral 159 is a user program start-up determination unit therein.

Reference numerals 160 and 161 are user programs, 115 and 116 are execution control and information reference / change for the user program, and 117 is execution control and information reference / change for the user program OS 153.

Next, the operation will be described. First, an operator who performs debugging inputs a command necessary for debugging from the display / operation unit 101. This command is line 1
02 to the microprocessor side via 02, and the debugger interrupt determination unit 106 in the debugger OS 105 is activated due to the command notification 103.

In response to the command notification 103, the debugger interrupt determination unit 106 first verifies the contents, performs the debugger interrupt acceptance processing 107 or 108 according to each interrupt, and then the debugger start processing 109. Move to.

In this debugger activation process, the debugger activation determination unit 110 verifies the activation contents and activates 114 the debugger program 111. In the debugger program 111, execution control and information reference / change 115, 1 which are processes corresponding to the command contents for the target user programs 160 and 161 are performed as in the conventional case.
Execute 16.

When the user program is stopped due to the processing, the status notification 104 is sent to the debugger O
In step S105, the debugger program 111 is activated 114 as in the command notification, and the debugger process is executed.

In the debugger program 111,
In order to send the execution result of the command generated as a result of the above-described processing and the user / program status notification to the display / command operation unit 101, a transmission request 112 is issued to the debugger OS 105.

As a result, the debugger OS 105 notifies the display / command operating unit 101 of the command execution result and the user / program status notification 104 via the line 102.
Is sent. During this period, the program OS 153 is used.
Is not involved at all.

On the other hand, regarding the user program information 151 and 152 generated separately from this, the conventional OS is used.
After passing through the program OS 153, which is equivalent to 53, to the user program interrupt determination unit 154, the corresponding user program interrupt acceptance processing 15
5 to 157 are executed.

Then, the user program starting process 1
The user program activation determination unit 159 in 58 activates the user program 160 or 161.
2,163. During this operation, the OS for the debugger is
105 is not involved at all.

[0042]

As described above, according to the present invention, a user program installed on a microprocessor and operating under the control of a program operating system is stored in the microprocessor as the program operating system. Is configured to perform debugging with a debugger program that operates under the control of an independent debugger operating system, the program OS does not need to prepare complicated processing in consideration of the activation of the debugger program.
The productivity of the program OS is improved, and the program OS is
Even if the above is not completed, there is an effect that a debugger OS and a debugger program can be created.

Further, the deterioration of the command responsiveness, which is a problem when the debugger program is activated similarly to the user program, can be solved by setting the priority of the debugger OS higher than that of the program OS. .

Further, from the viewpoint of the program OS debugger program and the debugger OS, since it is positioned as one of the user programs, the debugging of the program OS, which was conventionally only possible with the in-circuit emulator, can also be performed from the debugger program. It is possible to perform the program OS in the existing system.
There is an effect that what can be easily added / ported to those operating under the control of is obtained.

[Brief description of drawings]

FIG. 1 is a block diagram showing a program debugging method according to an embodiment of the present invention.

FIG. 2 is a block diagram showing a conventional program debugging method.

FIG. 3 is a block diagram showing another conventional example of a program debugging method.

[Explanation of symbols]

105 OS for Debugger (Operating System for Debugger) 111 Debugger Program 153 OS for Program (Operating System for Program) 160, 161 User Program

Claims (1)

[Claims] 1. A user program, which is mounted on a microprocessor and operates under the control of a program operating system, is controlled by a debugger operating system independent of the program operating system in the microprocessor. A program debugging method for debugging with a running debugger program.