This is an old revision of this page, as edited by 81.129.234.117 (talk) at 09:32, 8 March 2009 (→Detection of storage violations - give examples). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 09:32, 8 March 2009 by 81.129.234.117 (talk) (→Detection of storage violations - give examples)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)A storage violation occurs when a task modifies computer storage that it does not own.
Types of storage violation
Storage violation can, for instance, consist of writing to or freeing storage not owned by the task.
A common type of storage violation is known as a stack buffer overflow where a program attempts to alter a memory location beyond its allocated memory.
Avoidance of storage violations
Storage violations can occur in transaction systems such as CICS in circumstances where it is possible to write to storage not owned by the transaction; such violations can be reduced by enabling features such as storage protection and transaction isolation.
Detection of storage violations
In systems such as CICS, storage violations are sometimes detected (by the CICS kernel) by the use of "signatures", which can be tested to see if they have been overlaid.
Some programming languages use software bounds checking to prevent these occurrences.
Some program debugging software will also detect violations during testing.
Examples of software detecting storage violations
- IBM OLIVER (CICS interactive test/debug) from APT UK, later Compuware which used used an Instruction set simulator
- Intertest originally from Online Software International , later Computer Associates
References
IBM. "CICS Transaction Server for z/OS, Version 3 Release 2 Information Center". IBM. Retrieved 2008-10-20.
 | This computer science article is a stub. You can help Misplaced Pages by expanding it. |