TW201321057A - Method of handling abnormal termination, server performing the same and storage media storing the same - Google Patents

Abstract

A method of handling abnormal termination is carried out inside an abnormal termination handling sewer capable of connecting to a user terminal which has caused a program error. The method of handling abnormal termination comprises receiving a program identification code obtained based on the corresponding program of the user terminal and an error identification code dependent on error data generated at the time of occurrence of the program error; and if the received program identification code is found in a temporary error repository, checking whether the received error identification code has been already received in association with the received program identification code.

Description

Method for handling abnormal termination, server for executing the method, and storage medium storing the method

The present invention relates to a method for handling abnormal termination, and more particularly to a method for handling abort and an abend processing server for executing the method, which enables a program developer to receive a program identification code and an error by a user terminal that has caused a program error. The identification code, and based on the received program identification code, stores the error identification code into the error storage and the temporary error storage to immediately process the program error according to the error information stored in the program version and the error type.

In the event of an unexpected program error, the user first asks the programmer to solve the problem, and the programmer tries to solve the problem by communicating with the individual user one-to-one. However, from a developer's point of view, due to the overlap between individual problem processing processes, attempts to solve individual user problems via one-to-one communication are inevitably involved in waste of time and resources; From a perspective, dissatisfaction occurs when the developer's response is delayed.

In order to overcome this situation, the program development company collects dumping files that have captured all or part of the program, and removes unexpected errors for program error correction, data checking and backup, etc.; however, due to the source code of the program The version, execution time, and execution time environment are different from each other depending on the individual user or service provider. Therefore, efficient processing error is a very difficult task.

A variety of technologies have been developed to handle exception program termination. The patents described below all relate to the above mentioned technology.

Korean Patent Publication No. 10-2009-0010458 relates to a method of controlling a game character according to an abnormal termination connection, and more particularly, to a method for controlling a game character under abnormal connection termination, when an abnormal connection termination occurs in a game program By using artificial intelligence to avoid role death penalty, it is possible to control the behavior of the game character for a predetermined time.

Korean Patent Publication No. 10-2002-0078230 relates to a method of storing data when an abnormal system is terminated, and more particularly, a method for avoiding data loss, which includes: a boot period in which a boot load is performed when power is turned on. And executing the program by loading the initial data into the RAM; the data re-calling period, wherein if the flash memory contains data from the previous task, the corresponding data is read and the corresponding application is started; and the data storage period If an abnormal system termination occurs during execution of the application, the system data and application data temporarily stored in the RAM are stored in the flash memory and subsequently terminated.

Previous technology only provided technology to prevent program users from experiencing unanticipated data loss when the program or system terminated abnormally. However, previous technologies did not provide technology to analyze and deal with the cause of errors from the perspective of a programmer.

The present invention has been made to provide a method of handling abnormal termination and to perform the method The abort processing server, which enables the program developer to receive the program identification code and the error identification code from the user terminal that has caused the program error, and store the error identification code to the error storage device based on the received program identification code and In the temporary error store, the program error is immediately processed by the error information stored according to the program version and the error type.

The present invention seeks to provide a method for processing an abend and an abend processing server for performing the method, which can detect a hash code associated with a program as a program identification code from a user terminal, and detect The resulting program modification.

The present invention seeks to provide a method for handling an abend and an abend processing server for executing the method, which enables a program developer to receive system information of a user terminal when a program error occurs, and to identify it by associating it with the program. Code and error identification code to store system information and handle program errors in a specific way.

In a particular aspect, the method of handling an abend is performed on an abend processing server that is capable of connecting to a user terminal that caused a program error. The method for processing the abnormal termination includes: receiving a program identification code obtained based on a corresponding program of the user terminal, and receiving an error identification code depending on an error data generated when a program error occurs; and if the received program identification code is found In the temporary error storage, it is checked whether the received error identification code has been received in association with the received program identification code.

In a specific aspect, the method for processing abnormal termination further includes: if the received error identification code has been received, by identifying the received error The code is associated with the received program identification code and the received error identification code is stored in the error store. Here, the method of processing the abnormal termination may further include: if the received error identification code has not been received, storing the received error identification code in the temporary error storage by associating the received error identification code with the received program identification code .

In a specific aspect, the method for processing the abnormal termination further includes: if the received program identification code is not found in the temporary error storage, storing the received error by associating the received error identification code with the received program identification code The identification code is in the temporary error storage.

In a specific aspect, the method for processing the abnormal termination further includes: if the received program identification code is not found in the temporary error storage, checking whether the received error identification code has been received in the temporary error storage; and if the received error is identified The code has been received, and the received error identification code is stored in the memory for suspecting the error caused by the defect by associating the received error identification code with the received program identification code.

In one embodiment, the program identification code corresponds to a hash code associated with a corresponding program of the user terminal.

In one embodiment, the error identification code corresponds to a hash code generated based on the error exception code and an offset code retrieved from the error data via the user terminal.

In a specific aspect, the method for processing the abnormal termination further includes: receiving system information of the user terminal when a program error occurs, and associating the received system information with the received error identification code and the received program identification code. Here, the receiving system information of the user terminal may further include: Allows collection of special system information from user terminals.

In one embodiment, the system information of the user terminal includes at least one of the following: program information of the user terminal, network information, screen display information when a program error occurs, and specification information.

In a specific aspect, the abend processing server can be connected to a user terminal that causes a program error. The abnormal termination processing server includes: an identification code receiving unit that receives a program identification code obtained based on a corresponding program of the user terminal, and receives an error identification code depending on an error data generated when a program error occurs; and a storage device The search unit, if the received program identification code is found in the temporary error storage, checks whether the received error identification code has been received in association with the received program identification code.

In a specific aspect, the abnormal termination processing server further includes: an error storage unit, if the received error identification code has been received, storing the received error identification by associating the received error identification code with the received program identification code Coded in the error store. Here, if the received error identification code has not been received, the error storage unit may store the received error identification code in the temporary error storage by associating the received error identification code with the received program identification code.

In a specific aspect, the abnormal termination processing server further includes: an error storage unit, if the received program identification code is not found in the temporary error storage, by associating the received error identification code with the received program identification code, Store the received error identification code in the temporary error storage.

In a specific aspect, if the received program identification code is not found in the temporary error storage, the storage search unit checks whether the received error identification code is Whether it has been received in the temporary error storage; and the abnormal termination processing server further includes a storage unit for suspecting the error caused by the defect, if the received error identification code has been received, by associating the received error identification code with The program identification code is received, and the received error identification code is stored in a memory for suspecting the error caused by the defect.

In one embodiment, the program identification code corresponds to a hash code associated with a corresponding program of the user terminal.

In one embodiment, the error identification code corresponds to a hash code generated based on the error exception code and an offset code retrieved from the error data via the user terminal.

In a specific aspect, the abnormal termination processing server further includes: a system information receiving unit that receives system information of the user terminal when a program error occurs; and a system information storage unit that associates the received system information with the received error Identification code and received program identification code. Here, the system information receiving unit allows special system information to be collected from the user terminal.

In one embodiment, the system information of the user terminal includes at least one of the following: program information of the user terminal, network information, screen display information when a program error occurs, and specification information.

In a specific aspect, a storage medium storing a computer program for performing a method of abnormally terminating the processing of the abnormality processing server includes the following functions: receiving a program identification code obtained based on a corresponding program of the user terminal, and receiving Depending on the error identification code of the error data generated when a program error occurs; and if the received program identification code is found in the temporary error storage, it is checked whether the received error identification code is already associated with Received by the received program identification code.

The method for processing abnormal termination according to an embodiment of the present invention and the technology related to the method enable a program developer to receive a program identification code and an error identification code from a user terminal that has caused a program error, and identify based on the received program The code stores the error identification code into the error storage and the temporary error storage, and immediately processes the program error according to the error information stored in the program version and the error type.

A method for abnormally terminating processing according to an aspect of the present invention and a technique for the method for detecting a program caused by a nickname by receiving a hash code associated with a program from a user terminal as a program identification code modify.

The method for processing abnormal termination according to an embodiment of the present invention and the technology related to the method enable a program developer to receive system information of a user terminal when a program error occurs, and by associating it with the program identification code and The error identification code stores system information and handles program errors in a specific way.

The description of the present invention is not to be construed as limiting the scope of the invention. In other words, the specific aspects may be modified in various ways; therefore, it is understood that the scope of the invention includes every possible equivalent of the technical principles of the invention. Similarly, the purpose or effect of the present invention does not necessarily specify a particular embodiment to support all purposes. Or only the effect is disclosed, so it should be understood that the technical scope of the present invention is not limited to the objects or effects described in this document.

At the same time, the vocabulary used in this document should be read as follows.

The words "first", "second" and the like have been introduced to distinguish between a certain member and other members; therefore, the technical scope of the present invention should not be limited to those words. For example, a first component can be referred to as a second component and vice versa.

When a component is said to be "connected" to another component, we should understand that there may be a third component to connect the two components, even if the two components can be directly connected. On the other hand, when a component is said to be "connected directly" to another component, it should be interpreted as having no further components between the two components. At the same time, the expression of the relationship between other narrative components, that is, "between" and "immediately between" or "adjacent" and "directly adjacent", It should also be understood as above.

Unless expressly stated otherwise, the singular expression should be interpreted as including the plural. For example, the words "include" and "have" are meant to indicate the presence of features, quantities, steps, behaviors, components, modules, and combinations thereof, and should be understood as not precluding the existence or The possibility of adding one or more features, quantities, steps, behaviors, components, modules, and combinations thereof.

The identification symbols (eg, a, b, c, and the like) introduced for the individual steps are for convenience of description; the symbols are not intended to indicate the order in which the corresponding steps are performed, and thus individual steps may be performed in a different order than specified, except Not specifically stated otherwise. In other words, individual steps may be performed in the same order as specified, or in fact, concurrently or in the reverse order.

The invention can be implemented in the form of computer readable code in a computer readable storage medium. Computer-readable storage media includes all types of storage devices that store data that can be read by a computer system. Examples of computer readable storage media include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like. Storage media implemented in the form of carriers (eg, data transfer via the Internet) are also included in the examples. At the same time, computer readable storage media can be distributed over computer systems connected to each other via a network, and computer readable code can be stored and executed in a decentralized manner.

The terms used in this document have the same meaning as understood by those skilled in the art, unless otherwise defined. The vocabulary defined by the general purpose dictionary should be interpreted to be consistent with the contextual meaning used by the relevant technology. Unless otherwise clearly defined in this document, those terms should not be interpreted as having an ideal or overly formal meaning.

[Mode of the invention]

1 illustrates an abnormal termination processing system in accordance with an embodiment of the present invention.

Referring to FIG. 1, the abnormal termination processing system includes a user terminal 110 and an abnormal termination processing server 120. Here, the user terminal 110 can connect to the abend processing server 120 via a network (especially the Internet).

User terminal 110 includes computing means that can be executed by a user. For example, the user terminal 110 may correspond to a desktop computer, a laptop computer, a smart phone, or a tablet personal computer (PC).

The user terminal 110 transmits the program identification code and the error identification code to the abnormal termination processing server 120.

In one embodiment, the user terminal 110 retrieves the hash code associated with the program and transmits the code to the abend processing server 120. Here, since the hash code is a unique value given by the special program, the abnormality termination processing server 120 determines the version of the program or the program modification due to the file by the received hash code.

In a specific aspect, the user terminal 110 retrieves the error data generated when a program error occurs, and transmits the error data to the abnormal termination processing server 120.

More specifically, the error data corresponds to a file that captures all or part of the program for program error correction, data inspection, backup, and the like. In one embodiment, if a crash occurs while the program is executing, the mini dump file may correspond to a file that includes information about the abnormal termination of the program (eg, stack tracking, stacking).

The user terminal 110 generates an error identification code depending on the error data generated when a program error occurs, and transmits the generated error identification code to the abnormal termination processing server 120.

More specifically, the user terminal 110 can generate a hash code corresponding to the error identification code by applying a hash function to the error data. In a specific aspect, the user terminal 110 can generate a hash code by extracting an error exception code and an offset code from the error data.

Here, the function performed by the error exception code is to terminate the program when an error occurs while the program is executing, and includes identifying an error by using an exception. The code of the function. The offset code corresponds to the sector address loaded into the memory during program execution, and the function provided is to calculate the memory reference state relative to the error that occurred.

The user terminal 110 generates a combined code by combining the error exception code and the offset code extracted from the error data. For example, if the error exception code is a 10-digit combination of letters or numbers and the offset code is a combination of 6-digit letters or numbers, the user terminal 110 can generate 16-bit letters by combining the error exception code and the offset code. Or a string of numbers. The user terminal 110 can generate a hash code corresponding to the error identification code by applying a hash function with a string of 16-bit letters or numbers generated as a root source. At this time, since the error identification code corresponds to the unique code depending on the error data, the abnormality termination processing server 120 that receives the error identification code can determine the type of the program error via the error identification code.

In one embodiment, the user terminal 110 transmits system information to the abnormal termination processing server 120 when a program error occurs. At this time, the system information includes at least one of the following: program information (such as program ID and name) of the user terminal in the event of a program error, network information (such as network utilization or the amount of input and output packets), screen output Information (such as screen photos), specifications (such as CPU, RAM, OS information, graphics card, motherboard).

The abend termination processing server 120 corresponds to a computing device that is connectable to the user terminal 110 via a network. Here, the abnormality termination processing server 120 can be managed by a program development company, a program supply service company, or a program management service company. The error handling server 120 will be described with reference to FIG. 2.

2 is a block diagram showing an abnormal termination processing server of FIG. 1.

Referring to FIG. 2, the abnormality termination processing server 120 includes an identification code receiving unit 210, a storage search unit 220, an error storage unit 230, a storage unit 240 for suspecting an error caused by a defect, a system information receiving unit 250, and system information. The storage unit 260 and the controller 270.

The identification code receiving unit 210 receives, from the user terminal 110, a program identification code obtained based on a program that has caused an error, and receives an error identification code depending on an error material generated when a program error occurs.

In one embodiment, the identification code receiving unit 210 receives the hash code associated with the program from the user terminal 110 as a program identification code. Here, since the hash code is a unique value given by the special program, the identification code receiving unit 210 determines the version of the program or the program modification due to the file by the received program identification code.

In a specific aspect, the identifier receiving unit 210 receives the hash code from the user terminal 110 as an error identification code, which is generated by applying a hash function to an error data generated when a program error occurs. . Here, the error identification code corresponds to a hash code generated based on the error exception code and an offset code extracted from the error data.

Here, since the error identification code corresponds to the unique code depending on the error data, the identification code receiving unit 210 can determine the type of the program error via the error identification code.

The storage search unit 220 searches the error database for at least one of the program identification code and the error identification code received from the user terminal 110.

The error storage unit 230 recognizes the program received from the user terminal 110. The code and the error identification code are stored in the error database.

The storage search unit 220 and the error storage unit 230 will be described with reference to FIG.

Figure 3 shows an example error database. FIG. 3 shows an error database included in the abnormal termination processing server 120, and is not intended to limit the technical scope of the present invention. In other words, FIG. 3 is a data structure to demonstrate an error database, wherein the error database can be implemented by a group of materials classified according to the program identification code.

As shown in FIG. 3, the error database 310 includes an error store 311, a temporary error store 312, and a storage 313 for suspecting the error caused by the defect.

The error store 311 corresponds to a data set in which the abnormality termination processing server 120 stores the program identification code and the error identification code collected from the user terminal 110 when a program error occurs. In other words, the abend processing server 120 classifies the types of program errors according to the program version and stores the codes in the error store 311.

The storage search unit 220 searches the error storage 311 to find the program identification code received from the user terminal 110. If the program identification code is found to be stored in the error store 311, the error storage unit 230 stores the error identification code in the error store 311 by associating the error identification code with the program identification code.

For example, as shown in FIG. 3b, if the identification code receiving unit 210 receives the program identification code corresponding to {A1} and the error identification code corresponding to {B1} from the user terminal 110, the storage searching unit 220 can execute search Let us see if the program identification code corresponding to {A1} is stored in the error store 311. Here, if the storage search unit 220 determines that there is a program identification code corresponding to {A1}, the error storage unit 230 stores {A1} and {B1} for error storage by associating {A1} and {B1} with each other. 311. In other words, if an error regarding the special program version has been stored in the error store 311, the error storage unit 230 stores the received program identification code and the error identification code in accordance with the existing program version.

Now, the storage search unit 220 performs a search to see if the same error identification code is stored in the error storage 311, and if the same program identification code and error identification code already exist, the error storage unit 230 counts and stores the corresponding program. The cumulative total of the identification code and the error identification code. In other words, the error storage unit 230 can store the number of occurrences according to the program version and the error type.

The storage search unit 220 performs a search to see if the program identification code received from the user terminal 110 is stored in the error storage unit 311; if the same program identification code is not found in the error storage unit 311, the storage search unit 220 searches The temporary error store 312 looks to see if the program identification code is stored therein.

First, if the storage search unit 220 determines that the program identification code is not stored in the temporary error storage 312, the error storage unit 230 stores the program identification code and the error identification code in a temporary error by associating the program identification code and the error identification code with each other. Reservoir 312. That is, if the received program identification code is not stored in the error store 311 and the temporary error store 312, there is no guarantee that the program identification code really indicates the new program version or is being shackled. The resulting program modification causes the error store 230 to store the program identification code and the error identification code into the temporary error store 312.

For example, as shown in FIG. 3b, if the identification code receiving unit 210 receives the program identification code corresponding to {A3} and the error identification code corresponding to {B2} from the user terminal 110, the storage search unit 220 can execute The search is to see if the program identification code corresponding to {A3} is stored in the temporary error storage 312 instead of being stored in the error storage 311. Here, if the storage search unit 220 determines that the program identification code corresponding to {A3} does not exist in the temporary error storage 312, the error storage unit 230 stores {A3} by associating {A3} and {B2} with each other. And {B2} in the error store 312.

Next, if the storage search unit 220 determines that the program identification code is stored in the temporary error storage 312, the storage search unit 220 performs a search to see if the error identification code is stored in the temporary error storage 312 and is associated with the received program identification code. .

Here, if the storage search unit 220 determines that the error identification code is associated with the received program identification code and thus is stored in the temporary error storage 312, the error storage unit 230 associates the program identification code and the error identification code with each other and stores them. In the error storage 311; and if it is determined that the error identification code is not stored in the temporary error storage 312, the error storage unit 230 associates the program identification code and the error identification code with each other and stores them in the temporary error storage 312.

For example, as shown in FIG. 3b, if the identification code receiving unit 210 receives the program identification code corresponding to {A4} and the error identification code corresponding to {B1} from the user terminal 110, the storage search unit 220 determines the corresponding On {A4} The program identification code is not stored in the error store 311 but is stored in the temporary error store 312.

Here, if the storage search unit 220 determines that the error identification code corresponding to {B1} is associated with the program identification code corresponding to {A4} and has been stored in the temporary error storage 312, the error storage unit 230 sets {A4, B1 } Move to the error store 311 and store them in it.

More specifically, if a special version of the special error type has been stored in the temporary error store 312 and received the same version and error type from the user terminal 110, then it may be considered that a particular type of error has occurred with respect to the new program version; Therefore, the error storage unit 230 stores the error type regarding the new program version in the error storage 311. This is a reasonable situation, because if the identification code receiving unit 210 receives the program identification code and the error identification code stored in the temporary error storage 312 two or more times, it can be regarded as an error with respect to the new version program instead of Modified by the program.

To another example, as shown in FIG. 3b, if the identification code receiving unit 210 receives the program identification code corresponding to {A4} and the error identification code corresponding to {B2} from the user terminal 110, the storage search unit 220 It is determined that the program identification code corresponding to {A4} is not stored in the error storage unit 311 but is stored in the temporary error storage unit 312.

Here, if the storage search unit 220 determines that the error identification code corresponding to {B2} is associated with the program identification code corresponding to {A4} but is not stored in the temporary error storage 312, the error storage unit 230 sets {A4, B2 } is stored in the temporary error store 312.

The above scenario assumes that the error identification code is the same as the program identification code stored in the temporary error storage 312 but the error type is different. In this case, it is not clear whether an error has occurred regarding the new version of the program or the program modification due to the shackles; and the error storage unit 230 stores the received program identification code and the error identification code in the temporary error storage 312.

Referring again to FIG. 2, the storage unit 240 for suspicion of the error caused by the defect is associated with the program identification code and the error identification code, and stores them in the storage 313 for suspicion of the error caused by the defect.

More specifically, the storage search unit 220 determines that the program identification code received from the user terminal 110 is not stored in the error storage 311, and checks whether the program identification code is stored in the temporary error storage 312. If the storage search unit 220 determines that the program identification code is not stored in the temporary error storage 312, the error storage unit 230 associates the program identification code and the error identification code with each other and stores them in the temporary error storage 312.

Here, the storage search unit 220 may perform a search to see if the error identification code received from the user terminal 110 is stored in the temporary error storage 312. If it is determined that the error identification code is stored in the temporary error storage 312, the storage unit 240 for suspicion of the error caused by the defect associates the program identification code and the error identification code with each other and stores them for suspected beating. The wrong storage 313.

For example, as shown in FIG. 3b, if the identification code receiving unit 210 receives the program identification code corresponding to {A3} and the error identification code corresponding to {B1} from the user terminal 110, the storage search unit 220 determines the corresponding The program ID of {A3} is neither stored in the error store 311 nor stored temporarily. Error store 312. Here, if the storage search unit 220 determines that the error identification code corresponding to {B1} is stored in the temporary error storage 312, the storage unit 240 for suspecting the error caused by the defect can store {A3, B1} for use. A reservoir 313 that is suspected of being caused by a defect.

More specifically, if the received program identification code is neither stored in the error store 311 nor stored in the temporary error store 312, the slave program identification code does not know whether the current situation corresponds to the new version of the program or is The resulting program modification; therefore, the error storage unit 230 stores the program identification code and the error identification code in the temporary error storage 312. Here, if the same error identification code has been stored in the temporary error storage 312, it indicates that the same type of error has occurred before but the program identification code is different; therefore, it may be regarded as a program whose program identification code has been caused by the problem. Modifications, not new versions of programs, are different. In this regard, the storage unit 240 for suspicion of the error caused by the bedding stores {A3, B1} in the storage 313 for suspecting the error caused by the bedding.

The system information receiving unit 250 receives the system information of the user terminal 110 from the user terminal 110 when a program error occurs.

In one embodiment, the system information includes at least one of: program information (eg, program ID and name) of the user terminal in the event of a program error, network information (eg, network utilization or amount of input and output packets) , screen output information (such as screen photos), specification information (such as CPU, RAM, OS information, graphics card, motherboard).

The system information storage unit 260 can close each other by associating the system information with the program identification code and the error identification code stored in the error database 310. The system information received from the user terminal 110 is stored in the error database 310. In other words, the system information storage unit 260 can allow the program developer to analyze the program error when the program error occurs by additionally storing the system information corresponding to the program version and the error type in the error database 310 (which is classified according to the program version and the error type). The system environment and handle special program versions and special error types in a specific way.

In one embodiment, system information receiving unit 250 allows for collection of special system information from user terminal 110. More specifically, when the user terminal 110 is collecting system information when a program error occurs, the user terminal 110 can transmit at least one piece of system information that can be collected to the system information receiving unit 250. Here, the system information receiving unit 250 can be allowed to collect special system information. In other words, since the system information receiving unit 250 is allowed to collect specific system information, the security problem regarding collecting personal information can be solved, and the program developer can obtain only system information that he or she is interested in.

The controller 270 controls the operation of the identification code receiving unit 210, the storage unit search unit 220, the error storage unit 230, the storage unit 240 for suspecting the error caused by the defect, the system information receiving unit 250, and the system information storage unit 260. flow.

4 is a flow chart showing an abnormal termination processing procedure executed by the abnormal termination processing server.

The identification code receiving unit 210 receives the program identification code obtained based on the program that has caused the error from the user terminal 110, and receives an error identification code depending on the error data generated when the program error occurs, S410.

In one embodiment, the identification code receiving unit 210 receives the hash code associated with the program from the user terminal 110 as a program identification code. Here, since the hash code is a unique value given by the special program, the identification code receiving unit 210 determines the version of the program or the program modification due to the file by the received program identification code.

In a specific aspect, the identifier receiving unit 210 receives the hash code from the user terminal 110 as an error identification code, which is generated by applying a hash function to an error data generated when a program error occurs. . Here, the error identification code corresponds to a hash code generated based on the error exception code and an offset code extracted from the error data.

The storage search unit 220 searches the error storage 311 to find the program identification code received from the user terminal 110, S420.

If the program identification code is found to be stored in the error store 311, the error storage unit 230 stores the error identification code in the error store 311 by associating the error identification code with the program identification code, S421. In other words, if an error regarding the special program version is stored in the error storage 311, the error storage unit 230 stores the received program identification code and the error identification code in the error storage 311.

The storage search unit 220 performs a search to see if the program identification code received from the user terminal 110 is stored in the error storage unit 311; if the same program identification code is not found in the error storage unit 311, the storage search unit 220 searches Temporary error store 312 to see if the program identification code is stored therein, S430.

First, if the storage search unit 220 determines that the program identification code is not Stored in the temporary error storage 312, the error storage unit 230 stores the program identification code and the error identification code in the temporary error storage 312, S431, by associating the program identification code and the error identification code with each other. That is to say, if the received program identification code is not stored in the error storage unit 311 and the temporary error storage unit 312, the error storage unit cannot be guaranteed because the program identification code does not indicate the new program version or the program modification caused by the file. The program identification code and the error identification code are stored in the temporary error storage 312.

Here, the storage search unit 220 may perform a search to see if the error identification code received from the user terminal 110 is stored in the temporary error storage 312, S432. If it is determined that the error identification code is stored in the temporary error storage 312, the storage unit 240 for suspicion of the error caused by the defect associates the program identification code and the error identification code with each other and stores them for suspected beating. The wrong storage 313, S433. In other words, if the same error identification code has been stored in the temporary error storage 312, it indicates that the same type of error has occurred before but the program identification code is different; therefore, it may be considered that the program identification code is modified by the program caused by the error. The new version of the non-program has become different. In this regard, the storage unit 240 for suspicion of the error caused by the shackles stores {A3, B1} in the storage 313 for suspicion of the error caused by the shackles.

If the storage search unit 220 determines that the program identification code is stored in the temporary error storage 312, the storage search unit 220 performs a search to see if the error identification code is stored in the temporary error storage 312 and is associated with the received program identification code, S440. .

Here, if the storage search unit 220 determines the error identification code association Upon receiving the program identification code but not stored in the temporary error storage 312, the error storage unit 230 associates the program identification code and the error identification code with each other and stores them in the temporary error storage 312, S441. The above scenario assumes that the error identification code is the same as the program identification code stored in the temporary error storage 312 but the error type is different. In this case, it is not clear whether an error has occurred regarding the new version of the program or the program modification due to the bedding; and the error storage unit 230 stores the received program identification code and the error identification code into the temporary error storage 312.

If the storage search unit 220 determines that the error identification code is associated with the received program identification code and is stored in the temporary error storage 312, the error storage unit 230 associates the program identification code and the error identification code with each other and stores them in the error storage. 311, S450. This is a reasonable situation, because if the identification code receiving unit 210 receives the program identification code and the error identification code stored in the temporary error storage 312 two or more times, it can be regarded as an error with respect to the new version program instead of Modified by the program.

In one embodiment, the system information receiving unit 250 receives, from the user terminal 110, system information of the user terminal 110 when a program error occurs.

In one embodiment, the system information includes at least one of: program information (eg, program ID and name) of the user terminal in the event of a program error, network information (eg, network utilization or amount of input and output packets) , screen output information (such as screen photos), specification information (such as CPU, RAM, OS information, graphics card, motherboard).

In one embodiment, the system information storage unit 260 can associate the system information with the program identification code and error stored in the error database 310. The identification codes are associated with each other to store system information received from the user terminal 110 in the error database 310. In other words, the system information storage unit 260 can allow the program developer to analyze the program error when the program error occurs by additionally storing the system information corresponding to the program version and the error type in the error database 310 (which is classified according to the program version and the error type). The system environment and handle special program versions and special error types in a specific way.

Although the present invention has been described with reference to the preferred embodiments thereof, it is understood that the invention may be modified and changed in various ways, without departing from the technical principles defined in the appended claims. range.

110‧‧‧User terminal

120‧‧‧Abnormal termination processing server

210‧‧‧ID receiving unit

220‧‧‧Storage Search Unit

230‧‧‧Error storage unit

240‧‧‧Storage unit for suspected errors caused by defamation

250‧‧‧System Information Receiving Unit

260‧‧‧System Information Storage Unit

270‧‧‧ Controller

310‧‧‧Error database

311‧‧‧Error storage

312‧‧‧ temporary error storage

313‧‧‧Storage for suspected errors caused by defamation

The accompanying drawings are included to provide a further understanding of the invention

1 is a block diagram showing an abnormal termination processing server according to an embodiment of the present invention; FIG. 2 is a block diagram showing an abnormal termination processing server of FIG. 1; FIG. 3 is an exemplary error database; and FIG. 4 is an exemplary execution of an abnormal termination processing servo. Flowchart of the abnormal termination process.

100‧‧‧Abnormal termination processing system

110‧‧‧User terminal

120‧‧‧Abnormal termination processing server

Claims (15)

A method for handling abnormal termination, which is executed in an abnormal termination processing server capable of connecting to a user terminal that has caused a program error, the method comprising: receiving a program identification code obtained based on a corresponding program of the user terminal, and receiving Depending on the error identification code of the error data generated when a program error occurs; and if the received program identification code is found in the temporary error storage, it is checked whether the received error identification code is associated with the received program identification code and received . The method of claim 1, further comprising: if the received error identification code has been received, storing the received error identification code in error storage by associating the received error identification code with the received program identification code Device. The method of claim 2, further comprising: if the received error identification code has not been received, storing the received error identification code in a temporary error by associating the received error identification code with the received program identification code Storage. The method of claim 1, further comprising: if the received program identification code is not found in the temporary error storage, storing the received error by associating the received error identification code with the received program identification code The identification code is in the temporary error storage. The method of claim 1, further comprising: if the received program identification code is not found in the temporary error storage, then checking and receiving Whether the error identification code has been received by the temporary error storage; and if the received error identification code has been received, storing the received error identification code for use by associating the received error identification code with the received program identification code A reservoir suspected of being mistaken by the shackles. The method of claim 1, wherein the program identification code corresponds to a hash code associated with a corresponding program of the user terminal. The method of claim 1, wherein the error identification code corresponds to a hash code generated based on the error exception code and an offset code retrieved from the error material via the user terminal. An abnormal termination processing server capable of being connected to a user terminal that has caused a program error, the server comprising: an identification code receiving unit that receives a program identification code obtained based on a corresponding program of the user terminal, and the receiving depends The error identification code of the error data generated when a program error occurs; and the storage search unit, if the received program identification code is found in the temporary error storage, it is checked whether the received error identification code is already associated with the received program identification. Code and receive. The server of claim 8 further comprising: an error storage unit, if the received error identification code has been received, storing the received error by associating the received error identification code with the received program identification code The identification code is in the error store. The server of claim 9, wherein if the received error identification code has not been received, the error storage unit stores the received error identification by associating the received error identification code with the received program identification code. Coded in a temporary error store. The server of claim 8 further comprising: an error storage unit, if the received program identification code is not found in the temporary error storage, by associating the received error identification code with the received program identification code, The received error identification code is stored in the temporary error storage. The server of claim 8, wherein if the received program identification code is not found in the temporary error storage, the storage search unit checks whether the received error identification code has been received in the temporary error storage; and the server Further comprising: a storage unit for suspicion of an error caused by the shackle, if the received error identification code has been received, storing the received error identification code by associating the received error identification code with the received program identification code A reservoir used to suspect the error caused by the bedding. The server of claim 8, wherein the program identification code corresponds to a hash code associated with a corresponding program of the user terminal. The server of claim 8, wherein the error identification code corresponds to a hash code generated based on the error exception code and an offset code retrieved from the error data via the user terminal. A storage medium for storing a computer program for processing an abnormal termination method, which stores a computer program for performing a method for abnormally terminating processing of an abnormality termination processing server, which includes the following functions: receiving a corresponding program based on a user terminal Program identifier and receive the function of an error identifier that depends on the error data generated when a program error occurs; If the received program identification code is found in the temporary error store, it checks whether the received error identification code has been associated with the received program identification code and received the function.