Error management system and method of using the same

• US 7,702,959 B2
• Filed: 08/01/2006
• Issued: 04/20/2010
• Est. Priority Date: 08/02/2005
• Status: Active Grant

• Current Assignee: NHN Entertainment Corporation
• Original Assignee: NHN Corporation
• Inventors: Hwang, Min Jae, Park, Hyun-Woo
• Primary Examiner(s): Beausoliel; Robert
• Assistant Examiner(s): Lottich; Joshua P
• Application Number:
  US11/498,121
• Publication Number:
  US 20070033281A1
• Time in Patent Office: 1,358 Days
• Field of Search: 714/37, 714/38, 714/48, 714/57
• US Class Current: 714/38.11
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications

Abstract

An error management system for managing an error occurring in a client application includes: a client terminal which intercepts an event, and collects error information and a crash dump file when the client application is abnormally terminated, and transmits the collected error information and the crash dump file in a predetermined format via a network; and an error collecting server which receives the error information and the crash dump file from the client terminal, and stores the received error information and the crash dump file for each online service, the error collecting server being independent from an online service server that executes a server application providing a service in correspondence to the client application.

Claims

1. An event collecting server system comprising:

a receiving module configured to receive information on an event in a client application when the client application is abnormally terminated, wherein the receiving module is configured to extract an address of the event by compiling source code of an object file, wherein the object file includes a function of identifying where the event has occurred; and

a storage module configured to store the received information in association with an online service with which the information is associated.

2. The system of claim 1, wherein the information comprises error data.

3. The system of claim 1, wherein the information includes an address for the event and an object file including a function where the event has occurred, and wherein the receiving module uses the address to provide information on the object file.

4. The system of claim 1, further comprising:

a processing module configured to count a number of event occurrences for the address, wherein the event occurrence includes an association between the information and the crash dump file.

5. The system of claim 1, wherein the storage module is configured to store a table where the object file and the function are associated with the address by inverse-indexing, and wherein the object file is retrieved by reference to the address.

6. The system of claim 1, further comprising:

a processing module configured to generate an SQL query from a pull-down type menu and process the information according to the SQL query.

7. The system of claim 1, wherein the storage module is further configured to store an SQL query corresponding to a natural language, and further comprising:

a processing module configured to process the information according to the SQL query when the natural language is selected; and

a display module configured to display the processed information.

8. The system of claim 1, further comprising:

a display module configured to display an information table including module information, function information, object file information, and a source code location corresponding to an address of the event.

9. The system of claim 1, further comprising:

a display module configured to display a list of the information which includes an address of the event and a crash dump file related to the event, wherein the list is ordered by the number of event occurrences for each address.

10. The system of claim 1, further comprising:

an event management terminal comprising;

a communication module configured to receive information including a crash dump file from the storage module.

11. An event collecting server system comprising:

a receiving module configured to receive information on an event in a client application when the client application is abnormally terminated, wherein the information includes a crash dump file, wherein the receiving module is configured to extract an address of the event by compiling source code of an object file, wherein the object file includes a function of identifying where the event has occurred;

a storage module configured to store the received information in association with an online service with which the information is associated; and

a display module configured to display a list of the information which includes a reason for the event and a crash dump file related to the event, wherein the list is ordered by the number of event occurrences for each reason.

12. The system of claim 11, wherein the event management terminal further comprises:

a display module configured to display an information screen with at least one selectable field, and further configured to display information of the at least one selectable field or arrange the information in response to selecting the at least one selectable field.

13. The system of claim 12, wherein the display module provides a link to the crash dump file to enable a user of the event management module to download the crash dump file.

14. An event collecting server system comprising

a receiving module configured to receive information on an event in a client application when the client application is abnormally terminated, wherein the information includes a crash dump file and a reason for the event in the client application, wherein the receiving module is configured to extract an address of the event by compiling source code of an object file, wherein the object file includes a function of identifying where the event has occurred;

a storage module configured to store the received information in association with an online service with which the information is associated; and

a processing module configured to create a link for the crash dump file for each reason for the event and configured to count the number of event occurrences for each reason.

15. A method of collecting event information comprising:

receiving information on an event in a client application when the client application is abnormally terminated, wherein the information includes a crash dump file;

storing the received information in association with an online service with which the information is associated;

extracting an address of the event by compiling source code of an object file including the function where the event has occurred;

generating a table where the object file and the function are associated with the address by inverse-indexing; and

retrieving from the table the object file and the function by reference to the address included in the event information.

16. The method of claim 15, wherein the information comprises error data.

17. The method of claim 15, wherein the information includes an address for the event and an object file including a function where the event has occurred, and further comprising:

providing information on the object file using the address.

18. The method of claim 15, further comprising:

displaying an information screen with at least one selectable field;

displaying information of the at least one selectable field or arranging the information in response to selecting the at least one selectable field;

generating an SQL query from a pull-down type menu;

processing the information according to the SQL query; and

displaying the processed information.