JP2000029738A - Device and method for monitoring debugging - Google Patents

Abstract

PROBLEM TO BE SOLVED: To save time and cost needed for software development through providing debugging information obtained by monitoring debugging dynamically for a user in a run time, while monitoring the debugging through a debugging manager. SOLUTION: On a debugging monitor device 10, a task called the debugging manager 13 is installed. The debugging manager 13 has an interface capable of interchanging information with all tasks 14 being run on the debugging monitor device 10. The tasks 14 are task programs and present on the debugging monitor device 10 and have unique process IDs. A debugging task which has a debugging program for debugging is included among the tasks 14. The tasks 14 have interfaces for passing debugging information to the debugging manager 13 at an information request to provide the debugging information which is made by the debugging manager 13. Namely, pieces of information from the tasks 14 are all provided to the user through the debugging manager 13.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a debug monitoring device and a debug monitoring method that operate on an operating system (OS) on a computer terminal. More specifically, the present invention relates to a debug monitoring device and a debug monitoring method incorporating a debug program.

[0002]

2. Description of the Related Art In recent years, with the rapid spread of the Internet and personal computers, the demand for software operating on computers has been rapidly increasing, and many software programs have been developed. With the rapid spread of graphical user interfaces, higher capacity and more complex application software is being used, and the development of such application software is required. On the other hand, competition in the software market is intensifying, and software development at lower cost is required to provide cheaper and higher quality software. One of the ways to reduce software development costs is to shorten the development cycle.

Generally, a software development cycle is roughly divided into 1) creation of a program specification, 2) creation of a program, 3) testing, and the like. By repeating these steps as one cycle to improve the quality step by step, a product of sufficient quality for sale is finally completed. In the above-described development cycle, generally, engineers having their respective specialized knowledge participate in the development, and the development is performed for each stage. For example, when the development is completed in step 1), the development in step 2) is started.

In general, the creation of the program in step 2) is performed by
It is performed by a developer called a programmer. The programmer has linguistic knowledge of program creation and creates a program based on the specifications of the program created in step 1). In the development stage of commercializing software, creating a program is an important development stage that determines the availability of software. At the same time, the test in step 3) is also an important development stage that determines the reliability of software. It is in the development stage. Generally, the test in step 3) is performed by a developer called a tester. In step 3),
The tester conducts tests to check whether the program has been created based on the specifications determined in step 1),
Give test results to programmer. When a test result indicating that the program has a failure is obtained, the programmer reproduces the test of the program by himself / herself based on the test result received from the tester, pursues the cause using tools such as a debugger, Make corrections. The tester tests the modified program and returns test results to the programmer. Then, the program correction and the test are repeated until the result of the program test becomes OK. Ultimately, the tester performs an operation test of the software in an environment in which the user actually uses it, and after confirming that the software operates normally in such an environment, the software is used as a product. Sold.

[0005]

However, in software development, a tester generally only reports test results to a programmer, and only a programmer can pursue a detailed cause of a failure. This person, a tester, had difficulty obtaining the cause of the failure from the operation of the software. In general, a programmer uses a dedicated software called a debugger to detect a failure in a program, and investigates an operation when the program is executed based on the execution result of the program in detail. However, when a programmer performs a debug operation to detect a cause of a program failure using a debugger, such a debug operation is performed in an environment in which the programmer develops software, so that the user actually uses the software. Debugging work could not be performed in such an environment. Therefore, it takes an enormous amount of time to detect the cause of the failure, and it has not been easy to accurately identify the location where the failure has occurred. That is, the programmer has to re-execute the reproduction test by himself / herself based on the information on the test result received from the tester to pursue the cause of the failure, and it has not been easy to accurately identify the location where the failure has occurred. Conventionally, developing software has required enormous labor, cost, and time.

Conventionally, when a programmer performs a debugging operation using a debugger, information obtained by the debugging operation is temporarily stored in a memory or a hard disk and then simply output to a printer or a display. Thus, only necessary information cannot be extracted from the information obtained by the debugging work.

Further, in the communication software, when the user actually uses the communication software, the user often uses a communication device such as a modem, a TA, or a DSU. Therefore, when the software to be developed is communication software, the user may use the communication software, for example, a modem, TA, DSU, or the like.
It is necessary to perform software testing in an environment where communication devices such as the above are used. Conventionally, during such tests,
Using only dedicated software such as a debugger could not obtain all the information on the debugging result, and a dedicated measuring instrument had to be used to obtain all the information on the debugging result.

[0008] The present invention has been made in view of the above problems in the prior art. An object of the present invention is to provide a debug monitoring device and a debug monitoring method that can reduce the time and cost required for software development. Further, an object of the present invention is to detect a failure immediately and easily in an environment where the user actually uses or uses the software, and to grasp the cause of the failure in detail. A debug monitoring device and a debug monitoring method are provided.

[0009]

Means for Solving the Problems A first invention of the present application for solving the above problems is a debug monitoring device which operates on an operating system having a multitasking function and has a plurality of task programs on a debug manager. A debug monitoring device characterized in that debug information obtained by the monitoring is dynamically provided to a user during runtime while monitoring the debug via a debug manager.

[0010] The term "dynamically during runtime" referred to in the first invention of the present application means, primarily, that the debug monitor immediately provides the user with such information during debugging. . Thus, according to the debug monitoring device of the first invention of the present application, while monitoring the debug via the debug manager, the debug information obtained by the monitoring is dynamically provided to the user during runtime. If a failure occurs during debugging, the failure can be found immediately, the location of the failure can be accurately identified, and the cause can be grasped in detail. As a result, the failure can be corrected immediately, so that the time and cost required for software development can be reduced.

Further, the second invention of the present application is a debug monitoring device which operates on an operating system having a multitasking function and has a plurality of task programs on a debug manager, and monitors the debug via the debug manager. The debug monitoring device is characterized in that the debug information obtained by the monitoring is provided to the user simultaneously during runtime.

The simultaneous progress during runtime referred to in the second invention of the present application is primarily defined as simultaneous progress with debugging.
This means that the debug monitoring device immediately provides such information to the user. Thus, according to the debug monitoring device of the second invention of the present application, by providing debug information obtained by the monitoring to the user simultaneously during runtime while monitoring the debug via the debug manager, If a failure occurs during debugging, the failure can be found immediately, the location of the failure can be accurately identified, and the cause can be grasped in detail. As a result, the failure can be corrected immediately, so that the time and cost required for software development can be reduced.

[0013] The third invention of the present application is a debug monitoring device that operates on an operating system having a multitasking function and has a plurality of task programs on a debug manager, and monitors debugging via the debug manager. And a debug monitoring device for providing the debug information obtained by the monitoring to the user in parallel with the progress of the task.

The term "parallel to the progress of a task during runtime" referred to in the third invention of the present application means that a debug monitoring device is primarily used while a task for executing debugging is operating. Immediately provide such information to the user. Thus, according to the debug monitoring device of the third invention of the present application, the debug information obtained by the monitoring is provided to the user during runtime at the same time as the progress of the task, while monitoring the debug via the debug manager. By doing so, if a failure occurs during debugging, the failure can be immediately found, the location of the failure can be accurately specified, and the cause can be grasped in detail. As a result, the failure can be corrected immediately, so that the time and cost required for software development can be reduced.

[0015] Further, the fourth invention of the present application is a first invention of the present invention.
3. The debug monitoring device according to any one of the claims 3, wherein the plurality of task programs have a process ID and one or more debug levels that can be switched and / or changed. Thus, according to the debug monitoring device of the fourth invention of the present application, debug information is required because a plurality of task programs have a process ID and one or more debug levels that can be switched and / or changed. In this case, only the necessary and sufficient debug information can be immediately provided to the user by designating the process ID and selecting and / or changing the debug level. Time and cost can be reduced.

Further, the fifth invention of the present application is the first invention of the present application.
4. The debug monitoring device according to any one of the aspects 4, wherein the plurality of task programs have a debug mode in which switching and / or change is possible. Thus, according to the debug monitoring device of the fourth invention of the present application, when a plurality of task programs have a debug mode that can be switched and / or changed, if the debug information becomes necessary, it is necessary and sufficient. Since only debug information can be immediately provided to the user,
The time and cost required for software development can be reduced.

Further, the sixth invention of the present application is the fifth invention of the present application, wherein the switching and / or the change of the debug mode can be executed by selecting from the display on the window of the display. This is a debug monitoring device. Thus, according to the debug monitoring apparatus of the fifth invention of the present application, the switching and / or the change of the debug mode can be executed by selecting from the display on the display window, so that the debug information is required. In this case, the user can easily select a necessary debug mode. As a result, the debug information is immediately provided to the user, so that the time and cost required for software development can be reduced.

Further, the seventh invention of the present application is a first invention of the first application.
6. A debug monitoring device according to any one of the sixth to sixth aspects, having a function of displaying debug information on a window of a display. As a result, the present application No. 7
According to the debug monitoring device of the invention of the present invention, it is possible to monitor debug information indicating the result of debugging at the same time as debugging, so that even if a failure occurs during debugging, the The location where the error occurred can be accurately specified, and the cause can be grasped in detail. As a result, a fault can be corrected immediately, and a response can be taken, so that the time and cost required for software development can be reduced.

The eighth invention of the present application operates on an operating system having a multitasking function, includes a plurality of task programs on a debug manager,
While monitoring the debug via the debug manager,
A debug monitoring method characterized in that debug information obtained by the monitoring is dynamically provided to a user during runtime.

The term "dynamically during runtime" referred to in the eighth invention of the present application means, primarily, that such information is immediately provided to the user during debugging. Thus, according to the debug monitoring method of the eighth invention of the present application, while monitoring the debug via the debug manager, the debug information obtained by the monitoring is dynamically provided to the user during runtime, If a failure occurs during debugging, the failure can be found immediately, the location of the failure can be accurately identified, and the cause can be grasped in detail.
This allows you to fix the failure immediately,
The time and cost required for software development can be reduced.

The ninth invention of the present application operates on an operating system having a multitasking function, includes a plurality of task programs on a debug manager,
While monitoring the debug via the debug manager,
A debug monitoring method characterized in that debug information obtained by the monitoring is provided to a user at the same time during runtime.

Simultaneously during runtime referred to in the ninth invention of the present application means, primarily, simultaneous with debugging and
This means providing such information to the user immediately. Thus, according to the debug monitoring method of the ninth invention of the present application, while monitoring the debug via the debug manager, the debug information obtained by the monitoring is provided to the user at the same time during the runtime. If a failure occurs during debugging, the failure can be found immediately, the location of the failure can be accurately identified, and the cause can be grasped in detail. As a result, the failure can be corrected immediately, so that the time and cost required for software development can be reduced.

The tenth invention of the present application operates on an operating system having a multitasking function,
A debug monitor comprising a plurality of task programs on a debug manager, and providing debug information obtained by the monitoring to a user in parallel with the progress of the task while monitoring the debug via the debug manager. Is the way.

The parallelism with the progress of a task during runtime referred to in the tenth invention of the present application means, primarily, that such information is immediately obtained while a task for executing debugging is operating. Is provided to the user. Thus, according to the debug monitoring method of the tenth aspect of the present invention, while monitoring the debug via the debug manager, the debug information obtained by the monitoring is provided to the user at runtime in parallel with the progress of the task. By doing so, if a failure occurs during debugging, the failure can be immediately found, the location of the failure can be accurately specified, and the cause can be grasped in detail. As a result, the failure can be corrected immediately, so that the time and cost required for software development can be reduced.

Further, the eleventh invention of the present application is the eighth invention of the present application.
A debug monitoring method according to any one of the first to tenth aspects, wherein the plurality of task programs have a process ID and one or more debug levels that can be switched and / or changed. As a result, the present application
According to the debug monitoring method of the present invention, when a plurality of task programs have a process ID and one or more debug levels that can be switched and / or changed, if the debug information becomes necessary, By specifying the process ID and selecting and / or changing the debug level, the user can immediately provide only necessary and sufficient debug information to the user, thereby reducing the time and cost required for software development. be able to.

Also, the twelfth invention of the present application is the eighth invention of the present application.
A debug monitoring method according to any one of the first to eleventh aspects, wherein the plurality of task programs have a debug mode in which switching and / or change is possible. Thus, according to the debug monitoring method of the twelfth aspect of the present invention, when a plurality of task programs have a debug mode that can be switched and / or changed, if the debug information becomes necessary, it is necessary and sufficient. Since only simple debug information can be immediately provided to the user, the time and cost required for software development can be reduced.

Further, the thirteenth invention of the present application is the first invention of the present application.
2. The debug monitoring method according to the second aspect, wherein the switching and / or the change of the debug mode can be executed by selecting from the display on the window of the display. Thus, according to the debug monitoring method of the twelfth aspect of the present invention, switching and / or change of the debug mode can be executed by selecting from the display on the display window, so that debug information is required. In this case, the user can easily select a necessary debug mode. As a result, the debug information is immediately provided to the user, so that the time and cost required for software development can be reduced.

Further, the fourteenth invention of the present application is the invention of the eighth application.
A debug monitoring method according to any one of the first to thirteenth aspects, having a function of displaying debug information on a window of a display. Thus, according to the debug monitoring method of the fourteenth invention of the present application, it is possible to monitor debug information indicating the result of debugging at the same time as debugging, so that even if a failure occurs during debugging, Failures can be found, the location where the failure has occurred can be accurately specified, and the cause can be grasped in detail. As a result, a fault can be corrected immediately, and a response can be taken, so that the time and cost required for software development can be reduced.

The fifteenth invention of the present application operates on an operating system having a multitasking function,
A debug monitoring program comprising a plurality of task programs on a debug manager, and dynamically providing a debug information obtained by the monitoring to a user at runtime while monitoring the debug via the debug manager. Is a computer-readable recording medium having recorded thereon. Thus, according to the fifteenth aspect of the present application, while debugging is monitored via the debug manager, the debug information obtained by the monitoring is dynamically provided to the user during runtime, so that debugging is performed during debugging. In the event that a failure has occurred, the failure can be found immediately, the location of the failure can be accurately identified, and the cause can be grasped in detail. As a result, the failure can be corrected immediately, so that the time and cost required for software development can be reduced.

The sixteenth invention of the present application operates on an operating system having a multitasking function,
A debug monitoring program comprising a plurality of task programs on a debug manager, and, while monitoring the debug via the debug manager, simultaneously providing debug information obtained by the monitoring to a user during runtime. Is a computer-readable recording medium having recorded thereon. Thus, according to the sixteenth aspect of the present invention, while debugging is monitored via the debug manager, the debug information obtained by the monitoring is provided to the user simultaneously during runtime, so that debugging can be performed during debugging. In the event that a failure has occurred, the failure can be found immediately, the location of the failure can be accurately identified, and the cause can be grasped in detail. As a result, the failure can be corrected immediately, so that the time and cost required for software development can be reduced.

The seventeenth invention of the present application operates on an operating system having a multitasking function,
A plurality of task programs are provided on the debug manager, and while monitoring the debug via the debug manager, the debug information obtained by the monitoring is provided to the user at runtime in parallel with the progress of the task. A computer-readable recording medium on which a debug monitoring program to be recorded is recorded. Thus, according to the seventeenth aspect of the present application, by monitoring the debug via the debug manager, and providing the debug information obtained by the monitoring to the user at runtime in parallel with the progress of the task, If a failure occurs during debugging, the failure can be found immediately, the location of the failure can be accurately identified, and the cause can be grasped in detail. As a result, the failure can be corrected immediately, so that the time and cost required for software development can be reduced.

[0032]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of the present invention will be described with reference to the drawings, but the following embodiments are merely examples showing a debug monitoring device and a debug monitoring method according to the present invention. (Embodiment) FIG. 1 is a diagram schematically illustrating a debug monitoring device and a debug monitoring method according to an embodiment of the present invention. FIG. 2 is a diagram schematically illustrating a debug manager in a debug monitoring device and a debug monitoring method according to an embodiment of the present invention. FIG. 3 is a diagram illustrating functions of a debug manager and a task in a debug monitoring device and a debug monitoring method according to an embodiment of the present invention. FIG. 4 illustrates functions of a debug manager and a task when a user sets a process ID and a debug level in a debug manager in order to obtain debug information in a debug monitoring device and a debug monitoring method according to an embodiment of the present invention. FIG.

As shown in FIG. 1, a debug monitor 10 according to an embodiment of the present invention is application software that operates on an operating system (OS) 11, and is provided by the OS 11 via an OSAPI 12. It works by using various functions. OS
The API (OS application programming interface) 12 is a function prepared in advance on the OS 11, and the debug monitoring device 10
It operates with the aid of the 12.

The debug monitoring device 10 according to one embodiment of the present invention is characterized in that a task called a debug manager 13 is installed on the debug monitoring device 10. The debug manager 13 has an interface capable of exchanging information with all the tasks 14 operating on the debug monitor 10 as shown in FIGS. The task 14 is a task program, and as shown in FIG. 2, there are a plurality of tasks 14 in the debug monitor 10, each of which has a unique process ID. The tasks 14 include a debug task having a debug program for performing debugging.
As shown in FIG. 3, the task 14 requests the information providing request 3 from the debug manager 13 to provide the debugging information 33.
The debugger 13 has the interface 31 for passing the debug information 33 to the debug manager 13 when there is a 2 and provides the debug information 33 to the debug manager 13. That is,
All information from task 14 is provided to the user through debug manager 13.

Further, the plurality of tasks 14 have their own debug modes, each of which can be switched and / or changed. The debug mode is a setting as to whether or not debug information can be provided. That is, turning on the debug mode means that the debug information can be provided to the user, and conversely, turning off the debug mode means providing the debug information to the user. Is to cancel. In the debug monitoring device 10 according to an embodiment of the present invention, the plurality of tasks 14 each have a unique debug mode that can be switched and / or changed. If you want to know the debug information of only one task, turn on the debug mode of that task program only
What should I do? Alternatively, when the debug information of a certain task program becomes unnecessary, the debug mode of the task program may be turned off. Further, in order to easily switch and / or change the debug mode, for example, a display for selecting the switch and / or change of the debug mode is created in a window of a display or the like, and a desired display is selected from the display. By selecting the switching and / or change of the debug mode, a setting may be made so that the debug mode can be switched and / or changed.

Each of the plurality of tasks 14 has a unique process ID. In addition, multiple tasks 14
Each has one or more debug levels set according to the function of the task, the content and type of information to be handled, and the like. FIG. 4 shows functions of the debug manager 13 when the user 40 sets a process ID and a debug level in order to obtain debug information in the debug monitoring device 10 according to one embodiment of the present invention. For example, in FIG. 4, the tasks 14 have process IDs of n, m, and p, respectively. FIG. 4 shows an example in which the user 40 sets to the debug manager 13 that the task 14 having the process ID m is required to have the information having the debug level n. In response, the debug manager 13 sends an information provision request 41 to the task 14 whose process ID is m so as to send information whose debug level is n. Task 14 receiving information provision request 41
After changing the debug level to n, the debug manager 13
To provide. The debug information 42 thus obtained
Is provided to the user by means such as being displayed on a window of a display or output from an output device such as a printer.

[0037]

Embodiment 1 Next, as an embodiment of the present invention, a debug monitoring device and a debug monitoring method having a graphical user interface for monitoring and monitoring the transmission communication device on a computer terminal connected to the transmission communication device will be described. . The debug monitoring device and the debug monitoring method according to the present invention are an example of the above-described embodiment of the present invention, and have the functions shown in FIGS. Is omitted. FIG. 5 is a diagram schematically illustrating a debug monitoring device and a debug monitoring method according to an embodiment of the present invention. FIG. 6 is a diagram illustrating the function of the debug manager in the debug monitoring device and the debug monitoring method according to one embodiment of the present invention. FIG.
FIG. 7 is a sequence diagram illustrating a request for debug information from a debug manager to a task and a transmission of debug information from the task to the debug manager in the debug monitoring device and the debug monitoring method according to one embodiment of the present invention. FIG. 8 is a diagram illustrating a procedure in which a task provides debug information to a debug manager in a debug monitoring device and a debug monitoring method according to an embodiment of the present invention. FIG. 9 is a diagram showing an example of a window displaying a debug level and debug information in the debug monitoring device and the debug monitoring method according to one embodiment of the present invention.

The debug monitor 50 according to the first embodiment of the present invention has a graphical user interface for monitoring and monitoring the transmission communication device on a computer terminal connected to the transmission communication device. Further, as shown in FIG. 5, the debug monitoring device 50 includes a debug manager 53, an alarm monitor task 54, a control task 55, a log task 56, and a debug task 57.
And The debug manager 53 has an interface capable of exchanging information with all tasks operating on the debug monitoring device 50. In this embodiment,
Debug manager 53 and alarm monitor task 5
4. Information can be exchanged with the control task 55, the log task 56, and the debug task 57. The alarm monitor task 54 has a function of displaying a detailed alarm state of the transmission communication device. Control task 55
Has a function of resetting the transmission communication device, performing a loopback test, and switching signals. The log task 56 has a function of acquiring a communication log held by the transmission communication device. These tasks provide debug information to the user through the debug manager 53. The debug task 57 has a debug program, and has a function of debugging another task program.

The operation of the debug monitor 50 according to the first embodiment of the present invention will be described. Such a debug monitoring device 5
When the debug monitoring device 50 is started, a script file having a function to start the debug manager 53 and subsequently the remaining tasks is set in the debug monitoring device 50 at 0. By using such a script file, the debug manager 53 and the remaining task programs are sequentially activated. When the debug task 57 is activated, debugging starts. Each of the alarm monitor task 54, the control task 55, and the log task 56 has a unique process ID. As shown in FIG. 6, the debug manager 53 stores a task database 61 for registering process IDs of these tasks.
Having. The task database 61 functions as a so-called name server in the debug manager 53. That is, when the debug monitoring device 50 is activated,
Subsequently, each task is also activated, and the process ID of the activated task is registered in the task database 61. Further, the process ID of the task started during the debugging process is also registered in the task database 61 as needed.
Thereby, the debug manager 53 can grasp which task in the debug monitor 50 is operating at any time. Further, when a user requests debugging information during the debugging process, the task database 6
From the process ID registered in No. 1, it is possible to grasp which task is the debug information.

Further, in this embodiment, the alarm monitor task 54, the control task 55, and the log task 5
6 is debug level 1 to debug level 3 respectively
Up to three debug levels. The debug level 1 is information indicating the current state of the task, and is a task of displaying which routine processing is being performed inside the task. The debug level 2 is command level information, and is a task of displaying the contents of a command when a command is transmitted to the transmission communication device monitored and monitored by the debug monitoring device 50, and does not include the work of the debug level 1. . The debug level 3 is the debug information in the task, for example, the value of a variable in the task, the name of the method being processed, the exception sending information, and the like. It is possible to detect an unauthorized access or the like from these information. This is an operation of displaying a certain amount of detailed information.

As described above, the debug manager 53
Are the alarm monitor task 54 and the control task 5
5 and an interface that can communicate with the log task 56. Such an interface has the process ID and debug level of these tasks as arguments. FIG. 7 shows the request of the debug information 72 from the debug manager 53 to the task and the transmission of the debug information 72 from the task to the debug manager 53 in the debug monitoring device 50. Upon receiving a request for debug information from the user of the debug monitoring device 50, the debug manager 53 uses the interface to immediately set the debug level and the process I of the task for which the debug information is required.
D71 is set, and the debug information 72 is requested from the task. The task that has received the request for the debug information 72 from the debug manager 53 transmits the debug information 72 of the requested debug level to the debug manager 53.

Each task provides the debug information 72 to the debug manager 53 according to the procedure shown in FIG. FIG. 8 shows a flow of the debug information when the debug manager 53 requests the debug information of the debug level 3. An application task 81 having a filter function 82 is set in the debug monitoring device 50. In the program of each task, debug information 72 such as the value of a variable in the task, the name of the method being processed, the exception sending information, etc. obtained in the work of the debug level 3 is prepared for each function and routine, and the application task 81
Filter function 82 selects only the debug information of the debug level requested from debug manager 53, so that only necessary information is provided to debug manager 53.
Can be provided.

An operation performed by the user on the display when the user requests debug information of a specific task of the debug monitor 50 will be described. A graphical user interface, as shown in FIG.
For example, a debug setting 94 is selected from a pull-down menu 93 of a menu bar 92 provided on a window 91 of the display. When the debug setting 94 is selected, the user is prompted to set a debug level. The user selects a debug level by turning on a radio button of a desired debug level from radio buttons 95, and then selects an OK button (not shown) displayed on a window. Is displayed in the window. The switching and / or change of the debug level is transmitted to the debug manager 53. As shown in FIG. 7, the switching and / or change of the debug level is transmitted to each task, and the debug level can be switched and / or changed during the execution of the debugging. In the debug information 96 displayed in the window, it is possible to display from which line of the program code of each task the message is transmitted, or the execution time. Further, a print button 97 and a file save button 98 are arranged on the window. By using the print button 97 and the file save button 98, the debug information 96 displayed in the window can be directly printed or saved in a file, respectively.

[0044]

Embodiment 2 Another embodiment of the present invention will be described below.
FIG. 10 is a diagram illustrating an example of a window displaying a debug level and debug information in the debug monitoring device and the debug monitoring method according to one embodiment of the present invention.

According to the debug monitoring device and the debug monitoring method of the present embodiment, it is possible to set only the task desired by the user to the debug mode. That is, when the user turns on the debug mode only for a task requiring debug information on the window of the display, the debug manager 53 requests the debug information only for the task concerned. Other functions are almost the same as those of the debug monitoring device 50 of the first embodiment.
A detailed description of that part is omitted. The user
As shown in FIG.
1. A debug setting 94 is selected from a pull-down menu 93 of a menu bar 92 installed on the top. When the debug setting 94 is selected, the user is prompted to select a task requiring debug information. The user clicks the check button 100
By selecting a desired task from among the above, and turning on the check button of the desired task, the debug mode of the task is turned on, and the debug information can be extracted. Next, the user is prompted to set a debug level for each of the selected tasks. In the present application, that the debug mode is ON refers to a state in which debug information can be extracted. For each task for which the debug mode is set to ON, the user selects a debug level by turning on a radio button of a desired debug level from among the radio buttons 95, and then clicks an OK button ( When (not shown) is selected, the debug manager 53 requests debug information of a task desired by the user. Further, the debug information consists only of debug information of a debug level required by the user. Next, such debug information 96 is displayed on the display.

According to the debug monitoring apparatus and the debug monitoring method described above, the debug information 96 can be provided to the user while monitoring the debug in parallel with the progress of the debug task during the runtime of the debug task.
When a failure occurs during debugging, the failure can be corrected immediately, so that the time and cost required for software development can be reduced. The debug manager 53 has a debug mode in which the alarm monitor task 54, the control task 55, and the log task 56 can be switched and / or changed, and a check button of a desired task is selected from the check buttons 100 on the display window. By turning ON and / or OFF, the debug mode can be switched and / or changed, so that the debug information can be immediately provided to the user. Thereby, the time and cost required for software development can be reduced. Further, the debug manager 53 determines that the alarm monitor task 54, the control task 55, and the log task 56 have a process ID and a debug level 1, a debug level 2, and a debug level 3 that can be switched and / or changed, respectively.
In addition to having a function of displaying debug information on a display window, when debug information is needed, only necessary and sufficient debug information can be immediately provided, The time and cost required for software development can be reduced.

[0047]

The debug monitoring apparatus and the debug monitoring method according to the present invention monitor a debug via a debug manager and dynamically provide a user with debug information obtained by the monitor during runtime. If a failure occurs during debugging, the failure can be found immediately, the location of the failure can be accurately specified, and the cause can be grasped in detail. As a result, the failure can be corrected immediately, so that the time and cost required for software development can be reduced.

Further, the debug monitoring apparatus and the debug monitoring method of the present invention provide the debug information obtained by the monitoring to the user at the same time during the runtime while monitoring the debug via the debug manager. If a failure occurs during debugging, the failure can be found immediately, the location of the failure can be accurately specified, and the cause can be grasped in detail. As a result, the failure can be corrected immediately, so that the time and cost required for software development can be reduced.

Further, the debug monitoring device and the debug monitoring method of the present invention provide the user with the debug information obtained by the monitoring in parallel with the progress of the task while monitoring the debug via the debug manager. Thus, when a failure occurs during debugging, the failure can be immediately found, the location of the failure can be accurately specified, and the cause can be grasped in detail. As a result, the failure can be corrected immediately, so that the time and cost required for software development can be reduced.

[Brief description of the drawings]

FIG. 1 is a diagram schematically illustrating a debug monitoring device and a debug monitoring method according to an embodiment of the present invention.

FIG. 2 is a diagram schematically illustrating a debug manager in a debug monitoring device and a debug monitoring method according to an embodiment of the present invention.

FIG. 3 is a diagram illustrating functions of a debug manager and a task in a debug monitoring device and a debug monitoring method according to an embodiment of the present invention.

FIG. 4 is a block diagram showing a configuration of a debug monitoring device and a debug monitoring method according to an embodiment of the present invention. FIG.

FIG. 5 is a diagram schematically illustrating a debug monitoring device and a debug monitoring method according to an embodiment of the present invention.

FIG. 6 is a diagram illustrating functions of a debug manager in a debug monitoring device and a debug monitoring method according to an embodiment of the present invention.

FIG. 7 is a sequence diagram illustrating a request for debug information from a debug manager to a task and a transmission of debug information from the task to the debug manager in the debug monitoring device and the debug monitoring method according to one embodiment of the present invention. is there.

FIG. 8 is a diagram illustrating a procedure in which a task provides debug information to a debug manager in a debug monitoring device and a debug monitoring method according to an embodiment of the present invention.

FIG. 9 is a diagram showing an example of a window displaying a debug level and debug information in the debug monitoring device and the debug monitoring method according to one embodiment of the present invention.

FIG. 10 is a diagram showing an example of a window displaying a debug level and debug information in the debug monitoring device and the debug monitoring method according to one embodiment of the present invention.

[Explanation of symbols]

 REFERENCE SIGNS LIST 10 debug monitoring device 11 operating system (OS) 12 OSAPI 13 debug manager 14 task 21 interface 31 interface 32 information provision request 33 debug information 40 user 41 information provision request 42 debug information 51 debug monitoring device 52 operating system (OS) 53 Debug Manager 54 Alarm Monitor Task 55 Control Task 56 Log Task 57 Debug Task 61 Task Database 71 Debug Level and Process ID 72 Debug Information 81 Application Task 82 Filter Function 91 Window 92 Menu Bar 93 Pulldown Menu 94 Debug Settings 95 Radio Button 96 Debug Information 97 Print button 98 File save button 1 00 Check button

Claims (17)

[Claims] 1. A debug monitoring device that operates on an operating system having a multitasking function and has a plurality of task programs on a debug manager, while monitoring the debug via the debug manager and obtaining the result obtained by the monitoring. A debug monitoring device for dynamically providing debug information to a user during runtime. 2. A debug monitoring device that operates on an operating system having a multitasking function and has a plurality of task programs on a debug manager while monitoring debug via the debug manager. A debug monitoring device for providing debug information to a user at the same time during runtime. 3. A debug monitoring device that operates on an operating system having a multitasking function and has a plurality of task programs on a debug manager, while monitoring the debug via the debug manager and obtaining the monitoring result. A debug monitoring device characterized in that debug information is provided to a user at runtime in parallel with the progress of a task. 4. The system according to claim 1, wherein the plurality of task programs have a process ID and one or more debug levels that can be switched and / or changed.
3. The debug monitoring device according to any one of 3. 5. The debug monitoring device according to claim 1, wherein the plurality of task programs have a debug mode in which switching and / or change is possible. 6. The switching of the debug mode and / or the change thereof can be executed by selecting from a display on a display window.
2. The debug monitoring device according to 1. 7. The debug monitoring device according to claim 1, further comprising a function of displaying the debug information on a window of a display. 8. Operating on an operating system having a multitasking function, comprising a plurality of task programs on a debug manager, and monitoring debugs via the debug manager while executing debug information obtained by the monitoring during runtime. A debug monitoring method characterized in that the method is dynamically provided to a user. 9. Operating on an operating system having a multitasking function, comprising a plurality of task programs on a debug manager, and monitoring debug via the debug manager, while executing debug information obtained by the monitoring during runtime. A debugging monitoring method characterized in that the debugging monitoring method is provided to the user simultaneously. 10. Operating on an operating system having a multi-tasking function, comprising a plurality of task programs on a debug manager, and monitoring debug via the debug manager, while executing debug information obtained by the monitoring during runtime. And providing the user with the task in parallel with the progress of the task. 11. The method according to claim 8, wherein the plurality of task programs have a process ID and one or more debug levels that can be switched and / or changed.
11. The debugging monitoring method according to any one of items 10 to 10. 12. The debug monitoring method according to claim 8, wherein the plurality of task programs have a debug mode that can be switched and / or changed. 13. The debug monitoring method according to claim 12, wherein the switching and / or changing of the debug mode can be executed by selecting from a display on a display window. 14. The debug monitoring method according to claim 8, further comprising a function of displaying the debug information on a window of a display. 15. Operating on an operating system having a multitasking function, comprising a plurality of task programs on a debug manager, and monitoring debug via the debug manager, while executing debug information obtained by the monitoring during runtime. A computer-readable recording medium storing a debug monitoring program, which is dynamically provided to a user. 16. An operating system having a multitasking function, a plurality of task programs provided on a debug manager, and monitoring of debugging via the debug manager while executing debugging information obtained by the monitoring during runtime. A computer-readable recording medium storing a debug monitoring program, which is provided to a user simultaneously. 17. A program which runs on an operating system having a multitasking function, has a plurality of task programs on a debug manager, monitors debugging via the debug manager, and executes debugging information obtained by the monitoring during runtime. A computer-readable recording medium storing a debug monitoring program, which is provided to a user in parallel with the progress of a task.