Unintended ROM code execution: Difference between revisions
Jump to navigation
Jump to search
Content added Content deleted
>Torchickens No edit summary |
>Sherkel m (Generally speaking, isn't this what a glitch is? Leaving it up for now, but removing it from Major.) |
||
| (4 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| ⚫ | |||
{{Major glitches}} |
|||
| ⚫ | |||
Under normal circumstances |
Under normal circumstances ROM execution is one of the main tasks of the hardware's central-processing unit (CPU) in order to process the game's engine. |
||
However, an access point such as a [[glitch item]]'s effect, a [[Arbitrary code execution#Via custom map script pointer|custom map script pointer]] or a [[glitch move]] is a means of running code from the ROM or a rewritable source ([[arbitrary code execution]]). |
However, an access point such as a [[glitch item]]'s effect, a [[Arbitrary code execution#Via custom map script pointer|custom map script pointer]] or a [[glitch move]] is a means of running code from the ROM or a rewritable source ([[arbitrary code execution]]). |
||
Although the code is in the ROM, executing it may lead to unintended behavior due to one or more of the following factors: |
Although the code is in the ROM, executing it may, in addition to events coded by the game developers, lead to unintended behavior due to one or more of the following factors: |
||
*If the registers are incorrect. |
*If the registers are incorrect. |
||
*If the location is in the middle of the code and/or the game interprets the wrong ASM. |
*If the location is in the middle of the code and/or the game interprets the wrong ASM. |
||
*If the bank to the function's pointer is wrong. |
|||
*If the location is not a routine (e.g. graphics data). |
*If the location is not a routine (e.g. graphics data). |
||
{{stub}} |
{{stub}} |
||
Latest revision as of 23:04, 6 March 2019
Unintended ROM code execution is the execution of existing code or data in the ROM of a video game from an access point, via a glitch.
Under normal circumstances ROM execution is one of the main tasks of the hardware's central-processing unit (CPU) in order to process the game's engine.
However, an access point such as a glitch item's effect, a custom map script pointer or a glitch move is a means of running code from the ROM or a rewritable source (arbitrary code execution).
Although the code is in the ROM, executing it may, in addition to events coded by the game developers, lead to unintended behavior due to one or more of the following factors:
- If the registers are incorrect.
- If the location is in the middle of the code and/or the game interprets the wrong ASM.
- If the bank to the function's pointer is wrong.
- If the location is not a routine (e.g. graphics data).
This article or section is a stub. You can help Glitch City Wiki by expanding it. 
|