Error management system and method of using the same

• US 20070033281A1
• Filed: 08/01/2006
• Published: 02/08/2007
• Est. Priority Date: 08/02/2005
• Status: Active Grant

• Current Assignee: NHN Entertainment Corporation
• Original Assignee: NHN Corporation
• Inventors: Park, Hyun-Woo, Hwang, Min
• Granted Patent: US 7,702,959 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• 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 management system comprising:

an intercept module configured to intercept and collect information on an event in a client application when the client application is abnormally terminated, wherein the client application is configured to operate with a server application via a network link;

a memory module configured to store the information collected by the intercept module; and

a transmission module configured to communicate the information to an event collecting server.

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

3. The system of claim 1, wherein the information includes a crash dump file for the event.

4. The system of claim 1, wherein the server application is configured to operate with a service server providing an online service.

5. The system of claim 1, wherein the intercept module is further configured to associate the information with an online service configured to operate with the server application.

6. The system of claim 1, wherein the transmission module is configured to transmit the stored information when the client application is restarted.

7. The system of claim 1, wherein the memory module is configured to collect the information when the client application is abnormally terminated, and wherein the transmission module is configured to immediately transmit the collected information.

8. The system of claim 3, wherein the information includes an address of the event in the client application.

9. The system of claim 1, wherein the transmission module is configured to transmit the information in the form of a file identifiable by a Uniform Resource Locator using the HyperText Transfer Protocol.

10. The system of claim 1, wherein the transmission module is configured to transmit the information using the Simple Object Access Protocol.

11. The system of claim 1, wherein the information includes environment information collected by the intercept module.

12. 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 storage module configured to store the received information in association with an online service with which the information is associated.

13. The system of claim 12, wherein the information comprises error data.

14. The system of claim 12, 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.

15. The system of claim 12, 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.

16. The system of claim 12, wherein the receiving module extracts an address of the event by compiling source code of an object file including the function where the event has occurred.

17. The system of claim 16, 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.

18. The system of claim 12, 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.

19. The system of claim 12, 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.

20. The system of claim 12, 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.

21. The system of claim 12, further comprising:

a display module configured to display a list of associations ordered by the number of event occurrences for an address of the event, wherein the event occurrence includes an association between the information and the crash dump file.

22. The system of claim 12, further comprising:

a display module configured to display a list of associations ordered by the number of event occurrences for a reason of the event, wherein the event occurrence includes an association between the information and the crash dump file.

23. The system of claim 12, wherein the information includes a reason for the event in the client application, and further comprising:

a processing module configured to create for the reason an association between the information and the crash dump file, and counts a number of associations for the reason.

24. The system of claim 12, further comprising:

an event management terminal comprising;

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

25. The system of claim 24, 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.

26. The system of claim 25, 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.

27. A method of event management, the method comprising:

intercepting and collecting information on an event in a client application when the client application is abnormally terminated, wherein the client application is configured to operate with a server application via a network link;

storing the collected information; and

communicating the information to an event collecting server.

28. The method of claim 27, wherein the information comprises error data.

29. The method of claim 27, wherein the event information includes a crash dump file for the event.

30. The method of claim 27, wherein the information is transmitted when the client application is restarted.

31. The method of claim 27, wherein the information is transmitted in the form of a file identifiable by a Uniform Resource Locator using the HyperText Transfer Protocol.

32. The method of claim 27, wherein the information is transmitted using the Simple Object Access Protocol.

33. 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; and

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

34. The method of claim 33, wherein the information comprises error data.

35. The method of claim 33, 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.

36. The method of claim 33, further comprising:

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.

37. The method of claim 33, 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.

38. A computer-readable medium storing instructions when executed perform a method comprising:

intercepting and collecting information on an event in a client application when the client application is abnormally terminated, wherein the client application is configured to operate with a server application via a network link;

storing the collected information; and

communicating the information to an event collecting server.