What is an unusual end?

Abnormal end is a sudden and unexpected end of a working computer program or application. Its name originally comes from the older operating system IBM 360, which recorded such an end such as Abend errors. The abnormal end of the program may occur for many different reasons, but the most common reasons include system memory problems or software code problems. When this type of termination occurs, the program closes itself and the operating system enters the damage by flushing the program memory and action as if the program has successfully closed in typical situations. When a computer allows you to leak memory - if it allows the program to write in memory that the operating system has not included - it can unintentionally rewrite parts of memory that Belonged to another program. As soon as the "attacked" program attempts to recover the information stored in the attacked parts of the memory, it does not find the correct, expected data. This mismatch often leads to a complete application failure because it cannot be started usingwritten information stored by invasion program.

software code problems can sometimes run an unusual end of the program. If the software has errors or does not contain sufficient error processing code, incorrect end -user inputs can lead to unusual software. For example, a program that asks the end user to enter its phone number will usually be coded so that any non-non-semheric answer that does not contain 10 digits is immediately "caught" as a potential error and returned to the end user as a bad result. Immature or incomplete software that does not include this err or manipulation code can collapse after incorrect input; The program will not be able to match if the end user decides to enter "ABCDEFG" as its anticipated phone number.

Once an abnormal end occurs, the operating system usually alerts the computer users that it has receivedo to end the program. Then the task of the operating system is to recover from the accident without adversely affecting any of the other programs in the system. To this end, he usually releases the memory he has assigned to the program exactly as it would be if the program successfully ended. Information about the abnormal end of the program is often stored in the operating system protocols, allowing the end user to review the accident information and look for the potential root cause of the conflict.