KR19990004963A - How to print debug messages at electronic exchange - Google Patents

Abstract

The present invention relates to a method for outputting a debugging message in an electronic switchboard.

Such a method of the present invention comprises the steps of calling a shared library when an error occurs in an application running in the electronic switching system; The called library receives parameters from the application program and reconfigures the message to send a signal to the output control block; When the output control block receives a signal, it outputs the corresponding debugging message to the console. When an error occurs in the program applied to the electronic switchboard, the error location and cause of the corresponding program are displayed to facilitate debugging.

Description

Method of printing debug messages in ATM exchange (Methodofprintingdebugmessages in ATM exchange)

The present invention relates to a method for outputting a debugging message in an electronic switchboard.

In general, real-time embedded systems, such as switching systems, are edited on a host computer using a general-purpose operating system, compiled using a cross-compiler that produces the target system's executable code, and then downloaded to the target system. Run it. The reason for using this cross-development method is that the target system has limited system resources such as memory or disk, so that necessary applications cannot be built-in enough, but the host computer can fully utilize such resources and applications. Therefore, it can be more convenient and more productive for programmers to debug the high-level language of the program to download to the target system from the host computer editing and compiling.

However, large-scale, complex, distributed real-time systems, such as electronic exchange systems, consist of parallel programs consisting of numerous processes.In addition, the operating environment is not a general-purpose operating system, but a special operating system that implements core distributed real-time functions. In many cases, it is not suitable to use commercial debugging tools developed based on general-purpose operating system environment, and it also lacks the function of the operating system that enables effective debugging of parallel programs.

In other words, many types of software programs and large amounts of software exist in an electronic switching system, especially in a large system such as an ATM switching system. This software is verified through a number of test steps from the design stage to the final validation test stage, where the errors in the program are corrected. Error correction of such a program can be easily corrected as the problem type is clear, but as the verification process is repeated, the problem type becomes ambiguous, and only problems that are difficult to correct in an unspecified period remain.

In the prior art, when such a problem occurs, the print port outputted during program execution can only be determined by using the debug port of the processor. However, this method has a problem due to the danger that the debug port has. That is, FIG. 1 is a flowchart illustrating a conventional printing of a debug message in an electronic switchboard. When an error is detected during a normal program, a message is output to a debug port through a print statement.

Accordingly, an object of the present invention is to output a debugging point specified by the software designer using a system message to output the debug message in the electronic switchboard which can identify the cause by tracking the software problem in the system operating state without using the debug port. To provide.

In order to achieve the above object, the present invention comprises the steps of: calling a shared library when an error occurs in the application running in the electronic switching system; The called library receives parameters from the application program and reconfigures the message to send a signal to the output control block; When the output control block receives a signal, it outputs the corresponding debugging message to the console. When an error occurs in the program applied to the electronic switchboard, the error location and cause of the corresponding program are displayed to facilitate debugging. do.

1 is a flowchart illustrating a flow of conventionally printing debug messages in an electronic switchgear;

2 is a flowchart illustrating a method of outputting a debug message in an electronic switch according to the present invention;

3 is a schematic diagram illustrating a signaling flow in accordance with the present invention;

4 is an example of a debug message in accordance with the present invention;

5 is a printing example of a debug message according to the present invention.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

2 is a flowchart illustrating a method of outputting a debug message in an electronic switch according to the present invention, and FIG. 3 is a schematic diagram illustrating a signal transmission flow according to the present invention.

Referring to Figure 2, the debugging message output method according to the present invention consists of steps 201 to 205. The program for operating in the electronic switching system is normally executed (201), if an error occurs in step 202, the shared library is called in step 203, and in step 204, the corresponding routine of the shared library sends a signal to the output control block. do. In step 205, the output control block receiving the signal outputs a debug message to the console.

Referring to FIG. 3 to more easily understand the concept of the present invention, an application program calls a parameter to a corresponding routine of a shared library to transfer the parameter, and the shared memory transfers a signal to the output control block accordingly. At this time, the corresponding routine of the shared library notifies the application program of the processing result, and the output control block prints a message to the console according to the signal. That is, when each application receives a debugging message handling routine while it is running, it calls the shared library where the actual program resides. The shared library takes parameter inputs, reconstructs the message, and requests the message output to the output control block via the signal. The output control block receives this and outputs a message to the operator console.

4 is a code example of a debug message according to the present invention, and FIG. 5 is a print example of a debug message according to the present invention.

Referring to FIG. 4, when looking at the code structure for classifying a debug message, the first D is an identifier indicating that the debug message is used to distinguish it from other messages, and 12 is a block name. Identifier that indicates whether an error occurred. Block names can be registered from 00 to 99. One block is designated by the software manager.

In FIG. 4, 34 is a module name of a program source, and 100 values from 00 to 99 can be registered and can be arbitrarily designated by a software designer. This number allows the software designer to estimate where in the program the error occurred.

5 is an example of output of a debug message output by the present invention.

Referring to FIG. 5, when a code D7230 is generated, a block name (BLOCK NAME), a module name (MODULE NAME), a source number (SOURCE_NO), an error cause (REASON), and the like of a program source are displayed. A program source block designated by code number 72 is a module name, and a module name is a name of a program source module stored at code number 30. FIG.

As described above, according to the present invention, the error of the designer during the development or operation of the switch software can be easily output through the operator output terminal, and a separate print statement is not inserted into the source for debugging. And when a software problem occurs, it accurately determines the cause of the problem and the problem site, and provides detailed information on the problem so that the designer can easily trace the problem and facilitate the correction.

Claims (3)

Invoking the shared library when an error occurs in an application running in the electronic switching system; The called library receives parameters from the application program and reconfigures the message to send a signal to the output control block; If the output control block receives a signal, including the step of outputting the corresponding debugging message to the console If an error occurs in a program that is applied to the electronic exchange, the debug message output method of the electronic exchange will display the error location and cause of the corresponding program to facilitate debugging. The method of claim 1, wherein the debugging message includes a module name of a program source, a block name, an error cause, and the like. The method of claim 1, wherein the code for classifying the debugging message comprises an identifier D, a two-digit block name, and a two-digit module name.