KR20070019881A - Error management system providing debugging information and method using the same - Google Patents

Abstract

The present invention relates to an error management system and method, and more particularly, to an error management system and method for collecting and managing errors occurring in a client application in an online service system consisting of a server application and a client application. An error management system for managing an error occurring in a client application according to the present invention collects error information and crash dump files by intercepting an event when the client application ends abnormally, and collects the collected error information and crash dump files. Receiving an error information and a crash dump file transmitted from the client terminal independently of a client terminal for transmitting the data in a predetermined format through a network and an online service server for executing a server application for providing a service corresponding to the client application. And an error collection server for storing and providing function and object file information in which an error occurs by using an address included in the error information during debugging. Therefore, it is possible to more effectively manage and debug errors of client applications occurring in the client terminal.

Client Application, Error Collection, Error Management, Debugging

Description

Error management system that provides debugging information and error management method using the same {ERROR MANAGEMENT SYSTEM PROVIDING DEBUGGING INFORMATION AND METHOD USING THE SAME}

1 is a block diagram of an online service system according to the prior art.

2 is a block diagram of an error management system according to an embodiment of the present invention.

3 is a block diagram illustrating an example of a client terminal illustrated in FIG. 2.

4 is a block diagram illustrating another example of the client terminal illustrated in FIG. 2.

5 is a diagram illustrating a screen displaying an example of error information stored in an error collection server.

FIG. 6 is an example of a subject setting screen for collecting error information shown in FIG. 5.

FIG. 7 is an example of a screen displayed when a specific address is clicked among the error information shown in FIG. 5.

8 is a flowchart illustrating an error management method according to an exemplary embodiment of the present invention.

9 is a flowchart illustrating an error management method according to another exemplary embodiment of the present invention.

10 is an internal block diagram of a general purpose computer device that may be employed to perform the error management method and the error transmission method according to the present invention.

<Explanation of symbols for the main parts of the drawings>

210-1 to 210-N: client terminals

220-1 to 220-N: online service servers

230: error collection server

The present invention relates to an error management system and method, and more particularly, to an error management system and method for collecting and managing errors occurring in a client application in an online service system consisting of a server application and a client application.

As the Internet becomes more common, an online service system for providing an online service by connecting a client application installed in each user terminal and a server application installed in a service server through a network is becoming common. Representative examples of such online services include online games such as Lineage, Cartrider, and King You Golf.

1 is a block diagram of an online service system according to the prior art.

Referring to FIG. 1, the online service system according to the related art includes client terminals 110-1, 110-2,..., 110 -N and an online service server 120-1, 120-2. , 120-N).

Each of the client terminals 110-1, 110-2,..., 110 -N is connected to each of the online service servers 120-1, 120-2,..., 120 -N and a network such as the Internet. Connected through. At this time, each of the client terminals 110-1, 110-2,..., 110 -N includes some or all of the online service servers 120-1, 120-2,..., 120 -N. Client application is installed to perform the online service provided by.

For example, the online service server 120-1 may be a 'lineage' game server, and the online service server 120-2 may be a 'you are the king of golf' game server. At this time, the client terminals 110-1, 110-2,..., 110 -N may be installed with the 'you are the king of golf' game client application for performing the 'you are the king of golf' game service. have.

In general, the client terminals 110-1, 110-2,..., 110 -N have different hardware or operating systems, and the client terminal and the server application interoperate with each other. The illustrated online service system requires complex debugging tasks as compared to normal program debugging. That is, in the process of developing an application, an unexpected error occurs when a client application that has been running smoothly is directly downloaded and executed to the client terminals 110-1, 110-2, ..., 110-N. many. In addition, even if an error occurs in the client application in the client terminals 110-1, 110-2,..., 110 -N, the user of the client terminal posts an error occurring in his terminal on the program manager bulletin board. If you don't report the error by e-mail notification to the administrator, it is difficult for the program developer to know whether the error has occurred, and even if you know the error, the error may be due to the specific client terminal environment. It is difficult to accurately reproduce the error.

For example, when the online service server 120-2 is a 'you are the king of golf' game server, the game program developer sets up a virtual client and operates in conjunction with the online service server 120-2 to 'you' Performs the King of Golf 'game test. After performing tests on a virtual client considering various client environments and debugging all errors, the program developer can download the game application from the client terminals 110-1, 110-2, ..., 110-N online. It operates in conjunction with a server application in the service server 120-2. However, in most cases, an error that does not occur in the test occurs in the client terminals 110-1, 110-2,..., 110 -N, and the client terminals 110-1, 110-2. , ..., 110-N) users' complaints only accumulate, and it is difficult to know whether the error occurred or even the cause of the error on the online service server 120-2, and even if the error occurs, It is difficult to debug because the state is unknown.

Therefore, there is an urgent need for an error management system and method for more effectively collecting and managing errors of client applications occurring in client terminals.

The present invention has been made to solve the problems of the prior art as described above, an object of the present invention is to provide an error management system and error management method that can efficiently collect the errors occurring in the client application, and manage them at a glance. It is done.

The present invention also collects error information and crash dump files by intercepting an event when an error occurs in the client application, and transmits the error management to conveniently collect the error of the client application without a separate error reporting procedure. It is an object to provide a system and an error management method.

In addition, the present invention facilitates error information and crash dump files stored in the error collection server through the network as long as service providers providing different online services transmit errors of the client application to the error collection server according to a predetermined format. It is an object of the present invention to provide an error management system and an error management method that can be easily provided.

In addition, the present invention collects and stores error information and crash dump files in the client terminal primarily when the client application is abnormally terminated, and transmits the stored error information and crash dump files through the network when the client application is restarted later. It is an object of the present invention to provide an error management method and an error transmission method capable of stably transmitting error information and crash dump files.

In addition, the present invention can be easily applied to anyone in a variety of platform environments by transmitting error information and crash dump files using the HTTP protocol, an error management system and error management method that can prevent transmission blocking by routers or firewalls The purpose is to provide.

Another object of the present invention is to provide an error management system and an error management method capable of effectively reproducing errors generated in a client terminal by transmitting error information and crash dump files when the client application is abnormally terminated.

In addition, an object of the present invention is to be able to determine the client environment that occurs a lot of errors by transmitting the client environment information of the client terminal when the client application is abnormally terminated.

In addition, the present invention provides an error management system and error management method that can easily find the function and the object file for the error collected on the server side by using a table in which the object file and the function is de-indexed by address For the purpose of

Furthermore, an object of the present invention is to provide an error management system and an error management method capable of varying the method of selecting, grouping, and sorting collected errors by simply operating a pointing device such as a mouse.

In order to achieve the above object and solve the problems of the prior art, an error management system for managing an error occurring in a client application according to an embodiment of the present invention, when the client application terminates abnormally An online service server that collects the error information and the crash dump file, collects the error information and the crash dump file, and transmits the collected error information and the crash dump file in a predetermined format through a network and a server application that provides a service corresponding to the client application. Independent of the error, and receives and stores the error information and crash dump file transmitted from the client terminal, and provides an error function function and object file information using the address included in the error information during debugging Characterized in that it comprises a collection server.

In addition, an error management method for managing an error occurring in a client application according to another embodiment of the present invention includes the steps of operating in conjunction with a server application executed in an online service server through a network with a client application performed in a client terminal, An error collection server receiving and storing error information about the client application from the client terminal through the network; and a function and an object having an error using the address included in the error information when the error collection server is debugged. Providing file information.

In this case, the error information about the client application may be collected by an error processing module installed in the client terminal and transmitted in a predetermined format through the network.

In this case, the error collection server may provide source code information together with the function and object file information in which the error occurs. In this case, the source code information may include a path, a source code name, and a line number of the source code. In this case, the path of the source code may be a path on the computer that generated the map file.

In addition, an error management method for managing an error occurring in a client application according to another embodiment of the present invention, the step of operating the client application running in the client terminal and the server application running in the online service server interworking through the network And receiving and storing error information about the client application from the client terminal through a network, and providing function and object file information in which an error occurs by using an address included in the error information during debugging. It is characterized by.

In this case, an object file is an file generated when the source file is compiled.

At this time, the function and object file information includes all information about the function and the object file, such as a function name and an object file name.

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

2 is a block diagram of an error management system according to an embodiment of the present invention.

Referring to FIG. 2, an error management system according to an exemplary embodiment of the present invention may include client terminals 210-1,..., 210 -N, and online service servers 220-1,. N) and error collection server 230.

Client terminals may be computers, pocket PCs, notebook computers, PDAs, mobile phones, game machines, and the like.

Client applications are installed in each of the client terminals 210-1,..., 210 -N. Two or more client applications may be installed in each of the client terminals 210-1,..., 210 -N.

Each client application operates in conjunction with a server application installed in online service servers 220-1, ..., 220-N through a network. For example, the client terminal 210-1 may be provided with a game client for the 'You are the king of golf' game service and a game client for the 'Lineage' game service. At this time, the 'You are the king of golf' game service works in conjunction with the server application installed on the online service server 220-1, 'Lineage' game service is linked to the server application installed on the online service server 220-2 Can be operated.

Each of the online service servers 220-1, ..., 220-N may execute a server application for one online service, and two or more online servers together perform a server application for one online service. You may. For example, the online service servers 220-1 and 220-2 may all be servers for 'you are the king of golf' game services.

In addition, an error processing module may be installed in each of the client terminals 210-1,..., 210 -N. The error handling module intercepts an event, collects error information and crash dump files when the client application executed in the client terminal abnormally terminates, and transmits the collected error information and crash dump files in a predetermined format through a network. .

At this time, the abnormal termination of the client application means that the client application can no longer continue to operate and a predetermined event (or exception) set by an operating system (OS) or the like occurs. An event may be generated by the operating system when the client application terminates abnormally. In this case, the operating system may be Microsoft's Windows series, Apple's macOS series, Palm's PalmOS series or various Real Time OS (RTOS).

For example, the error handling module may be computer program code written to perform a predetermined action in an event handler.

The error information may include a system time when the client application is abnormally terminated, an address where an error occurs, and a cause of the error. For example, the cause of the error may be "Access Violation" or "Divide By Zero". The error information may include a call stack, register information, corresponding program version information at the time of error occurrence, and module related information used by the corresponding program at the time of error occurrence.

The call stack shows the call relationships between functions in the program at the time of the error. For example, the call stack may have a relationship of calling Print function from main function and GetData function from Print function. At this time, the call stack included in the error information may transmit only the address value of each function. The receiving side receiving the error information can find out a function corresponding to the transmitted address using the module related information. For example, when "Ox04001000 Ox04000700 Ox04000103" is transmitted to the call stack, the receiving side may associate 'Ox04001000' and GetData function, 'Ox04000700' and Print function, and 'Ox04000103' and main function, respectively, using module related information. .

The register information may include data stored in a register of a central processing unit (CPU) when an error occurs. For example, in the case of using an Intel X86 CPU, the register information may include data stored in registers such as EAX, EBX, ECX, EDX, ESI, EDI, EBP, and EIP. Register information can be very useful for finding out what happened at the time of an error.

The module related information may include the name of the module, the checksum of the module, and the memory address in which the module is loaded.

In some embodiments, the error information may include client environment information of the client terminal. In this case, the client environment information may include a type of hardware such as a central processing unit (CPU) or a graphics card and a version of a device driver used for driving the hardware.

A crash dump file is a file that contains an error situation such as information stored in memory when an error occurs while an application is running. Therefore, a crash dump file can be very useful in finding out what part of the system caused an error. For example, the crash dump file may be generated by an operating system of Microsoft Corporation.

The error handling module may be separately provided for each client application, or two or more client applications may share one error handling module. For example, you may have a king error application and a lineage application each have a corresponding error handling module, and you may share a single error handling module with the golf king application and the lineage application. It may be.

3 is a block diagram illustrating an example of a client terminal illustrated in FIG. 2.

Referring to FIG. 3, the client terminal 210-1 shown in FIG. 2 includes client applications 311 and 321 and error processing modules 312 and 322.

The error processing module 312 processes an error generated by the client application 311 in correspondence with the client application 311, and the error processing module 322 corresponds to the client application 321 and occurs in the client application 321. Handle the error

Although FIG. 3 illustrates an example in which two client applications 311 and 321 are installed, the client terminal 210-1 may include three or more client applications or may include only one client application. . In the example shown in FIG. 3, since the error processing module is provided for each client application, the number of client applications is provided.

4 is a block diagram illustrating another example of the client terminal illustrated in FIG. 2.

Referring to FIG. 4, the client terminal 210-1 illustrated in FIG. 2 includes client applications 411 and 421 and an error processing module 430.

The error processing module 430 processes an error occurring in the client application 411 and the client application 421. That is, the client application 411 and the client application 421 share the error processing module 430.

In FIG. 4, the case where two client applications 411 and 421 are installed is illustrated as an example, but the client terminal 210-1 may include three or more client applications or may include only one client application. . In addition, three or more client applications may share an error handling module.

In the above description, the client terminal 210-1 shown in FIG. 2 has been described as an example. However, the client terminal 210-1 is also applied to the other client terminals 210-2,. The description may be applied as it is.

According to an embodiment, the error processing module collects and stores the error information and crash dump file in the client terminal when the client application ends abnormally, and stores the error information and crash dump stored when the client application is restarted. A file can be transmitted in the predetermined format via the network. If the client application terminates abnormally, the system is likely to be unstable. Therefore, collect error information and crash dump files in the client terminal and save the error information and crash dump files once the client application is started again. Can reliably send error information and crash dump files.

In addition, the error processing module may collect error information and crash dump files when the client application is abnormally terminated and immediately transmit them in a predetermined format through the network.

At this time, the network may be a wired / wireless Internet.

The error processing module may transmit the error information and the crash dump file using HTTP (HyperText Transfer Protocol). In this case, the port used may be 80 ports. In this way, by using the HTTP protocol and port 80, error information can be easily transmitted in any client model, and transmission can be prevented from being blocked by a router or a firewall.

In this case, the error processing module may transmit the error information and the crash dump file in the form of a uniformly used URL (Uniform Resource Locator) by using the HTTP protocol.

In addition, the error processing module may use the Simple Object Access Protocol (SOAP) protocol to transmit the error information and the crash dump file using an existing Internet infrastructure without being accidentally blocked by a firewall. .

Referring back to FIG. 2, the error collection server 230 receives and stores error information and crash dump files transmitted from an error processing module through a network such as a wired / wireless internet.

In this case, the error collection server 230 may store the error information and the crash dump file transmitted through the network in a separate database such as an Oracle database.

In this case, the error collection server 230 may sort the error information and the crash dump file stored in the error collection server 230 according to the address of the error occurring in the client application, or the error collection server according to the cause of the error occurring in the client application ( Error information and crash dump files stored in 230 may be sorted.

In addition, when the error information includes the client environment information of the client terminal, the error collection server 230 may be used to drive a kind of hardware such as a central processing unit (CPU) or a graphics card of the client terminal or drive the hardware. The error information stored in the error collection server 230 may be sorted according to the version of the device driver. Therefore, it is possible to grasp at a glance which hardware combination generates a lot of errors at the receiving side which receives the error information, so that the error can be effectively debugged in cooperation with a manufacturer such as hardware.

Therefore, whenever an error occurs in a client application included in the client terminals 210-1, ..., 210 -N, and the client application is abnormally terminated, an error information and a crash dump file are automatically generated from the error processing module. Is transmitted and collected at the error collection server 230.

At this time, the error management system is not shown in Figure 2 is connected to the error collection server 230 via a network to further receive an error management terminal provided with the error information and crash dump file stored in the error collection server 230 It may include. In this case, the error management terminal may be a computer, a pocket PC, a notebook computer, a PDA, a mobile phone, and a game machine. Accordingly, various errors for various online services may be uniformly collected / managed by the error collection server 230, and an administrator may easily access accumulated error information and crash dump files through the Internet.

The error collection server 230 extracts the address of a function included for each object file generated by compiling the source code of the online service program, and de-indexes the object file for each address. A table can be provided to which functions are mapped. In this case, reverse indexing refers to indexing in the order of 'specific memory address-> object file and function'. In this case, the table may correspond to an object file name and a function name for each address. In this case, the source code information corresponding to each address may correspond to the table. Further, the source code information may include a file path, a file name, and the number of lines in the file.

During debugging, the error collection server may search for the object file and the function of the address included in the error information in the table and provide debugging information such as the function and the object file information. In this case, the function and object file information may include a function name and an object file name.

5 is a diagram illustrating a screen displaying an example of error information stored in an error collection server.

For example, FIG. 5 may be a screen displayed on an error management terminal connected to an error collection server through a network.

Referring to FIG. 5, it can be seen that the errors after June 5, 2005 are selected by the period selecting unit 510. Therefore, errors collected before June 5, 2005 are not selected. In the example shown in FIG. 5, the selection start date and the selection end date are both implemented in a pull-down menu manner so that the period can be selected only by simple operation of a pointing device such as a mouse.

The query generator 520 creates a structured query language (SQL) that selects, groups, and sorts a database with a click of a mouse. In the example illustrated in FIG. 5, the query generator 520 may select a word that may be located after the "select", "group by", and "order by" commands from a pull down menu, thereby making a complex structured query word. Even if you don't know the syntax, you can easily select, group and sort the error information you want.

In addition, the query preparing unit 520 provides a table in which a natural query such as Korean and a specific query are matched 1: 1, and when a user selects a desired natural language from the table, the query matching the selected natural language is used as a query as error information. You can select, group, and sort them. For example, a query corresponding to "error information for each error occurrence address in the order of occurrence of errors" is matched, and the query is matched when the user selects "error information for error occurrence address in the order of occurrence of many errors". Error information can be processed and displayed. Therefore, in the case of frequently used queries, anyone can easily use it to display error information.

The query display unit 530 displays the query created by the query generator 520.

In this case, the query displayed on the query display unit 530 may be stored in a table by corresponding to the input natural language 1: 1 by inputting a natural language such as Korean by clicking “add to custom query”.

The result display unit 540 displays error information according to the query displayed on the query display unit 530.

In the example of FIG. 5, the result display unit 540 shows that the error information stored in the error collection server is sorted in order from the address where a lot of errors occur. As shown in FIG. 5, the result display unit 540 includes an address 541 in which an error occurs in order of occurrence of an error, a cause of an error 542, a call stack 543, register information 544, and program version information. 545, module related information 546, crash dump file link 547, and error occurrence count 548 are displayed in the result table.

The address where the error occurred 541 indicates a memory address where an error occurred, such as "10018BB9", "1000E119", or the like.

The cause 542 of the error indicates the reason or type of the error, such as "EXCEPTION_FLT_DIVIDE_BY_ZERO", "EXCEPTION_ACCESS_VIOLATION", and the like. The cause of the error 542 may vary depending on the operating system installed on the client computer.

Call stack 543 represents the call relationship between functions in the program at the time of the error. In the example shown in FIG. 5, call stack 543 represents the address value of each function.

Register information 544 represents data stored in a register of the client computer at the time of the error. For example, register information 544 is "EAX: FFFFFFE2 EBX: 029D2420 ECX: 00000000 EDX: 0000001E ESI: 021EC1D8 EDI: 0000000F EBP: 00000000 EIP: 00000000 SegCs: 0000001B EFlags: 00010286 Esp: 00000008 SegGS: 00000000" Can be displayed.

The program version information 545 indicates version information of the corresponding program at the time of the error occurrence.

The module related information 546 represents module related information used by the corresponding program at the time of the error occurrence. The module related information 546 may include a name of the module, a checksum of the module, a memory address into which the module is loaded, and the like.

The crash dump file link 547 may be a link to download the corresponding crash dump file.

In this way, the user can simply access the error collection server, access the desired error information, and arrange the desired form, so that errors occurring in the client application can be managed at a glance. Furthermore, programmers can debug in the order of the most frequent errors, effectively debugging errors in the client application.

According to an embodiment, when each field of the result display unit 540 illustrated in FIG. 5 is selected, detailed information corresponding to the field may be displayed or arranged in the order of the fields. For example, in the example illustrated in FIG. 5, when the '10018BB9' field of the address 541 where an error occurs is selected, detailed information about errors occurring at the '10018BB9' address may be displayed. For example, in the example shown in FIG. 5, when the 'version' field of the version information 545 is clicked with a pointing device such as a mouse, error information may be arranged in program version order.

FIG. 6 is an example of a subject setting screen for collecting error information shown in FIG. 5.

Referring to FIG. 6, an address 541 where an error shown in FIG. 5 occurs, a cause 542 of an error, a call stack 543, register information 544, program version information 545, and module related information 546. Field name 610, field type 620, omission 630, key 640, default 650, and other information for each item to collect crash dump file link 547 information. 660 and the delete button 670 are set.

The field name 610 corresponds to the name of each column of the result display unit of FIG. 5 and includes "address" or "reason".

The field type 620 is a data type of items corresponding to each column of the result display unit of FIG. 5.

The omission 630 indicates whether the corresponding item can be omitted. For example, if the skippability 630 is set to "YES", the corresponding item may be omitted when transmitting / receiving error information. At this time, if omission 630 is set to "NO", the corresponding item must be included in error information transmission / reception.

Key 640 represents the key setting in the database.

The default value 650 indicates a default value to be applied when the omission 630 is an item that can be omitted as "YES" and thus the item is not transmitted from the client side.

The miscellaneous information 660 is for enabling the setting of miscellaneous information necessary for each item.

The delete button 670 is for deleting the corresponding item.

In order to collect error information as displayed on the result display unit 540 of FIG. 5, a subject is generated by setting necessary items as in the example shown in FIG. 6, and an error corresponding to each item of the generated subject is generated. Set the client program to send the information from the client side so that the client terminal collects the desired error information. If a new item is needed, add a new item in the subject as shown in FIG. 6 and add a field name 610, field type 620, omission 630, key 640, default value 650, and the like. Other information 660 may be set, and if it is determined that the set item is unnecessary, the delete item 670 may delete the corresponding item.

FIG. 7 is an example of a screen displayed when a specific address is clicked among the error information shown in FIG. 5.

Referring to FIG. 7, when a field corresponding to an address 541 in which an error occurs or an address in the call stack 543 is clicked among the fields displayed on the result display unit 540 of FIG. 5, the call stack starts from the clicked address. As can be seen, the related address 710, the module 720 corresponding to the related address, the function / object file information 730 corresponding to the related address 710, and the source code information 740 are displayed.

The associated address 710 follows the function calling the function from the function in which the error occurs according to the call relationship of the function, and the address corresponding to each function is displayed.

Module 720 represents a module that includes a function corresponding to an associated address 710.

The function / object file information 730 represents information of a function corresponding to the related address 710 and an object file to which the function belongs. The function / object file information 730 may include a function name and an object file name.

The source code information 740 indicates a file path, a file name, and a line number in the file of the source code corresponding to the related address 710.

At this time, each address, module, function, object file, and source code can be mapped using a table that compiles all the source code for the application, extracts the address corresponding to the function for each object file, and de-indexes the address. have.

As shown in FIG. 7, the error collection server of the error management system of the present invention provides the module, function, object file, and source code information corresponding to the address with respect to the address at which the error occurs so that the online service programmer can easily obtain the client. Allows you to debug errors in your application.

8 is a flowchart illustrating an error management method according to an exemplary embodiment of the present invention.

Referring to FIG. 8, in the error management method according to an exemplary embodiment of the present invention, a client application executed in a client terminal and a server application executed in an online service server interoperate with each other through a network (S810).

In this case, two or more client terminals may be installed with client applications, and two or more online service servers may provide different server applications. In addition, two or more client applications may be installed in one client terminal.

In an error management method for managing an error occurring in a client application, an error processing module installed in the client terminal collects error information and crash dump files generated in the client application and transmits the crash information in a predetermined format through a network (S820). .

In this case, the error handling module may be set to correspond to each client application, or two or more client applications may share one error handling module.

In this case, the step S820 may be performed by intercepting the event when the client application is abnormally terminated, collecting the error information and the crash dump file, and storing the error information and the crash dump file in the client terminal. Transmission of error information and crash dump files in the predetermined format via the network may be performed step by step.

In addition, transmission of the error information and the crash dump file through the network may be transmitted to the 80 port using the HyperText Transfer Protocol (HTTP). Therefore, error information can be easily sent from any client model, and transmission can be prevented from being blocked by a router or a firewall.

When the error information and the crash dump file are transmitted, the error management method for managing an error occurring in the client application receives and stores the error information and the crash dump file transmitted through the network from the error collection server (S830).

In addition, the error management method for managing an error occurring in a client application provides a function and object file information in which an error occurs by using an address included in the error information when debugging in an error collection server (S840).

In this case, the providing of the function and the object file information in which the error occurs (S840) extracts the address of a function included for each object file generated by compiling source code and reverse indexes the extracted address so that the object file and Maintaining a table to which functions correspond, and searching the table for an object file and a function for an address included in the error information, and providing the function and object file information.

According to an embodiment, in the error management method, when a field of an error information screen displayed on an error management terminal is selected, detailed information of the selected field is displayed or error information is sorted based on the selected field, and the structured query is formed in a pull-down menu format. When prepared, the error information is processed and displayed according to the structured query word, and a table storing a structured query word corresponding to a natural language is provided. When the natural language is selected, the error information may be processed and displayed according to a corresponding structured query word. .

Each step shown in FIG. 8 may be performed in the order shown in FIG. 8, in the reverse order, or simultaneously.

9 is a flowchart illustrating an error management method according to another exemplary embodiment of the present invention.

Referring to FIG. 9, in the error management method according to another exemplary embodiment of the present invention, a client application executed in a client terminal and a server application executed in an online service server interoperate with each other through a network (S910).

In this case, two or more client terminals may be installed with client applications, and two or more online service servers may provide different server applications. In addition, two or more client applications may be installed in one client terminal.

An error management method for managing an error occurring in a client application receives and stores error information about the client application from the client terminal through a network (S920).

In addition, the error management method for managing errors occurring in the client application provides debugging information such as a function and object file information in which an error occurs by using an address included in the error information at the time of debugging (S930).

Since the description of step S840 illustrated in FIG. 8 may be applied directly to step S930 of FIG. 9, a detailed description of step S930 is omitted.

Each step shown in FIG. 9 may be performed in the order shown in FIG. 9, in the reverse order, or simultaneously.

Contents not described in connection with the method described with reference to FIGS. 8 and 9 are omitted in the embodiments related to the error management system.

The error management method according to the present invention can be implemented in the form of program instructions that can be executed by various computer means and recorded in a computer readable medium. The computer readable medium may include program instructions, data files, data structures, etc. alone or in combination. Program instructions recorded on the media may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well-known and available to those having skill in the computer software arts. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tape, optical media such as CD-ROMs, DVDs, and magnetic disks, such as floppy disks. Magneto-optical media, and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. The medium may be a transmission medium such as an optical or metal wire, a waveguide, or the like including a carrier wave for transmitting a signal specifying a program command, a data structure, or the like. Examples of program instructions include machine code, such as produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter. The hardware device described above may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.

10 is an internal block diagram of a general purpose computer device that may be employed to perform the error management method in accordance with the present invention.

The computer device 1000 includes one or more processors 1010 connected to a main memory device including a random access memory (RAM) 1020 and a read only memory (ROM) 1030. The processor 1010 is also called a central processing unit (CPU). As is well known in the art, the ROM 1030 serves to transfer data and instructions to the CPU unidirectionally, and the RAM 1020 typically transmits data and instructions bidirectionally. Used to. RAM 1020 and ROM 1030 may include any suitable form of computer readable media. Mass storage 1040 is bi-directionally coupled to processor 1010 to provide additional data storage capability, and may be any of the computer readable recording media described above. The mass storage device 1040 is used to store programs, data, and the like, and is a secondary memory device such as a hard disk which is generally slower than the main memory device. Certain mass storage devices such as CD ROM 1060 may be used. The processor 1010 may include one or more input / output interfaces, such as a video monitor, trackball, mouse, keyboard, microphone, touchscreen display, card reader, magnetic or paper tape reader, voice or handwriting reader, joystick, or other known computer input / output device. 1050 is connected. Finally, the processor 1010 may be connected to a wired or wireless communication network through the network interface 1070. Through this network connection, the procedure of the method described above can be performed. The apparatus and tools described above are well known to those skilled in the computer hardware and software arts. On the other hand, the hardware device described above may be configured to operate as one or more software modules to perform the operations of the present invention.

As described above, although the present invention has been described with reference to limited embodiments and drawings, the present invention is not limited to the above embodiments, and those skilled in the art to which the present invention pertains various modifications and variations from such descriptions. This is possible.

Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the claims below but also by the equivalents of the claims.

The error management system and error management method of the present invention can efficiently collect errors occurring in a client application and manage them at a glance.

In addition, when an error occurs in a client application, the present invention may collect an error information and a crash dump file by intercepting an event and transmitting the same, and conveniently collect the error of the client application without a separate error reporting procedure.

In addition, the present invention provides error information and crash dump files stored in the error collection server through the network as long as service providers providing different online services transmit errors of the client application to the error collection server according to each predetermined format. It can be provided easily.

In addition, the present invention collects and stores error information and crash dump files in the client terminal primarily when the client application is abnormally terminated, and transmits the stored error information and crash dump files through the network when the client application is restarted later. This makes it possible to reliably transmit error information and crash dump files.

In addition, the present invention can be easily applied to anyone in various platform environments by transmitting error information and crash dump files using the HTTP protocol, it is possible to prevent transmission blocking by the router or firewall.

In addition, the present invention can effectively reproduce the error occurred in the client terminal by sending the error information and crash dump file when the client application terminates abnormally.

In addition, according to the present invention, when the client application is abnormally terminated, it is possible to identify the client environment in which a lot of errors occur by transmitting the client environment information of the client terminal.

In addition, the present invention can easily find the function and the object file for the error collected by the server using a table in which the object file and the function corresponding to the address is de-indexed.

Furthermore, the present invention can vary the method of selecting, grouping and sorting the collected errors by simply manipulating a pointing device such as a mouse.

Claims (19)

In an error management system for managing errors occurring in client applications, A client terminal intercepting an event when the client application terminates abnormally, collecting error information and crash dump files, and transmitting the collected error information and crash dump files in a predetermined format through a network; And Independent of an online service server that performs a server application that provides a service corresponding to the client application, receives and stores error information and crash dump files transmitted from the client terminal, and includes the address included in the error information during debugging. Collection server that provides information on the function and object file where the error occurred Error management system comprising a. The method of claim 1, The error collection server Extracting the address of a function included for each object file generated by compiling source code, and inversely indexing the extracted address, and having a table corresponding to the object file and function for each address, And searching the table for an object file and a function corresponding to an address included in the error information to provide the function and object file information. The method of claim 1, The error management system And an error management terminal accessing the error collection server through the network and receiving error information and crash dump files stored in the error collection server. The method of claim 3, The error collection server Selecting a field of an error information screen displayed on the error management terminal to display detailed information of the selected field or to sort the error information based on the selected field; The method of claim 1, The error collection server And constructing a structured query in the form of a pull-down menu and processing and displaying error information according to the structured query. The method of claim 1, The error collection server And a table storing a structured query word corresponding to a natural language, and if the natural language is selected, processing and displaying the error information according to the corresponding structured query word. The method of claim 1, The error collection server And when any address is clicked in the result table displaying the error information, one or more of module information, function information, object file information, and source code information corresponding to the clicked address are displayed. The method of claim 1, The error collection server And providing a link of the dump file so that a user of the error management terminal can download the dump file through the link. The method of claim 1, The client terminal When the client application terminates abnormally, the error information and crash dump file are collected and stored in the client terminal. When the client application is restarted, the stored error information and crash dump file are stored through the network. Error management system, characterized in that the transmission in the format. The method of claim 1, The client terminal Error management system characterized in that for transmitting the error information and crash dump file in the form of a URL using the HTTP protocol. The method of claim 1, The client terminal Transmitting the error information and the crash dump file using a SOAP protocol. The method of claim 1, The error information is Error management system comprising the client environment information of the client terminal. An error management method for managing an error occurring in a client application, Operating a server application executed in an online service server in association with a client application executed in a client terminal through a network; Receiving, by an error collecting server, error information about the client application from the client terminal through the network; And Providing, by the error collecting server, function and object file information in which an error occurs by using an address included in the error information during debugging. Error management method comprising a. The method of claim 13, Error information for the client application And collected by an error processing module installed in the client terminal, transmitted in a predetermined format through the network, and received by the error collection server. The method of claim 13, Providing the function and object file information in which the error occurs Extracting an address of a function included for each object file generated by compiling source code, and de-indexing the extracted address to maintain a table corresponding to the object file and the function for each address; And And searching the table for an object file and a function corresponding to an address included in the error information, and providing the function and object file information. The method of claim 13, The error management method Selecting a field on the displayed error information screen displays the details of the selected field or sorts the error information based on the selected field. When a structured query is made in the form of a pull-down menu, error information is processed and displayed according to the structured query. And a table storing a structured query word corresponding to a natural language, and if the natural language is selected, processing the error information according to the corresponding structured query word and displaying the processed error information. The method of claim 13, Receiving and storing the error information Error management method characterized in that for receiving the error information in the form of a URL using the HTTP protocol. The method of claim 13, Receiving and storing the error information Receiving the error information using a SOAP protocol. A computer-readable recording medium in which a program for executing the method of any one of claims 13 to 18 is recorded.

Images