KR100291016B1 - How to add / remove debugging module - Google Patents

Abstract

end. The technical field to which the invention described in the claims belongs

How to add or remove a debugging module in a system that uses a debugging module.

I. The technical problem to be solved by the invention

The operator can easily add or delete debugging modules and provide a way to add / delete debugging modules to check the version change.

All. Summary of Solution of the Invention

The debugging process is assigned to each of the debugging modules and checks the on / off status of the module flags that are on / off corresponding to the addition / deletion of the corresponding debugging module, and performs the debugging module corresponding to the module flag of the on status. do. And the version display process is shown when checking the on / off state of the module flags to display the version.

la. Important uses of the invention

Used to add or remove debugging modules.

Description

How to add / remove debugging module

The present invention relates to a system using a debugging module (debugging module), and more particularly to a method for adding or deleting a debugging module in a mass communication processing system.

In a large communication processing system, a debugging module for debugging is used in software. For example, the ″ CHECKSUM ″ and ″ SEQUENCE ″ debugging modules are used to verify data loss during file transfer.

However, in the past, it was not possible to know about adding / deleting debugging modules to software. Therefore, it was inconvenient to use after compiling a program when adding module for debugging. Also, since it is impossible to check the addition / deletion of the software debugging module, it was difficult to check the version even if a problem occurred during system operation.

Accordingly, an object of the present invention is to provide a method for adding / deleting a debugging module that allows an operator to easily add or delete a debugging module.

Another object of the present invention is to provide a method for adding / deleting a debugging module that allows an operator to easily check a version change.

1 is a block diagram of a conventional monitoring device,

2 is a process flow diagram according to an embodiment of the present invention;

3 is a flow chart of the debugging process of FIG. 2 in accordance with an embodiment of the present invention;

4 is a flow chart of the version display process of FIG. 3 in accordance with an embodiment of the present invention.

The debugging process of the present invention for achieving the above object is given to each of the debugging modules and the on / off state of the module flags that are ON / OFF (ON / OFF) corresponding to the addition / deletion of the corresponding debugging module Check and execute the debugging module corresponding to the module flag in the on state. And the version display process is shown when checking the on / off state of the module flags to display the version.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the following description and the annexed drawings, detailed descriptions of well-known functions and configurations that may unnecessarily obscure the subject matter of the present invention will be omitted.

1 is a block diagram of a typical monitoring apparatus, and includes a keyboard 100, a controller 102, a memory 104, and a monitor 106. The control unit 102 performs the processing according to the input from the keyboard 100 operated by the system operator and displays it on the monitor 106. In the present invention, the monitoring apparatus of FIG. 1 is used to add / delete debugging modules and check the version change.

In the present invention, a flag variable is used for adding / deleting a debugging module. In addition, it can be used in addition to the version display function so that the contents of the flag variable can be seen so that the operator can easily check the version change. To do this, the operator writes debugging modules and assigns a module flag corresponding to each debugging module. Then add a command to change the flag variable. If the flag variable is on, the debugging module is added. If the flag variable is off, the debugging module is deleted. It also adds a version display command.

Figure 2 shows a processing flow diagram according to this embodiment of the present invention. The operator changes the module flag as needed to add debugging modules. Then, the controller 102 inputs the module flag on / off in step 200 of FIG. 2 and stores the module flag on / off in the memory 104. Thereafter, the debugging process of step 202 is performed.

For convenience, for example, if there are two debugging modules, A debugging module and B debugging module, the module flag corresponding to A debugging module is A_flag, the module flag corresponding to B debugging module is B_flag, and the debugging process is A The process of debugging is as follows.

A process () {

if A_flag

A Debugging Module

if B_flag

B Debugging Module

}

Referring to FIG. 3, which shows a flowchart of the debugging process, in step 300, the on / off state of the module flags is checked. In operation 302, the debugging module corresponding to the on-state module flag is performed.

After debugging, change the module flag to delete the debugging module again.

On the other hand, after the debugging process as described above, the version display process is performed in step (204). Here, when the version display process is referred to as the B process, the version display process is as follows.

B process () {

date: MM_DD_YY

company: SS

if A_flag

printf A MODULE INSERT

if B_flag

printf B MODULE INSERT

}

Referring to FIG. 4, which shows a flowchart of the version display process, in step 400, the on / off state of the module flags is checked. In operation 402, the version is displayed by displaying the debugging module corresponding to the module flag in the on state.

Therefore, the operator can check whether the status of module addition / deletion is correct by the version display command.

Meanwhile, in the above description of the present invention, specific embodiments have been described, but various modifications can be made without departing from the scope of the present invention. In particular, a dummy terminal or the like may be used instead of the monitoring apparatus of FIG. 1. Therefore, the scope of the invention should not be defined by the described embodiments, but should be defined by the equivalent of claims and claims.

As described above, the present invention has an advantage that the operator or the program developer can perform the desired debugging in a short time because the operator can easily add or delete the debugging module by giving a module flag to each of the debugging modules. . In addition, the version can be checked as a version display command so that errors can be eliminated by changing the version by adding / deleting debugging modules.

Claims (4)

In how to add / remove debugging module, Storing module flags which are assigned to each of the debugging modules and which are turned on / off corresponding to the addition / deletion of the corresponding debugging module; The debugging process checking the on / off status of the module flags; And a debugging module performing a debugging module corresponding to an on-module flag. The method of claim 1, further comprising: displaying a version when the version display process checks the on / off status of the module flags and displays the version. The method of claim 2, wherein the module flags are turned on / off by an operator corresponding to the addition / deletion of each of the debugging modules. 4. The method of claim 3, wherein only one of the module flags is on.